This is the mail archive of the
mailing list for the GCC project.
[email@example.com: cccp.c::print_help() not called.]
- To: gcc at gcc dot gnu dot org
- Subject: [firstname.lastname@example.org: cccp.c::print_help() not called.]
- From: "Bradley M. Kuhn - Assistant to RMS" <rms-assist at gnu dot org>
- Date: Sat, 1 Apr 2000 21:40:37 -0500
This message was originally sent directly to RMS. He asked me to forward
such messages along to <email@example.com>.
------- Start of forwarded message -------
Date: Sat, 25 Mar 2000 10:09:21 -0500 (EST)
From: "Eric R. Buddington" <firstname.lastname@example.org>
Subject: cccp.c::print_help() not called.
Content-Type: TEXT/PLAIN; charset=US-ASCII
A while ago I was failing to fix a problem of autoconf wherein ./configure
did macro substitution with cpp, which had undesired, built-in defines.
I just now discovered the 'cpp -u' switch, which does what I want, but
doesn't appear in 'cpp --help'.
The cpp in the *build* directory gives the expected help message (from
cccp.c), but the xcpp that gets installed seems to be a different beast
entirely (basically a teraked gcc, according to the Makefile). I assume
that cccp.c is just for bootstrapping?
I propose that cccp.c::print_help() and cpp.c::display_help get moved into
cppspec.c and gccspec.c, respectively, in order to give more relevant
help for whatever program is invoked. Do you agree?
North Adams, MA
------- End of forwarded message -------