Mail Archives: djgpp-workers/2001/02/06/02:38:13
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.
Comments?
------- Start of forwarded message -------
Mailing-List: contact gcc-bugs-help AT gcc DOT gnu DOT org; run by ezmlm
Precedence: bulk
List-Unsubscribe: <mailto:gcc-bugs-unsubscribe-eliz=is DOT elta DOT co DOT il AT gcc DOT gnu DOT org>
List-Archive: <http://gcc.gnu.org/ml/gcc-bugs/>
List-Post: <mailto:gcc-bugs AT gcc DOT gnu DOT org>
List-Help: <mailto:gcc-bugs-help AT gcc DOT gnu DOT org>
Sender: gcc-bugs-owner AT gcc DOT gnu DOT org
To: Franz Sirl <Franz DOT Sirl-kernel AT lauterbach DOT com>
Cc: Neil Booth <neil AT daikokuya DOT demon DOT co DOT uk>, gcc-bugs AT gcc DOT gnu DOT org
Subject: Re: Why warn about #include_next in system headers?
From: Alexandre Oliva <aoliva AT redhat DOT com>
Organization: GCC Team, Red Hat
Date: 05 Feb 2001 23:56:49 -0200
In-Reply-To: <01020600221104 DOT 26861 AT enzo DOT bigblue DOT local>
User-Agent: Gnus/5.0808 (Gnus v5.8.8) XEmacs/21.1 (Cuyahoga Valley)
Content-Type: text/plain; charset=us-ascii
Content-Length: 610
On Feb 5, 2001, Franz Sirl <Franz DOT Sirl-kernel AT lauterbach DOT 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
------- End of forwarded message -------
- Raw text -