On Nov 24, 2012, at 05:00, [email protected] wrote: > Revision: 100023 > https://trac.macports.org/changeset/100023 > Author: [email protected] > Date: 2012-11-24 03:00:15 -0800 (Sat, 24 Nov 2012) > Log Message: > ----------- > codeblocks: use gcc not clang (#35072) > > Modified Paths: > -------------- > trunk/dports/devel/codeblocks/Portfile > > Modified: trunk/dports/devel/codeblocks/Portfile > =================================================================== > --- trunk/dports/devel/codeblocks/Portfile 2012-11-24 09:56:38 UTC (rev > 100022) > +++ trunk/dports/devel/codeblocks/Portfile 2012-11-24 11:00:15 UTC (rev > 100023) > @@ -4,7 +4,7 @@ > > name codeblocks > version 10.05 > -revision 1 > +revision 2 > platforms darwin freebsd > categories devel aqua x11 > maintainers afb > @@ -24,6 +24,11 @@ > sha1 b7697f512de69ad731f0febac4b91bb6c605fa57 \ > rmd160 a1b4e93f4cc41ae6b7fd955689dae8648f0fd2f9 > > +# apparently only works with gcc > +if {${configure.compiler} == "clang"} { > + configure.compiler gcc > +} > +
"gcc" is an alias, not a specific compiler, so it should not be used in configure.compiler. On latest Xcode for example, "gcc" is a symlink to llvm-gcc. What you probably should write is: compiler.blacklist clang And add a comment above that, referencing the upstream bug port about the problem. If there isn't one yet, please file one; blacklisting compilers is meant to be a temporary measure. _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo/macports-dev
