From: N8TM@aol.com
To: dj@delorie.com, gnu-win32@cygnus.com
Subject: Re: BUg in GNU make 3.75 (CYGWIN port)
Date: Sun, 31 Jan 1999 23:52:00 -0000 [thread overview]
Message-ID: <3e461352.369d5c23@aol.com> (raw)
In a message dated 1/13/99 2:42:48 PM Pacific Standard Time, dj@delorie.com
writes:
<< We all have 95 or 98 machines available for testing, but
since NT is much more stable and reliable, we tend to use
NT for the bulk of our development. We don't get much
work done when we have to reboot the machine all the time. >>
I'm still mystified by these comments disparaging W9x. My NT4/SP3 takes
several times as long to run scripts as my W95 under cygwin, and W95 doesn't
crash any more often than NT unless you insist on running without USB or
running AOL and an egcs build at the same time, as I'm doing now. make-3.77
is worth installing even on NT, but it's a necessity on W95. I've had a few
egcs incremental patch problems on W95 which weren't replicated on NT, and the
egcs testsuite skips different sections on NT and W95, but I'll take the speed
of W95 ever NT any day. Yes, linux is still faster than any Windoze, but I
find those version incompatibilities just as annoying as the Windoze ones. It
does run egcs testsuite and struct OTOB.
-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".
next reply other threads:[~1999-01-31 23:52 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-01-31 23:52 N8TM [this message]
1999-01-31 23:52 ` DJ Delorie
-- strict thread matches above, loose matches on Subject: below --
1999-01-31 23:52 Dominique PELLE
1999-01-31 23:52 ` Glenn Spell
[not found] ` <199901111339.FAA06638.cygnus.gnu-win32@shell4.ba.best.com>
1999-01-31 23:52 ` DJ Delorie
1999-02-04 1:49 ` David M. Smith
1999-02-28 23:02 ` David M. Smith
1999-01-31 23:52 N8TM
1999-01-31 23:52 ` Glenn Spell
1999-01-31 23:52 Earnie Boyd
1999-01-31 23:52 ` Glenn Spell
1999-01-31 23:52 Earnie Boyd
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3e461352.369d5c23@aol.com \
--to=n8tm@aol.com \
--cc=dj@delorie.com \
--cc=gnu-win32@cygnus.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).