This is the mail archive of the email@example.com
mailing list for the Cygwin project. See the Cygwin
home page for more information.
[Date Prev][Date Next][Thread Prev][Thread Next]
[Date Index] [Subject Index] [Author Index] [Thread Index]
Re: Compiled executable differences between 9x and NT
- To: firstname.lastname@example.org, email@example.com
- Subject: Re: Compiled executable differences between 9x and NT
- From: N8TM@aol.com
- Date: Mon, 8 Mar 1999 21:09:59 EST
- Delivered-To: firstname.lastname@example.org
- Delivered-To: mailing list email@example.com
- Mailing-List: contact firstname.lastname@example.org; run by ezmlm
- Sender: email@example.com
In a message dated 3/8/99 6:23:52 AM Pacific Standard Time, firstname.lastname@example.org
<< What are the *exact* differences between 95 and NT,
as far as the cygwin environment and compiler are
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 email@example.com