macports 2.0.4 breaks the usage of clang on Xcode 4.3.2

[Jeremy Lavergne]

Ooops, forgot to reply to the list.

> I also see the same breakage in MacPorts 2.0.4 when built from sources in
> MacPorts-2.0.4.tar.bz2 using...
> 
> ./configure && make && sudo make install
> 
> under Xcode 4.3.2 on Lion. When executing 'sudo port -v selfupdate', port is blindly
> using llvm-gcc-4.2 rather than the expected clang compiler at the point it is
> starting to build again from sources. I strongly suspect this breakage is somehow
> due to the new binary package support. Is there any way to disable that feature?
> I don't see any obvious options to do that listed in /opt/local/etc/macports/macports.conf.

Python and Perl record what compiler was used to build them, which then influences many packages that blindly go with those same values. The workaround for this is to rebuild python/perl from source, then subsequent perl/python packages should pick up that compiler.

-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 8796 bytes
Desc: not available
URL: <http://lists.macosforge.org/pipermail/macports-dev/attachments/20120408/6814ddcf/attachment.bin>