Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
Sender: cygwin-owner@sourceware.cygnus.com
Date: Wed, 8 Mar 2000 22:08:13 -0500
Message-Id: <200003090308.WAA29406@envy.delorie.com>
From: DJ Delorie <dj@delorie.com>
To: Brendan.Simon@ctam.com.au
CC: cygwin@sourceware.cygnus.com
In-reply-to: <38C70079.FCDADBF4@ctam.com.au> (message from Brendan J Simon on
	Thu, 09 Mar 2000 12:38:02 +1100)
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> <38C70079.FCDADBF4@ctam.com.au>


> If they are just names that are independent of architecture, then
> why is there any need to mention the architecture ?

Well, so you can tell the difference between those and, say,
ppc-pc-cygwin.  Or, i86-pc-cygwin (if a 16-bit version were even
possible).

> Furthermore, what is the point of changing the name of the
> architecture if there is no difference ?

Marketing.  People don't like buying software for "older" computers.
Plus, "uname" returns the actual cpu, and config.guess uses that, so
if you built cygwin on a 486, it would default to i486-pc-cygwin
because that's what you built it on.  We all have 686's so that's our
default.

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