On Sat, May 12, 2012 at 11:41:14PM -0500, Ryan Schmidt wrote: > > On May 12, 2012, at 14: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? > > Can you give an example of such a port?
I was just rebuilding molmol (which uses gcc without a path in its Makefile). The error messages issued were from llvm-gcc. I thought MacPorts under Xcode 4.3.2 should be defaulting instances of unpathed gcc to clang, no? Jack _______________________________________________ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev