Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-developers-subscribe AT sources DOT redhat DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin-developers/>
List-Post: <mailto:cygwin-developers AT sources DOT redhat DOT com>
List-Help: <mailto:cygwin-developers-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-developers-owner AT sources DOT redhat DOT com
Delivered-To: mailing list cygwin-developers AT sources DOT redhat DOT com
Date: Tue, 24 Apr 2001 23:54:42 -0400
From: Christopher Faylor <cgf AT redhat DOT com>
To: cygwin-developers AT cygwin DOT com
Cc: cygwin-apps AT cygwin DOT com
Subject: screwup in w32api release
Message-ID: <20010424235442.A3785@redhat.com>
Reply-To: cygwin-developers AT cygwin DOT com, cygwin-apps AT cygwin DOT com
Mail-Followup-To: cygwin-developers AT cygwin DOT com, cygwin-apps AT cygwin DOT com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.3.11i

I screwed up the w32api release somehow.  At one point, I thought it
would be a good idea to make symbolic links from /usr/lib/w32api to
/usr/lib.  But, when I did that, I managed to include the full path to
my own directory layout in the tar ball.

So, I've regenerated a w32api-20010424-2.  It doesn't have any symlinks
at all.  This will work fine with the latest version of gcc.  It will
require that users add a -L/usr/lib/w32api for older versions.

Let the email flood begin...

cgf