Delivered-To:	listarch-cygwin-developers AT sourceware DOT cygnus DOT com
Mailing-List:	contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender:	cygwin-developers-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin-developers AT sourceware DOT cygnus DOT com
Date:	Tue, 16 Feb 1999 00:32:36 -0500
Message-Id:	<199902160532.AAA30182@envy.delorie.com>
From:	DJ Delorie <dj AT delorie DOT com>
To:	cgf AT cygnus DOT com
CC:	khan AT xraylith DOT wisc DOT edu, cygwin-developers AT sourceware DOT cygnus DOT com
In-reply-to:	<19990216002959.B12208@cygnus.com> (message from Christopher
	Faylor on Tue, 16 Feb 1999 00:29:59 -0500)
Subject:	Re: tiny winsup config patch
References:	<199902160016 DOT TAA28214 AT envy DOT delorie DOT com> <Pine DOT SUN DOT 3 DOT 93 DOT 990215231806 DOT 23933A-100000 AT modi DOT xraylith DOT wisc DOT edu> <19990216002959 DOT B12208 AT cygnus DOT com>

> I don't think that it should be the function of winsup's configure to
> ensure that the build environment which surrounds it is ok.  Cygnus
> provides a build environment.  If you don't want to use it, then you
> take your lumps.

I think winsup's configure needs to know if it's building with a local
version of newlib et al, and use it directly if so, rather that use
newlib's libc.a (via libcygwin.a) but the installed cross compiler's
headers.

> If you're going to check for ../newlib, then you should check for
> ../libiberty and ../include, too.  Do we really want to go down that
> path?

For building winsup and winsup/utils, I think we must.  That's the
library we link against (via libcygwin.a), those should be the headers
we include.

- Raw text -