This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
Re: Why warn about #include_next in system headers?
At 00:38 2001-02-06, Neil Booth wrote:
>Franz Sirl wrote:-
>
> > Hmm, does -I/usr/include qualify for 2)?
>
>Obviously it shouldn't. gcc -v gives for me:-
>
>#include "..." search starts here:
>#include <...> search starts here:
> /usr/local/include
> /usr/local/lib/gcc-lib/i586-pc-linux-gnu/2.97/include
> /usr/local/i586-pc-linux-gnu/include
> /usr/include
>
>I don't get the warning, and if the file is just #include <limits.h> I get
>
>. /usr/local/lib/gcc-lib/i586-pc-linux-gnu/2.97/include/limits.h
>.. /usr/local/lib/gcc-lib/i586-pc-linux-gnu/2.97/include/syslimits.h
>... /usr/local/lib/gcc-lib/i586-pc-linux-gnu/2.97/include/limits.h
>.... /usr/include/limits.h <<<<< This is the one for you, no?
>..... /usr/include/features.h
>...... /usr/include/sys/cdefs.h
>...... /usr/include/gnu/stubs.h
>..... /usr/include/bits/posix1_lim.h
>...... /usr/include/bits/local_lim.h
>....... /usr/include/linux/limits.h
>..... /usr/include/bits/posix2_lim.h
>
>Are you different to the above in a relevant way? Has this just
>appeared recently for you? Apart from all the random configure /
>Makefile stuff that's been happening recently, nothing has changed to
>affect this that I'm aware of.
Aaaaarrrrggghhh! The invocation uses -pedantic :-(. I must have looked at
the command line a dozen times and just didn't see it yesterday, maybe it
was too late already...
Sorry for the confusion,
Franz.