This is the mail archive of the
mailing list for the GDB project.
Re: GDB compile problem.
- To: chastain at cygnus dot com
- Subject: Re: GDB compile problem.
- From: Eli Zaretskii <eliz at delorie dot com>
- Date: Mon, 26 Feb 2001 14:50:52 -0500 (EST)
- CC: gdb at sourceware dot cygnus dot com
- References: <200102261847.KAA05097@bosch.cygnus.com>
- Reply-to: Eli Zaretskii <eliz at is dot elta dot co dot il>
> Date: Mon, 26 Feb 2001 10:47:23 -0800
> Cc: email@example.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.
The question is, how to check the value of $CPP so that the test won't
be too viral...