It's been ages that the 10.6 default (gcc 4.2) can no longer build clang. I've never considered that to be MacPort's fault, given the errors in the make log, so I never filed a ticket ...
BTW, the build process using gcc 4.8 finally went through, when I invoke make without -j from within the MP build directory. I did that to try and get the exact command that failed. My impression is that there may have been an issue with the parallelised build process (I use the default setting, i.e -j0). My MBP has 8Gb, but I also have lots of windows open in Chrome, so I may have hit a process cap. I also saw kernel log entries about emergency paging; with hindsight they could well be related. R On 12 Jan 2014, at 08:37, Ryan Schmidt <[email protected]> wrote: > > On Jan 11, 2014, at 17:30, René J.V. Bertin wrote: > >> I'm trying to build clang-3.4 on a 10.6.8 host (x86_64), to replace >> clang-mp-3.3 . llvm-3.4 built fine using >> configure.compiler=macports-gcc-4.7, but clang-3.4 is giving me a headache. >> Even using port install clang-3.4 configure.compiler=macports-gcc-4.8, the >> build fails, with the attached logfile. > > We do not want you to have to change the compiler when compiling a port. What > happens when you use the compiler MacPorts chose? Did you file a ticket? > _______________________________________________ macports-users mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-users
