Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
From: N8TM AT aol DOT com
Message-ID: <3f153aea.36e482f7@aol.com>
Date: Mon, 8 Mar 1999 21:09:59 EST
To: jonpryor AT vt DOT edu, cygwin AT sourceware DOT cygnus DOT com
Mime-Version: 1.0
Subject: Re: Compiled executable differences between 9x and NT
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7bit
X-Mailer: AOL 4.0 for Windows 95 sub 13

In a message dated 3/8/99 6:23:52 AM Pacific Standard Time, jonpryor AT vt DOT edu
writes:

<< What are the *exact* differences between 95 and NT,
 as far as the cygwin environment and compiler are
 concerned? >>

I imagine many of them are dependent on proprietary M$ information.

<<Under 95, it's currently causing
a "blue screen">>

There's one of these when expect crashes in the egcs testsuite on W95.  It
doesn't get that far under NT.

<<Is there anything that is known to break 95 while
working under NT?>>

Of course, but I haven't seen any official list.  One of them is attempting to
build egcs from patch files.  The snapshot releases have made progress on the
vfork failures of the original b20.1 under W95.  There are also things which
work better under W95 than NT.  One of them is catching success/failure
returns from gcc/g++/g77 compiled a.exe.

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com