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
Message-Id: <199907160346.WAA05998@mercury.xraylith.wisc.edu>
To: Chris Faylor <cgf AT cygnus DOT com>
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 
In-Reply-To: Your message of "Thu, 15 Jul 1999 13:29:26 EDT."
             <19990715132926 DOT A1102 AT cygnus DOT com> 
Date: Thu, 15 Jul 1999 22:46:49 -0500
From: Mumit Khan <khan AT xraylith DOT wisc DOT EDU>

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?

Regards,
Mumit