Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sourceware.cygnus.com Delivered-To: mailing list cygwin@sourceware.cygnus.com Date: Tue, 7 Mar 2000 18:48:51 -0500 From: Glenn Spell To: cygwin@sourceware.cygnus.com Subject: Re: cygwin-inst-20000304 query Message-ID: <20000307184850.B9319@shell4.ba.best.com> Reply-To: cygwin@sourceware.cygnus.com Mail-Followup-To: cygwin@sourceware.cygnus.com References: <38C441C9.D83FB437@ctam.com.au> <200003070146.UAA19157@envy.delorie.com> <38C5820D.23D114E1@ctam.com.au> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <38C5820D.23D114E1@ctam.com.au>; from "Brendan J Simon" on Wed, Mar 08, 2000 at 09:26AM Organization: the aerie On 8 Mar 2000 around 9:26AM (+1100) Brendan J Simon wrote: > DJ Delorie wrote: > > > Right. We're working on migrating all the packages to the > > i686-pc-cygwin target identifier. > > Does this mean that some programs wont run on CPUs pre 686 > (ie. 386, 486, 586) ? I'll let DJ answer that. But a related question: What compiler flags are used in compiling the snapshots and net releases? Are any compiler optimizations for the x86 family used? -glenn -- ________________________________________ _ _____ ) )_ _ (__\____o /_/_ | ) Glenn Spell ) >-----._/_/__]> )________________________________________) `0 | -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com