public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Kevin Layer <layer@franz.com>
To: David Deaven <deaven@execpc.com>
Cc: cygwin@sourceware.cygnus.com
Subject: Re: why is make so bloody slow (for me)
Date: Mon, 10 Apr 2000 12:37:00 -0000	[thread overview]
Message-ID: <200004101936.MAA26892@ultra.franz.com> (raw)
In-Reply-To: <200004091906.OAA03179@pop00.execpc.com>

>> 
>> Just to make sure, you are not using a network drive to build on, are you?  
>> For me, doing that in Windows NT (using NFS or clearcase MVFS network 
>> filesystems) makes builds run a factor of 10-50 slower, even though they are 
>> fast as ever under Linux or FreeBSD on the same physical box.  I chalk it up 
>> to poor network code in Microsoft OS.

No networks drives in my path, nor is my current working directory on
a remote machine.  I do have some mounted, though.

>> 
>> Dave
>>  
>> >I'm running Windows 2000 on a PIII 700 with 256mb of PC100 ECC RAM.
>> >It's not the machine, obviously.  It's probably win2k, but I thought
>> >I'd ask...
>> >
>> >I'm running the V1.0 of cygwin.
>> >
>> >The command "make --debug" gives this output:
>> >
>> >  GNU Make version 3.77, by Richard Stallman and Roland McGrath.
>> >  Copyright (C) 1988, 89, 90, 91, 92, 93, 94, 95, 96, 97, 98
>> >	  Free Software Foundation, Inc.
>> >  This is free software; see the source for copying conditions.
>> >  There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
>> >  PARTICULAR PURPOSE.
>> >
>> >  Report bugs to <bug-make@gnu.org>.
>> >
>> >  Reading makefiles...
>> >  Reading makefile `makefile'...
>> >  Reading makefile `../makefile.top' (search path) (no ~ expansion)...
>> >  Reading makefile `../makefile.defs' (search path) (no ~ expansion)...
>> >  Got a SIGCHLD; 1 unreaped children.
>> >  Got a SIGCHLD; 1 unreaped children.
>> >  Got a SIGCHLD; 1 unreaped children.
>> >  Got a SIGCHLD; 1 unreaped children.
>> >
>> >There is a 10 second pause after each of the above 4 lines is
>> >printed.  The overall effect is that it takes a good minute or two to
>> >get to doing some real work.
>> >
>> >I upgraded my processor and NT (from 4.0sp6a) around the same time,
>> >but I can swear it never was this slow.
>> >
>> >I have a bunch of $(shell ...) in lines my makefile.
>> >I have the environment variable MAKE_MODE set to UNIX.
>> >
>> >Ideas?
>> >
>> >	Kevin Layer
>> >
>> >--
>> >Want to unsubscribe from this list?
>> >Send a message to cygwin-unsubscribe@sourceware.cygnus.com
>> >
>> 
>> -- 
>> -------------------------------------
>> David Deaven        deaven@execpc.com
>> http://www.execpc.com/~deaven
>> 
>> 
>> 
>> 
>> -- 
>> -------------------------------------
>> David Deaven        deaven@execpc.com
>> http://www.execpc.com/~deaven
>> 
>> 
>> 


--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com

  reply	other threads:[~2000-04-10 12:37 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
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 [this message]
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=200004101936.MAA26892@ultra.franz.com \
    --to=layer@franz.com \
    --cc=cygwin@sourceware.cygnus.com \
    --cc=deaven@execpc.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).