Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sourceware.cygnus.com
Message-ID: <38C70079.FCDADBF4@ctam.com.au>
Date: Thu, 09 Mar 2000 12:38:02 +1100
From: Brendan J Simon <Brendan.Simon@ctam.com.au>
Reply-To: Brendan.Simon@ctam.com.au
Organization: CTAM Pty Ltd, Australia.
MIME-Version: 1.0
To: DJ Delorie <dj@delorie.com>
CC: cygwin@sourceware.cygnus.com
Subject: Re: cygwin-inst-20000304 query
References: <38C441C9.D83FB437@ctam.com.au>
	 <200003070146.UAA19157@envy.delorie.com> <38C5820D.23D114E1@ctam.com.au> <200003080020.TAA26089@envy.delorie.com>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

DJ Delorie wrote:

> The target name doesn't affect that at all.  It's just a name.
>
> An i586 is not the same as an i686, but i586-pc-cygwin32 is the same
> target as i686-pc-cygwin.  They're just names that mean "cygwin".

If they are just names that are independent of architecture, then why is
there any need to mention the architecture ?
Furthermore, what is the point of changing the name of the architecture if
there is no difference ?

I thought that the intention of the target directories was to have
libraries and code that are target specific.  eg. i686-pc-cygwin would have
i686 specific/optimized code, i586-pc-cygwin would have i586
specific/optimized code, etc.

Brendan Simon.


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com