On Feb 15, 2012, at 9:05 AM, Ryan Schmidt <[email protected]> wrote:
> > On Feb 14, 2012, at 23:20, Jeremy Huddleston wrote: > >> On Feb 14, 2012, at 11:50 AM, Jeremy Lavergne wrote: >> >>>> Works for me here... where is that "no_default_gcc" coming from? >>> >>> Comes from our page detailing that the build script isn't using the >>> compiler MacPorts set e.g., "gcc": >>> http://trac.macports.org/wiki/UsingTheRightCompiler >>> >>> The page instructs on detect blind use of "gcc" by setting up a dummy gcc >>> in MacPorts' binpath. >> >> Well I get: >> >> checking for cpp... /usr/bin/cpp > > Jeremy Lavergne is only seeing the issue because he has followed the > instructions at the bottom of the wiki page UsingTheRightCompiler that are > designed to expose these kinds of issues. The output you showed suggests that > you have not followed those instructions, therefore you don't see the issue. Right, but you stripped off the rest of my reply in which I pointed out that there is no ${configure.cpp} set to begin with, so the issue is not that the port isn't following ${configure.cpp}. The issue is that ${configure.cpp} isn't set, and we should figure out a way to fix that in base. _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
