delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/1999/08/02/11:58:31

Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>,
<http://sourceware.cygnus.com/ml/#faqs>
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
From: Chris Faylor <cgf AT cygnus DOT com>
Date: Mon, 2 Aug 1999 11:56:30 -0400
To: Mumit Khan <khan AT xraylith DOT wisc DOT EDU>
Cc: cygwin AT sourceware DOT cygnus DOT com, mingw32 AT egroups DOT com
Subject: Re: gcc-2.95 mingw32 MSVCRT runtime fixed/updated.
Message-ID: <19990802115630.A869@cygnus.com>
References: <199908021407 DOT JAA30620 AT mercury DOT xraylith DOT wisc DOT edu>
Mime-Version: 1.0
X-Mailer: Mutt 0.95.6i
In-Reply-To: <199908021407.JAA30620@mercury.xraylith.wisc.edu>; from Mumit Khan on Mon, Aug 02, 1999 at 09:07:34AM -0500

On Mon, Aug 02, 1999 at 09:07:34AM -0500, Mumit Khan wrote:
>Those of you using gcc-2.95 mingw msvcrt runtime, please redownload.
>It was botched -- the drivers were looking in the wrong directory and
>also I had the target libraries in a directory named i386-mingw32msvc
>instead of i386-mingw32.
>
>ftp://ftp.xraylith.wisc.edu/pub/khan/gnu-win32/mingw32/gcc-2.95/

I'm getting ready to make a B21 release.  I don't want to include gcc,
gas, ld, etc. in this, though, because experience has shown that
it just causes confusion for people later on who try to use the old
outdated version of the compiler.

So, I was hoping to either provide a pointer to your site or to
actually mirror it at the sourceware.cygnus.com.  Alternatively,
I could give you an account on sourceware if you thought it would
be useful.

My basic stumbling block to releasing this right now is that I don't
have a full version of InstallShield here and I don't want to rely on
the internal group who did this last time to produce it since they are
notoriously slow.  So, I was thinking of trying to just do something
with a shell script and offering the option to download individual
packages from the net or bundling everything up and sending a large tar
ball.

So, the shell script would just ask basic questions like "what packages
do you want to install?", "where should I install this?" and "should
this be root, then?".  There won't be any fancy graphics or anything.

What do you think?

cgf

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

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019