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 From: Christopher Faylor Message-ID: <19990216200912.N15986@cygnus.com> Date: Tue, 16 Feb 1999 20:09:12 -0500 To: DJ Delorie Cc: khan AT xraylith DOT wisc DOT edu, cygwin-developers AT sourceware DOT cygnus DOT com Subject: Re: tiny winsup config patch References: <199902160016 DOT TAA28214 AT envy DOT delorie DOT com> <19990216002959 DOT B12208 AT cygnus DOT com> <199902160532 DOT AAA30182 AT envy DOT delorie DOT com> <19990216004811 DOT A12358 AT cygnus DOT com> <199902161420 DOT JAA32394 AT envy DOT delorie DOT com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93i In-Reply-To: <199902161420.JAA32394@envy.delorie.com>; from DJ Delorie on Tue, Feb 16, 1999 at 09:20:18AM -0500 On Tue, Feb 16, 1999 at 09:20:18AM -0500, DJ Delorie wrote: >> Why would we use the installed cross-compiler's headers? > >Because gcc may pick up there by default when we build, say, >mount.exe > >> If someone has winsup installed without newlib then this will just >> work. Ok. We're going around and around then. It seems that the right thing to do as far as the net is concerned is to just include ../../newlib/libc/include, etc. then, as Mumit proposed. Cygnus-specific release problems are another matter... cgf