ftp.delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin-apps/2000/07/08/11:58:34

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: <39675070.9C41CB2E@ece.gatech.edu>
Date: Sat, 08 Jul 2000 12:01:52 -0400
From: Charles Wilson <cwilson AT ece DOT gatech DOT edu>
X-Mailer: Mozilla 4.73 [en] (Windows NT 5.0; U)
X-Accept-Language: en
MIME-Version: 1.0
To: cygwin-apps AT sourceware DOT cygnus DOT com
Subject: processor compatibility when building packages

What is the 'official' policy concerning cygwin application
compatibility with older processors? For instance, zlib contains some
assembly routines for i586 and i686, but if I include those in an
updated zlib package on sourceware 'latest' then the package won't work
with older x86 processors.

Does cygwin only officially work on i686, so that it is okay to use
these routines and break compatibility with older systems?

--Chuck

- Raw text -


  webmaster     delorie software   privacy  
  Copyright 2019   by DJ Delorie     Updated Jul 2019