Message-ID:	<20010207171301.1212.qmail@lauras.lt>
From:	"Laurynas Biveinis" <lauras AT softhome DOT net>
Date:	Wed, 7 Feb 2001 19:13:01 +0200
To:	djgpp-workers AT delorie DOT com
Cc:	DJ Delorie <dj AT delorie DOT com>
Subject:	Re: [aoliva AT redhat DOT com: Re: Why warn about #include_next in system headers?]
Mail-Followup-To:	djgpp-workers AT delorie DOT com, DJ Delorie <dj AT delorie DOT com>
References:	<200102062053 DOT PAA21029 AT envy DOT delorie DOT com> <Pine DOT SUN DOT 3 DOT 91 DOT 1010207081617 DOT 2148H-100000 AT is>
Mime-Version:	1.0
User-Agent:	Mutt/1.3.12i
In-Reply-To:	<Pine.SUN.3.91.1010207081617.2148H-100000@is>; from eliz@is.elta.co.il on Wed, Feb 07, 2001 at 08:18:35AM +0200
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 Wed, Feb 07, 2001 at 08:18:35AM +0200, Eli Zaretskii wrote:
> > Does -isystem disable any warnings?

It doesn't. There is an option -Wsystem-headers to do it, but
it isn't on by default.

> I don't know.  Perhaps Laurynas and Andris could tell.

I think we should use -isystem if this is available. I can't
think of anything wrong about it right now.

Laurynas

- Raw text -