From mboxrd@z Thu Jan  1 00:00:00 1970
From: Eli Zaretskii <eliz@delorie.com>
To: chastain@cygnus.com
Cc: gdb@sourceware.cygnus.com
Subject: Re: GDB compile problem.
Date: Mon, 26 Feb 2001 11:51:00 -0000
Message-id: <200102261950.OAA24493@indy.delorie.com>
References: <200102261847.KAA05097@bosch.cygnus.com>
X-SW-Source: 2001-02/msg00377.html

> Date: Mon, 26 Feb 2001 10:47:23 -0800
> Cc: gdb@sourceware.cygnus.com
> 
> > PS. How do you even check that the preprocessor ``works''?
> 
> That part is easy.  You preprocess this file:
> 
>   int i;
> 
> ... and check that the output contains the line "int i"

Then CPP="sed ''" will pass your test ;-)

> I would definitely draw the line so that "CPP" is inside it.  "CPP" really
> is an ambiguous word and prone to misunderstanding; in my opinion, CC and
> LN_S aren't.  Even the Gnu Compiler Collection acknowledges "FILE.cpp"
> as an extension for C++ source code.
> 
> > Moreover, these variables are there _precisely_ so the end-user could set 
> > them to whatever she pleases without being subject to Autoconf's 
> > scrutiny, for those cases where Autoconf isn't smart enough.
> 
> I definitely accept this point.
> 
>   User: my $FOO is named "bar" ...
>   Software: your $FOO does not fit my pre-conceptions ...
> 
> That would not be very Unix-like.

Yes.

The question is, how to check the value of $CPP so that the test won't
be too viral...