Mailing-List: contact cygwin-developers-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT cygwin DOT com>
List-Help: <mailto:cygwin-developers-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT cygwin DOT com
Delivered-To: mailing list cygwin-developers AT cygwin DOT com
Date: Thu, 14 Nov 2002 22:08:46 +0000
Message-ID: <5568-Thu14Nov2002220846+0000-starksb@ebi.ac.uk>
From: David Starks-Browning <starksb AT ebi DOT ac DOT uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
To: cygwin-developers AT sources DOT redhat DOT com
Subject: Re: Fwd: Re: later w32api package required to build cygwin
In-Reply-To: <3DD3ED09.8050807@netscape.net>
References: <3DD3E347 DOT 60703 AT yahoo DOT com>
	<3DD3EB49 DOT 6000306 AT netscape DOT net>
	<3DD3ED09 DOT 8050807 AT netscape DOT net>

On Thursday 14 Nov 02, Nicholas Wourms writes:
> Nicholas Wourms wrote:
> > 
> > IIRC, the new gcc has started to ignore system directory overrides (in 
> > addition to barfing out that stupid message).  Using -isystem instead of 
> > -I for including the local w32api dir might be the solution here, 
> > although I was just lazy and copied the header over to the system dir.
> 
> After investigating a few minutes, I found that in 
> Makefile.common changing:
> 
> w32api_include:=-I$(w32api_source)/include
> 
> to
> 
> w32api_include:=-isystem $(w32api_source)/include

No, something else is going on.

In fact, the right "-isystem $(w32api_source)/include" appears in the
c++ command line, by virtue of the FLAGS_FOR_TARGET definition in
configure.in.

However, the c++ front-end also feeds "-isystem /usr/include/w32api"
to cc1plus.exe, before the cvs one in the Makeile.  This screws us up.

Is this coming from the specs file?  If "-isystem /usr/include/w32api"
has to be there (because gcc won't ever find it otherwise?), then a
workaround for building Cygwin is to replace -isystem with -I in
FLAGS_FOR_TARGET.  At least, I think that will work.  I'll try it now.

Regards,
David