Clang is a faster and BSD-licensed compiler that Apple is putting all its weight behind now. LLVM-GCC has also been deprecated as it was removed as-of LLVM 3.0.
Clang is the future and it's the default compiler with the Command Line Tools. We just need to wait for upstreams to fix the various issues.
It's worth noting that this is why monocultures are bad. For all the love of GCC (and it is great) we now have a huge quantity of open-source software that only compiles with one compiler. This is a shame and hopefully Clang will help rectify that.
I wonder if there's a compelling reason for these add-on distros (Fink, Homebrew, Macports) to be strictly "build from source" with no option for binary package downloads. For me, it just seems to add long delays in getting a tool installed, and adds frustrating dependencies on my Xcode version.
For that to happen, someone has to take responsibility for creating, managing, and distributing those binary packages. That's much easier said than done.
So, the simple answer is that no one has, as of yet, volunteered to do the work.
Fink ships apt-get which is still perfectly capable of using them.
For example Qt has a bottle: https://github.com/mxcl/homebrew/blob/master/Library/Formula...
The reason we aren't doing this for more packages is basically people power and hosting (as I'm not sure Sourceforge would be happy we hosting the number of binaries we'd want to have).
Hope that explains a bit. Feel free to comment if you think we're taking a good/bad approach here.
http://lists.macosforge.org/pipermail/macports-users/2011-Ju...
In my experience, those are quite common now - most of the packages I install are delivered as binaries.
While strictly true, it's kind of irrelevant. The official stance is that GCC is the only compiler that is supported to build recent versions of GCC. This has been true since some point around GCC 4.0.
[1] https://github.com/mxcl/homebrew/wiki/Acceptable-Formula
(And llvm-gcc is based on that version, which is 4.2.1 or something, about 5 years old)
This is problematic for the Cocotron project [1], which is an Xcode-compatible cross-compiler environment for creating Windows/Linux ports of Cocoa apps. Currently one has to revert to Xcode 4.0.2 to build Cocotron's cross-compiler, then upgrade back to 4.2... This is not terribly convenient. (I guess the long-term solution is that Cocotron either has to add a dependency on a non-Apple gcc, or needs to switch to clang for its cross-compiler.)
The only measure by which llvm-gcc is not "real" is that it's not included in the core gcc distribution.
Edit -- the llvm-gcc project doesn't seem to share your opinion of the project as being "just another back-end". They certainly don't claim that it's fully compatible, only that it supports "many" features, "most" options, "a number of" extensions:
"Being derived from the GNU Compiler Collection, llvm-gcc has many of gcc's features and accepts most of gcc's options. It handles a number of gcc's extensions to the C programming language."
You don't even have to go as far as kernel developers. From a 'write once, compile everywhere' perspective, GCC is actually pretty bad. I used to work at a company that built and deployed to somewhere in the neighborhood of 20 different *nix platforms, over 6 different hardware architectures, running various GCC versions. Working around version- or backend-specific GCC issues was almost a daily task, and it wasn't getting any better with later versions.
It's not that GCC is 'bad', but it's not holy either, not by any stretch of imagination. There's a reason Apple decided to push clang as an alternative. I believe clang+LLVM will some day replace GCC on Linux and other platforms that use GCC as well.
All the backends which gcc publish share huge amounts of code, in particular all the optimizations framework in the shape of the SSA representation and GIMPLE, support for generating debugging information via DRAWF.
LLVM-GCC just takes the minimum amount of GCC and replaces the entire back-end.
Do you mean something more specific?
http://stackoverflow.com/questions/7137480/how-do-i-add-ppc-...
http://www.cocoabuilder.com/archive/xcode/299924-no-ppc-from...
It's been 6 years. The world has moved on, and Apple no longer has any commercial interest in PowerPC. You really expect them to keep bothering with it?
Apple isn't actually stopping you from compiling for PPC. They just aren't shipping the compiler themselves. AFAIK, they don't ship any compilers for hardware they don't support — no VAX, no MIPS, no M68k — PPC is not special in that respect. I don't see what's so terrible about that.
Lion is the _second_ version of OS X not to even run on PPC. Why should the developer tools they distribute for Lion support it at all?
Also available are 1.5, 2.3, 2.4, 2.4.1, 3.0, 3.1, 3.1.1, on through to the latest 4.x versions, free for the taking. All versions prior to 4 will happily build code for PowerPC.
What is it you think they're preventing anyone from doing again?
llvm-gcc doesn't compile many projects correctly, including gcc itself (as of Xcode 4.2 there were reports that it's not possible to compile a gcc cross-compiler using llvm-gcc). Hopefully there have been improvements in this regard.
Still, anyone who needs the real gcc will have to install it through some other means.