From: Kevin Layer <layer@franz.com>
To: Corinna Vinschen <corinna@vinschen.de>
Cc: cygwin <cygwin@sourceware.cygnus.com>
Subject: Re: why is make so bloody slow (for me)
Date: Fri, 07 Apr 2000 16:56:00 -0000 [thread overview]
Message-ID: <200004072356.QAA08588@ultra.franz.com> (raw)
In-Reply-To: <38EE68A4.2CFC51BB@vinschen.de>
>> Kevin Layer wrote:
>> >
>> > >> I'm using W2K since B3 and I never saw _that_ one. On my machine
>> > >> PII 450, it runs fast enough. On the first glimps you wouldn't
>> > >> see a difference to NT4.
>> > >>
>> > >> So I would like to ask some questions:
>> > >>[...]
>>
>> Could you do me two favors?
>>
>> - Please try that `make -debug' with the latest snapshot from
>> the sourceware server.
Found it. http://sourceware.cygnus.com/cygwin/snapshots/
>> Do you see a clear speed up?
>> Does the SIGCHLD problem still exist?
>>
>> - If changing the dll doesn't help, could you please strace
>> `make -debug' and send the output as .gz file directly
>> to my mail address (not to the mailing list, please)?
>>
>> TIA,
>> Corinna
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next prev parent reply other threads:[~2000-04-07 16:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-04-07 11:24 Kevin Layer
2000-04-07 14:20 ` Corinna Vinschen
2000-04-07 14:26 ` Corinna Vinschen
2000-04-07 14:51 ` Kevin Layer
2000-04-07 16:10 ` Corinna Vinschen
2000-04-07 16:54 ` Kevin Layer
2000-04-07 16:56 ` Kevin Layer [this message]
2000-04-07 17:04 ` Kevin Layer
2000-04-07 17:05 ` Kevin Layer
2000-04-11 13:51 ` Cygwin CD licensing? Keith Graham
2000-04-11 14:04 ` DJ Delorie
2000-04-11 14:09 ` Chris Faylor
2000-04-09 12:06 ` why is make so bloody slow (for me) David Deaven
2000-04-10 12:37 ` Kevin Layer
2000-04-07 13:18 Kevin Layer
[not found] <013601bfa32d$d323ae50$5f0f4dd1@TIMYX18EWDT6RQ>
2000-04-10 13:53 ` Kevin Layer
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=200004072356.QAA08588@ultra.franz.com \
--to=layer@franz.com \
--cc=corinna@vinschen.de \
--cc=cygwin@sourceware.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).