Some build systems do ignore the compiler that you ask for in the configure environment. You might have to patch it if that's what's happening.
On 2012-9-18 22:54 , James George wrote: > Hi Josh, > > We did that I think. Though, from memory, it was still showing clang > use in the logs. I shall double check. > > Cheers! > > On 18/09/12 8:52 PM, Joshua Root wrote: >> On 2012-9-18 22:06 , James George wrote: >>> Hi all, >>> >>> I tried to do this, though quite likely got it wrong. I set the >>> configure.cc and configure.cxx in the port file to use /usr/bin >>> llvm-gcc-4.2 and llvm-gxx-4.2 but this resulted in the build failing. I >>> suspect this may be due to changes in (deprecated) APIs or "improved" >>> compiler checks that some old myth code uses but more investigation is >>> required. >>> >>> Is there is a better way to config the port to use the llvm-g?? variants >>> and not choose clang? >> See <https://trac.macports.org/wiki/ProblemHotlist#compiler>. In the >> case that you just want to not use clang (as opposed to selecting a >> specific compiler), you'd add 'compiler.blacklist clang' to the portfile. >> >> - Josh > _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo/macports-dev
