UsingTheRightCompiler

[Dominik Reichardt]

With xcode 4.2 (or 4.1 or 4.0) Apple did away with gcc and only brings llvm-gcc and clang. By default MacPorts uses the compiler that comes with Xcode and only uses a macports compiler when the xcode compilers don't work at all. And when people are using Lion, they are likely to have Xcode 4.x installed.
That said, pango installs fine via default macports for me. And clang works fine on the projects I compile on my own.

Dom

Am 16.04.2012 um 08:08 schrieb Jan Stary <hans at stare.cz>:

> On Apr 15 23:04:58, Jeff Singleton wrote:
>> Yes I am referring to the Wiki article found here...
>> http://trac.macports.org/wiki/UsingTheRightCompiler
>> 
>> I just can't say a lot for Clang.  I have mentioned this before.  I have
>> taken many suggestions.  Tried Tried and Tried some more to like Clang.
>> 
>> I just can't do it.
>> 
>> Its ugly.  It causes more problems between ports that depend on one
>> another, yet some are built with Clang, other built with GCC.
>> 
>> I am simply fed up with Clang and I don't really want to use it anymore.
>> *libtool: link: /usr/bin/clang  -o .libs/pango-basic-coretext.so
> 
> I must be missing something, but why do you even have
> clang installed on your system?
> 
> _______________________________________________
> macports-users mailing list
> macports-users at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo.cgi/macports-users