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 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?
More generally, let me say that I'm just now overhauling the way -I
and friends work for other reasons, and I'm happy to implement
whatever behavior people actually want. However, y'all have to hash
out what the behavior should be and tell me, first. I don't have an
opinion here and I don't particularly care about the debate. Just
find something everyone likes, then tell me what it is, and I'll write
the code.
Well, I do have a meta-opinion, which is that a solution that is not
acceptable to people in *all* of the camps of GCC users isn't gonna
fly. Make it work for BSD, make it work for Linux, make it work for
native use on proprietary operating systems, make it work for cross
compiles to embedded targets, I'm sure there are more.
zw