On Mar 14, 2013, at 12:20, Lawrence Velázquez wrote: > On Mar 14, 2013, at 9:38 AM, [email protected] wrote: > >> Revision: 104065 >> https://trac.macports.org/changeset/104065 >> Author: [email protected] >> Date: 2013-03-14 06:38:50 -0700 (Thu, 14 Mar 2013) >> Log Message: >> ----------- >> kytea: update to 0.4.4; use g++ instead of clang. >> >> Modified Paths: >> -------------- >> trunk/dports/textproc/kytea/Portfile > >> +compiler.blacklist clang > > Simply blacklisting "clang" still allows the use of Clang from MacPorts, as > well as DragonEgg. If you want to blacklist Clang entirely, you'll have to > add the macports-clang* compilers. Alternatively, if you really intend to > only allow GCC, you should use compiler.whitelist instead. > > A list of valid compiler names is on the wiki. > https://trac.macports.org/wiki/UsingTheRightCompiler#configure-compiler
More importantly: please explain (via comment in the port) why you're blacklisting clang and what you're doing to fix it (i.e. a link to the upstream bug report). The Xcode 4.6 release notes state that it is the last major version of Xcode that will offer any compilers other than clang, so getting ports to compile with clang is important. _______________________________________________ macports-dev mailing list [email protected] https://lists.macosforge.org/mailman/listinfo/macports-dev
