Mailing-List:	contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Unsubscribe:	<mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT sourceware DOT cygnus DOT com>
List-Subscribe:	<mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive:	<http://sourceware.cygnus.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help:	<mailto:cygwin-help AT sourceware DOT cygnus DOT com>,
	<http://sourceware.cygnus.com/ml/#faqs>
Sender:	cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To:	mailing list cygwin AT sourceware DOT cygnus DOT com
Message-ID:	<37C98524.6A62A265@ece.gatech.edu>
Date:	Sun, 29 Aug 1999 15:08:20 -0400
From:	"Charles S. Wilson" <cwilson AT ece DOT gatech DOT edu>
X-Mailer:	Mozilla 4.6 [en] (WinNT; U)
X-Accept-Language:	en
MIME-Version:	1.0
To:	cygwin AT sourceware DOT cygnus DOT com
Subject:	New snapshots and old binaries

I want to update my cygwin environment to the newer snapshots, for two
reasons:

1) to make sure that perl5.6(pre) will build and execute properly with
cygwinB21(pre) while there's still time to fix perl5.6 / cygwinB21.
2) to use Sergey's port of ssh-2.0.13

My question:

If I do switch over to the newer snapshots, by unpacking cygwin-inst-*
over my current setup and fixing gcc-2.95 using Mumit's
gcc-2.95-dev-ss.tar.gz, how badly will this break my cygwin environment?
(I know that the i586-cygwin32 directory has changed its name to
i586-pc-cygwin32, but that's fairly minor from a user perspective).

I have Arlindo daSilva's X11 libs (for B20) installed, Andy Piper's
/usr/local (for B20), gcc-2.95, Sergey's remote package, libmysql,
msql-2.0.5, and a number of binaries that I have compiled against B20.1.

Will I need to recompile ALL of these libraries and executables before
my system returns to "normal", or what?

--Chuck





--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -