Mailing-List: contact cygwin-developers-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-developers-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin-developers AT sourceware DOT cygnus DOT com Date: Mon, 28 Feb 2000 00:03:03 -0500 From: Glenn Spell To: cygwin-developers AT sourceware DOT cygnus DOT com Subject: Re: next net release preview Message-ID: <20000228000303.A17938@shell4.ba.best.com> Reply-To: cygwin-developers AT sourceware DOT cygnus DOT com Mail-Followup-To: cygwin-developers AT sourceware DOT cygnus DOT com References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: ; from "Mumit Khan" on Sun, Feb 27, 2000 at 08:16PM Organization: the aerie On 27 Feb 2000 around 8:16PM (-0600) Mumit Khan wrote: > I just checked my local copy, and binutils does use i686-pc-cygwin > and not i686-pc-cygwin32. Could someone who's downloaded the > preview binaries please double check and report if there's an > inconsistency? The binaries from the preview use i686-pc-cygwin and not cygwin32. config.guess uses cygwin32. So I guess if someone builds from source without specifying the architecture they'll get the "cygwin32", right? (or does config.sub override config.guess??) There are various cygwin32's in conditional macros throughout the source but that should be no problem. etc/configure.texi uses cygwin32 throughout. dlltool.c and dllwrap.c use cygwin32 but only in comments. However, gdb *does* use "i686-pc-cygwin32" in the binary package. -glenn -- ________________________________________ _ _____ ) )_ _ (__\____o /_/_ | ) Glenn Spell ) >-----._/_/__]> )________________________________________) `0 |