delorie.com/archives/browse.cgi | search |
Date: | Wed, 7 Feb 2001 08:18:35 +0200 (IST) |
From: | Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> |
X-Sender: | eliz AT is |
To: | DJ Delorie <dj AT delorie DOT com> |
cc: | djgpp-workers AT delorie DOT com |
Subject: | Re: [aoliva AT redhat DOT com: Re: Why warn about #include_next in system headers?] |
In-Reply-To: | <200102062053.PAA21029@envy.delorie.com> |
Message-ID: | <Pine.SUN.3.91.1010207081617.2148H-100000@is> |
MIME-Version: | 1.0 |
Reply-To: | djgpp-workers AT delorie DOT com |
Errors-To: | nobody AT delorie DOT com |
X-Mailing-List: | djgpp-workers AT delorie DOT com |
X-Unsubscribes-To: | listserv AT delorie DOT com |
On Tue, 6 Feb 2001, DJ Delorie wrote: > > The below seems to indicate that we need to change the library > > makefile's to use -isystem instead of -I. Since -isystem is supported > > even by GCC 2.7.2, it sounds safe. > > Does -isystem disable any warnings? I don't know. Perhaps Laurynas and Andris could tell. The reason I suggested to use -isystem is that CPP doesn't treat directories mentioned with -I as system headers, so all kinds of tricks we might want to do there (some of them were discussed here in the past) won't work, or won't DTRT.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |