www.delorie.com/archives/browse.cgi | search |
Mailing-List: | contact cygwin-apps-help AT sourceware DOT cygnus DOT com; run by ezmlm |
Sender: | cygwin-apps-owner AT sourceware DOT cygnus DOT com |
List-Subscribe: | <mailto:cygwin-apps-subscribe AT sources DOT redhat DOT com> |
List-Archive: | <http://sources.redhat.com/ml/cygwin-apps/> |
List-Post: | <mailto:cygwin-apps AT sources DOT redhat DOT com> |
List-Help: | <mailto:cygwin-apps-help AT sources DOT redhat DOT com>, <http://sources.redhat.com/lists.html#faqs> |
Delivered-To: | mailing list cygwin-apps AT sources DOT redhat DOT com |
Message-ID: | <20011013222258.87917.qmail@web14503.mail.yahoo.com> |
Date: | Sun, 14 Oct 2001 08:22:58 +1000 (EST) |
From: | =?iso-8859-1?q?Danny=20Smith?= <danny_r_smith_2001 AT yahoo DOT co DOT nz> |
Subject: | Re: processor compatibility when building packages |
To: | cygwin-apps <cygwin-apps AT cygwin DOT com> |
MIME-Version: | 1.0 |
This topic came up about a year ago on this list: http://sources.redhat.com/ml/cygwin-apps/2000-07/msg00039.html and I've recently raised it again on mingw lists. Looking at cygwin's spec file it says: *cpp_cpu_default: %(cpp_686) To me that means that, unless user overrides with command line -march or -mcpu option, code is tuned for i686. To get that into the specs file, one has to either configure gcc so that TARGET_CPU_DEFAULT=3 (=pentium) or pass that define to make when building gcc. That interpretion is different from the conclusion that was posted in the message pointed to above, which says that cygwin-produced code will run on any i[35467]86 arch. I'm not talking about the platform triplet moniker -- that I realise is just a name. I'm asking: Has anyone complained that cygwin-built apps fail on i386 but not on i686? Danny http://briefcase.yahoo.com.au - Yahoo! Briefcase - Manage your files online.
webmaster | delorie software privacy |
Copyright © 2019 by DJ Delorie | Updated Jul 2019 |