Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sourceware.cygnus.com Delivered-To: mailing list cygwin@sourceware.cygnus.com X-Authentication-Warning: hp2.xraylith.wisc.edu: khan owned process doing -bs Date: Tue, 23 Nov 1999 15:47:24 -0600 (CST) From: Mumit Khan To: cygwin@sourceware.cygnus.com Subject: Re: Solution to DLLWRAP problem in Cygwin v1.0 CD In-Reply-To: <19991123090940.A952@cygnus.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII On Tue, 23 Nov 1999, Chris Faylor wrote: > Hmm. The stuff on the CD should have been cut at least six months after > B20.1. The change logs seem to indicate that it has some cygwin32 -> > cygwin changes. > > However, our master sources also check for "cygwin32" rather than > cygwin, so I guess this is why. Geoff checked in some changes back in > October but they didn't specifically change the string which searched > for cygwin32. > Is there something different in the external binutils repository? The problem is there as well. The reason v1.0 exposes this problem is by changing the target name from i586-cygwin32, used by b20.1 even though internal names were changed from cygwin32 to cygwin, to i686-cygwin used by v1.0. I'll submit a change to binutils. May be a good time to grep for all occurrances of "cygwin32" in all the development tools and see what we come up with. Regards, Mumit -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com