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:	Fri, 16 Jul 1999 10:54:06 -0400
From:	Chris Faylor <cgf AT cygnus DOT com>
To:	Mumit Khan <khan AT xraylith DOT wisc DOT EDU>
Cc:	Egor Duda <deo AT logos-m DOT ru>, "Suhaib M. Siddiqi" <ssiddiqi AT ipass DOT net>,
	cygwin-developers <cygwin-developers AT sourceware DOT cygnus DOT com>
Subject:	Re: gcc-2.95/ July 5 snapshot
Message-ID:	<19990716105406.A644@cygnus.com>
References:	<19990715132926 DOT A1102 AT cygnus DOT com> <199907160346 DOT WAA05998 AT mercury DOT xraylith DOT wisc DOT edu>
Mime-Version:	1.0
X-Mailer:	Mutt 0.95.3i
In-Reply-To:	<199907160346.WAA05998@mercury.xraylith.wisc.edu>; from Mumit Khan on Thu, Jul 15, 1999 at 10:46:49PM -0500

On Thu, Jul 15, 1999 at 10:46:49PM -0500, Mumit Khan wrote:
>Chris Faylor <cgf AT cygnus DOT com> writes:
>> Just to reiterate: Everyone should be building their stuff in a separate
>> directory, i.e., don't build winsup in the same directory as the winsup
>> sources.
>> 
>
>That and the fact that folks should also download the newest newlib
>from the corresponding cygwin-src-1999xxxx.tar.gz file, and not use
>the installed newlib.
>
>I've had 4-5 bug reports from users who've had trouble with the compiler
>side, and all because they downloaded winsup-* packages, and not the
>cygwin-src-* packages. In turn, the build process used the installed
>newlib, which is usually from Cygwin-b20.1 days and quite a bit out of
>step with what winsup expects.
>
>This is what I do: 
>
>- if the latest version comes in cygwin-src-*, get that. Done.
>- if the latest version comes only winsup-*, I get the cygwin-src-*
>  the precedes it, unpack, and replace the winsup with the latest
>  one.
>
>This sound reasonable?

Absolutely.

cgf

- Raw text -