On Jul 20, 2011, at 11:26, Jeremy Huddleston wrote:
> If both clang and llvm-gcc-4.2 fail to build, you can try falling back on
> gcc-4.2. If gcc-4.2 works, you can fall back on it, but we recommend you try
> to fix the problem. A common reason for both llvm-gcc and clang failing
> where gcc-4.2 works is buggy inline asm. If you are unfamiliar with x86 asm,
> please file a bug with upstream developers and put a reference to it in the
> Portfile.
>
> if {${configure.compiler} == "clang" ||
> ${configure.compiler} == "llvm-gcc-4.2"} {
> configure.compiler gcc-4.2
> if {![file executable ${configure.cc}]} {
> depends_build-append port:apple-gcc42
> configure.compiler apple-gcc-4.2
> }
> }
Remind me, what is the purpose for the "if {![file executable
${configure.cc}]}" block? On what systems would /usr/bin/gcc-4.2 not exist? I'm
only coming up with Tiger, but nobody would request llvm-gcc-4.2 or clang on
Tiger either.
_______________________________________________
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
