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 09:20:18 -0500
Message-Id:	<199902161420.JAA32394@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:	<19990216004811.A12358@cygnus.com> (message from Christopher
	Faylor on Tue, 16 Feb 1999 00:48:11 -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> <199902160532 DOT AAA30182 AT envy DOT delorie DOT com> <19990216004811 DOT A12358 AT cygnus DOT com>

> Why would we use the installed cross-compiler's headers?

Because gcc may pick up <stdio.h> there by default when we build, say,
mount.exe

> If someone has winsup installed without newlib then this will just
> work.

If someone has winsup installed without newlib, they can't build
cygwin1.dll - can they?

> If they don't then they should keep everything up to date.
> ../newlib/lib[cm].a should be up to date with respect to the
> headers.

That *is* the problem.

- Raw text -