On Dec 8, 2012, at 20:12, [email protected] wrote: > Revision: 100350 > https://trac.macports.org/changeset/100350 > Author: [email protected] > Date: 2012-12-08 18:12:30 -0800 (Sat, 08 Dec 2012) > Log Message: > ----------- > group/crossgcc-1.0: > Use a single tarball for gcc sources (default distribution since 4.7.x, also > available for 4.6.x). > Compilation with llvm-gcc-4.2 is supposed to work with Xcode >= 4.3. > Parallel building is already the default. > > Modified Paths: > -------------- > trunk/dports/_resources/port1.0/group/crossgcc-1.0.tcl
> # http://trac.macports.org/ticket/29104 > - if {${configure.compiler} == "llvm-gcc-4.2"} { > - configure.compiler clang > + # http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48301 > + if {[vercmp ${xcodeversion} 4.3] < 0} { > + compiler.blacklist llvm-gcc-4.2 > } I was going to ask if you could use the compiler_blacklist_versions portgroup to check the build number of llvm-gcc-4.2 instead of the Xcode version, since it is possible for users to mismatch those. But according to the information in https://trac.macports.org/wiki/XcodeVersionInfo and http://en.wikipedia.org/wiki/Xcode#Toolchain_Versions the llvm-gcc-4.2 build number has been 5658 ever since Xcode 3.2.3, so that doesn't help us. Meanwhile the llvm build number has allegedly increased. Is that the build number we should be checking for llvm-gcc-4.2 in the portgroup? If so how do I obtain that number? Our wiki page says I should be able to get it from `llvm-gcc --version`, but I don't: $ llvm-gcc --version | head -1 llvm-gcc (GCC) 4.2.1 (Based on Apple Inc. build 5658) (LLVM build) _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo/macports-dev
