Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT sourceware DOT cygnus DOT com Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com Message-ID: <38C70079.FCDADBF4@ctam.com.au> Date: Thu, 09 Mar 2000 12:38:02 +1100 From: Brendan J Simon Reply-To: Brendan DOT Simon AT ctam DOT com DOT au Organization: CTAM Pty Ltd, Australia. X-Mailer: Mozilla 4.61 [en] (X11; I; Linux 2.0.36 i586) X-Accept-Language: en MIME-Version: 1.0 To: DJ Delorie CC: cygwin AT sourceware DOT cygnus DOT com Subject: Re: cygwin-inst-20000304 query References: <38C441C9 DOT D83FB437 AT ctam DOT com DOT au> <200003070146 DOT UAA19157 AT envy DOT delorie DOT com> <38C5820D DOT 23D114E1 AT ctam DOT com DOT au> <200003080020 DOT TAA26089 AT envy DOT delorie DOT 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 AT sourceware DOT cygnus DOT com