On 2012-5-13 05:48 , Jack Howarth wrote: > Is anyone else finding that a clean install of MacPorts 2.1.0-rc2 from > the source tarball on 10.7.4 with Xcode 4.3.2 results in the installed > MacPorts building packages with llvm-gcc rather than clang? Is there a quick > fix to hack port to properly default back to clang on such a configuration?
In fact there is such a thing: <https://trac.macports.org/ticket/30008> However, I see the default being clang as expected. The default compiler is based on $xcodeversion, which is derived from the output of `xcodebuild -version`, and controls the value of CC, CXX etc. during the configure step. Of course, whether any given port will obey those environment variables is a different question. Also, some ports of course change configure.compiler for various reasons. - Josh _______________________________________________ macports-users mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-users
