delorie.com/archives/browse.cgi   search  
Mail Archives: cygwin/1999/10/01/15:33:05

Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Unsubscribe: <mailto:cygwin-unsubscribe-archive-cygwin=delorie DOT com AT sourceware DOT cygnus DOT com>
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
Message-ID: <551CAE7F65D2D211A67E0008C7A4A99E0502E6@exchny25.sbi.com>
From: "Whitney, John" <john DOT whitney AT ssmb DOT com>
To: "'cygwin AT sourceware DOT cygnus DOT com'" <cygwin AT sourceware DOT cygnus DOT com>
Subject: RE:RE: why gcc.exe compilation SLOW on NT?
Date: Fri, 1 Oct 1999 15:26:55 -0400
X-Mailer: Internet Mail Service (5.5.2650.10)

Paul,

Thanks for your response.

I tried mingw32 and it DID compile fast.  It took a couple of seconds at the
most to compile my source.  So that verified that cygwin was part of the
problem.

After trying Mumit's advice from the mailing list, I found if I removed
network paths from my PATH variable, leaving simply a "...\cygwin\..." path,
i got down to a reasonable mingw32-like compilation time of a couple of
seconds, in bash and on the command line.

-John

-----Original Message-----
From: Paul Garceau [mailto:pgarceau AT teleport DOT com]
Sent: Thursday, September 30, 1999 9:07 PM
To: Whitney, John
Subject: Re: why gcc.exe compilation SLOW on NT?


Hi John,

	You've probably already gotten lots of email on this...

On 30 Sep 99, at 19:31, the Illustrious John Whitney wrote:

> Hey Folks,
> 
> I didn't expect my "helloworld.c" program to take 10 minutes to
> compile via cygwin's gcc.exe (version egcs-2.91.57) on my NT
> machine.  The compile did complete and the resulting exe does
> run, but why so long to compile?

	not sure what platform you're running...shouldn't matter too 
much...I am running an Intel based platform (Celeron).  I copied 
your source code and then, at the ms-dos command line, compiled 
it using the following command under MS-Dos Command Prompt.

	gcc helloworld.c -ohelloworld.exe

		I have 65M ram.  Total compile time using Mingw32 (GCC-2.95)

was about 5 seconds.

	Even so, it shouldn't take 10 minutes.  You might want to 
consider using Mingw32 instead of cygwin.  They are, in essence, 
the same thing.  The biggest difference between them is that 
Cygwin.dll gives you the ability to run in a shell in much the 
same way that Unix requires a shell.

	Mingw32 doesn't need any shell unless you consider the MSDOS 
Command Prompt a "shell" (which, imho, it isn't).

	Hope this helps.

	Peace,

		Paul G.

> 
> I'm a unix/gcc veteran but am very new to NT.  (I don't dare make
> assumptions about what is going on under NT's hood yet).
> 
> Below is my program.  I used a command line like "gcc.exe -o
> hello.exe helloworld.c" in bash and in the dos shell.  Both were
> slow.  From bash, the ps command showed something called
> collect2.exe running along with gcc.exe.  Sorry, I don't know if
> collect2.exe is relevant.
> 
> The NT machine is a late-model, multiuser, lightly used,
> heavyduty server (ie, LOTS of memory).
> 
> ------------
> #include <stdio.h>
> 
> int
> main(int argc, char **argv)
> {
>  printf("hello world, %s\n", argv[argc-1]);
> }
> -----------
> 
> 
> 
> Thanks in advance for any insights,
> 
> John Whitney
> 
> john DOT whitney_a AT t_ssmb DOT com
> 
> 
> 
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com
> 




Nothing real can be threatened.
    Nothing unreal exists.

--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019