Skip to content

clang used instead of gcc on my version of MacOS, prints different output for c compiler setup #163

@tamblood

Description

@tamblood

For this section of the setup for MacOs for C Compiler:

This gives you the GCC or the GNU Compiler Collection. To test installation, within the Terminal application, type gcc and you should get the following:

1
2
$ gcc
i686-apple-darwin11-llvm-gcc-4.2: no input files

However, I see:

Tamaras-MacBook-Pro:new-coder tamaralblood$ gcc
clang: error: no input files
Tamaras-MacBook-Pro:new-coder tamaralblood$

I believe this happens because MacOs defaults to calling clang when gcc is typed.
I think this section of the tutorial could be clearer if it mentioned, 'you may also see a different output, such as
$ gcc
clang: error: no input files
'

Without such verbiage, I thought I had made a mistake because I didn't see:
i686-apple-darwin11-llvm-gcc-4.2: no input files

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions