This is the mail archive of the gcc-bugs@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]

Re: Why warn about #include_next in system headers?

To: Franz Sirl <Franz dot Sirl-kernel at lauterbach dot com>
Subject: Re: Why warn about #include_next in system headers?
From: Alexandre Oliva <aoliva at redhat dot com>
Date: 05 Feb 2001 23:56:49 -0200
Cc: Neil Booth <neil at daikokuya dot demon dot co dot uk>, gcc-bugs at gcc dot gnu dot org
Organization: GCC Team, Red Hat
References: <01020523112001.26861@enzo.bigblue.local><20010205231508.C3104@daikokuya.demon.co.uk><01020600221104.26861@enzo.bigblue.local>

On Feb  5, 2001, Franz Sirl <Franz.Sirl-kernel@lauterbach.com> wrote:

>> 2) For some reason CPP doesn't think the file it appears in is a
>> system header.

> Hmm, does -I/usr/include qualify for 2)?

Yep.  -isystem is the way to tell GCC to search a certain directory as
a system header.  -I is for non-system headers.

-- 
Alexandre Oliva   Enjoy Guarana', see http://www.ic.unicamp.br/~oliva/
Red Hat GCC Developer                  aoliva@{cygnus.com, redhat.com}
CS PhD student at IC-Unicamp        oliva@{lsd.ic.unicamp.br, gnu.org}
Free Software Evangelist    *Please* write to mailing lists, not to me

Follow-Ups:
- Re: Why warn about #include_next in system headers?
  - From: Neil Booth

References:
- Why warn about #include_next in system headers?
  - From: Franz Sirl
- Re: Why warn about #include_next in system headers?
  - From: Neil Booth
- Re: Why warn about #include_next in system headers?
  - From: Franz Sirl

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