On Feb 16, 2012, at 22:08, Joshua Root wrote:
> On 2012-2-17 07:10 , Jeremy Huddleston wrote:
>>
>> 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.
>
> I imagine whoever set up the values for clang just couldn't figure out
> anything sensible to set cpp to, since the available /usr/bin/*cpp*
> tools all invoke gcc or llvm-gcc.
Wouldn't "${configure.cc} -E" be a sensible value?
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
