Preparing GCC Build: Difference between revisions
Jump to navigation
Jump to search
| [unchecked revision] | [unchecked revision] |
Content added Content deleted
| Line 75: | Line 75: | ||
The makefiles of Binutils and GCC use the <source lang="make" enclose="none">$(CC)</source> variable to invoke the compiler. On OS X, this resolves to <source lang="text" enclose="none">GCC</source> by default, which is actually not the "real thing", but <source lang="bash" enclose="none">Clang</source>. Note that since at least OS X 10.8, Xcode's Command Line Tools package comes with Clang, and this version of Clang does indeed work to compile a working version of GCC, unlike what these instructions previously reflected. |
The makefiles of Binutils and GCC use the <source lang="make" enclose="none">$(CC)</source> variable to invoke the compiler. On OS X, this resolves to <source lang="text" enclose="none">GCC</source> by default, which is actually not the "real thing", but <source lang="bash" enclose="none">Clang</source>. Note that since at least OS X 10.8, Xcode's Command Line Tools package comes with Clang, and this version of Clang does indeed work to compile a working version of GCC, unlike what these instructions previously reflected. |
||
Note that users running OS X 10.7 may need to find and install GCC, either from [http://brew.sh |
Note that users running OS X 10.7 may need to find and install GCC, either from [http://brew.sh Homebrew], or from somewhere on Apple's website. |
||
Thus, the instructions below are really only relevant for these users, but your mileage may vary. |
Thus, the instructions below are really only relevant for these users, but your mileage may vary. |
||
<source lang="bash"> |
<source lang="bash"> |
||