public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Colman Curtin" <ccurtin@trintech.com>
To: "Sonic Junior" <mphalpin@iag.net>, "GNU Win 32" <gnu-win32@cygnus.com>
Subject: sh crashes on 95
Date: Wed, 13 Aug 1997 11:50:00 -0000	[thread overview]
Message-ID: <199708131851.TAA30622@muzak.trintech.ie> (raw)

>
> Okay... when I'm doing make, sh has a habit of crashing. It's got bad
>recently. Where can I get da patch? Ack!
>
> SJ
>
Yip I've run into the same problem. Running configure scripts it seems to
choke at no particular point some times it get further than others. If I
reboot under NT4 configure completes to the end.
Looking at the processes while a configure is in progress I have seen up to
six instances of sh running, I haven't seen more as it normally dies and more
often than not needs the three fingered salute!

Anyone got any ideas??

running w95,16MB with Sergery's latest release.(the one with the borken wait
code on W95 removed)

thanx
Colman.
____________________________________________________________
Colman Curtin     mailto:ccurtin@trintech.ie
Software Engineer
------------------------------------------------------------
Trintech (Manufacturing) Ltd,  http://www.trintech.com/
South County Business Park,
Leopardstown,
Dublin 18.
Tel +353-1-2956766  Fax +353-1-2954735
------------------------------------------------------------

Q: How many IBM CPU's does it take to execute a job?
A: Four; three to hold it down, and one to rip its head off.






-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request@cygnus.com" with one line of text: "help".

             reply	other threads:[~1997-08-13 11:50 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-08-13 11:50 Colman Curtin [this message]
1997-08-14  8:07 ` Tony FITZPATRICK

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=199708131851.TAA30622@muzak.trintech.ie \
    --to=ccurtin@trintech.com \
    --cc=gnu-win32@cygnus.com \
    --cc=mphalpin@iag.net \
    /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).