This is the mail archive of the gcc@gcc.gnu.org mailing list for the GCC project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: New cpp0 warning in 3.1 breaks configure (autoconf)

On Wednesday 12 June 2002 06:35, Alexandre Oliva wrote:
> >
> > Well, the problem stemmed from /usr/local/include in the first place.
> > Entirely different beast.
> >
> > See what I mean about different assumptions ?
>
> Same difference to me.  -I/usr/local/include is wrong too, since
> /usr/local/include is a system header directory.  -Iing it may not be
> as evil as /usr/include, but it's still a bad idea IMO.

There more. If for example /usr/X11R6/include is specified in C_INCLUDE_PATH
(or accordingly CPLUS_INCLUDE_PATH for C++) it is also treated as system 
header directory. So I'm getting warning when -I/usr/X11R6/include is 
specified in command line. Perhaps it would be better to  limit this warning 
to list of system include directories before adding ones from C_INCLUDE_PATH 
or CPLUS_INCLUDE_PATH (or even to ones which are processed by fixincludes)

Andris
Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]