This is the mail archive of the
gcc@gcc.gnu.org
mailing list for the GCC project.
Re: New cpp0 warning in 3.1 breaks configure (autoconf)
On Tue, Jun 11, 2002 at 05:59:36PM -0700, Zack Weinberg wrote:
> On Tue, Jun 11, 2002 at 08:03:12PM -0400, Daniel Jacobowitz wrote:
> > >
> > > We can recover from parsing errors and continue. Why can't we recover from
> > > command-line user errors and continue?
> >
> > Heck, the warning I want to get out of all this are includes of what
> > STANDARD_INCLUDE_DIR and the equivalent for /usr/local/include would be
> > in a native compiler, when using a cross compiler. Readline in the GCC
> > source tree does this sometimes, for instance.
>
> I can't figure out what this means. The warning I want to get out of
> this is includes? Huh?
I must be getting tired...
The case that I very much want to see a warning in is:
powerpc-unknown-linux-gcc -I/usr/include foobar.c
Ditto for -I/usr/local/include.
These generally come from -I$(prefix)/include, which is an install
directory properly and not a build directory. This is an amazingly
common error, and my local patch to warn about it (a stupid patch,
which just hardcodes /usr and /usr/local) has been very successful.
--
Daniel Jacobowitz Carnegie Mellon University
MontaVista Software Debian GNU/Linux Developer