[51027] trunk/dports/devel

[Toby Peterson]

On Fri, May 15, 2009 at 14:03, Ryan Schmidt <ryandesign at macports.org> wrote:
>
> On May 15, 2009, at 13:55, toby at macports.org wrote:
>
>> Revision: 51027
>>          http://trac.macports.org/changeset/51027
>> Author:   toby at macports.org
>> Date:     2009-05-15 11:55:33 -0700 (Fri, 15 May 2009)
>> Log Message:
>> -----------
>> libmowgli 0.7.0
>
> [snip]
>
>> +# Why do we set a bogus CPP value, anyway?
>> +configure.cpp
>
> What is bogus about it? Are you referring to this idea:
>
> http://lists.macosforge.org/pipermail/macports-dev/2009-April/008148.html
>
> If so, let's discuss it (on the list, not as comments in portfiles :)). Thus
> far, nobody offered any input on my message so nothing has happened yet.

It should be "gcc -E". To illustrate the problem:

% touch foo.c bar.c
% gcc -E foo.c bar.c
# 1 "foo.c"
# 1 "<built-in>"
# 1 "<command line>"
# 1 "foo.c"
# 1 "bar.c"
# 1 "<built-in>"
# 1 "<command line>"
# 1 "bar.c"
% cpp foo.c bar.c
%

Most configure scripts will just use "$CC -E" if CPP isn't specified
explicitly, which is what I'm taking advantage of there. And, if you
run nearly any configure script with no special setup:

checking how to run the C preprocessor... gcc -E

I'd vote for just never setting CPP, but setting it to "$CC -E" would
probably work too.

- Toby