RE: C compilation slow on NT

RE: C compilation slow on NT

[Earnie Boyd]

Hi Emmanuel,

You have several problems with your setup.  I've highlighted below.

--- Emmanuel STAPF <manus@eiffel.com> wrote:
> > Please paste in a `cygcheck -s -v -r'.  You've a setup problem
> > that you need to resolve.
> 
> Below is the result of the command as typed on my machine.
> 
> Regards,
> Manu
> 
> 
> Cygnus Win95/NT Configuration Diagnostics
> Current System Time: Sun Oct 31 09:26:11 1999
> 
> WinNT Ver 4.0 build 1381 Service Pack 3
> 
> Path:	/WINNT/system32
> 	/WINNT
> 	/Program Files/Mts
> 	//D/tmp/jacques/BIN
> 	//d/apps/matisse/bin
> 	/APPS/InstallShield/InstallShield 5.5 Professional Edition/Program
> 	/PROGRA~1/Tcl/bin
> 	//D/APPS/MSVC/COMMON/TOOLS/WINNT
> 	//D/APPS/MSVC/COMMON/MSDEV98/BIN
> 	//D/APPS/MSVC/COMMON/TOOLS
> 	//D/APPS/MSVC/VC98/BIN
> 	/BIN
> 	//D/APPS/BORLAND/CBUILD~1/PROJECTS/BPL
> 	//D/APPS/BORLAND/CBUILD~1/BIN
> 	//D/APPS/VIM
> 	//D/APPS/GNU
> 	//d/apps/Cygnus/cygwin-B20/H-I586-CYGWIN32/BIN
> 	//D/APPS/MATISSE/BIN
> 

First of all the //d/apps/Cygnus/cygwin-B20/H-I586-CYGWIN32/BIN should be
listed first in the PATH.  Also, remove the directories that you don't plan to
use while in bash with cygwin.

Second, you have the root directory mounted on C: and the cygwin product on D:.
  This could have been because you installed on C: and then moved it to D:. 
The package will run this way but could be an unconfirmed cause for your slow
down.  If you wish to change this, change to the directory contain the mount
and umount binaries and then do sh -c './umount / && mount d:\\ /'.
 
Third, you should also `mount d:\\ /d' so that you don't end up looking for a
UNC path.

> SysDir: C:\WINNT\System32
> WinDir: C:\WINNT
> 
> GCC_EXEC_PREFIX = `d:\apps\Cygnus\cygwin-B20\H-i586-cygwin32\lib\gcc-lib\'

You shouldn't need the GCC_EXEC_PREFIX variable if you have things setup
correctly.

> TCL_LIBRARY = `d:\apps\Cygnus\cygwin-B20\share\tcl8.0\'
> 
-8<-
> 
> Found: d:\apps\Cygnus\cygwin-B20\H-I586-CYGWIN32\BIN\bash.exe
> Found: d:\apps\Cygnus\cygwin-B20\H-I586-CYGWIN32\BIN\cat.exe
> Found: d:\apps\Cygnus\cygwin-B20\H-I586-CYGWIN32\BIN\cpp.exe
> Found: d:\apps\Cygnus\cygwin-B20\H-I586-CYGWIN32\BIN\find.exe
> Found: d:\apps\Cygnus\cygwin-B20\H-I586-CYGWIN32\BIN\gcc.exe
> Found: d:\apps\Cygnus\cygwin-B20\H-I586-CYGWIN32\BIN\gdb.exe
> Found: d:\apps\Cygnus\cygwin-B20\H-I586-CYGWIN32\BIN\ld.exe
> Found: d:\apps\Cygnus\cygwin-B20\H-I586-CYGWIN32\BIN\ls.exe
> Found: D:\APPS\BORLAND\CBUILD~1\BIN\make.exe
> Found: d:\apps\Cygnus\cygwin-B20\H-I586-CYGWIN32\BIN\make.exe
> Warning: D:\APPS\BORLAND\CBUILD~1\BIN\make.exe hides
> d:\apps\Cygnus\cygwin-B20\H-I586-CYGWIN32\BIN\make.exe

So you wish to use Borland's make instead of the cygwin make?  This is due to
the PATH variable.

> Found: C:\BIN\sh.exe
> Found: d:\apps\Cygnus\cygwin-B20\H-I586-CYGWIN32\BIN\sh.exe
> Warning: C:\BIN\sh.exe hides
> d:\apps\Cygnus\cygwin-B20\H-I586-CYGWIN32\BIN\sh.exe
> 
>   371k 1998/12/01
> d:\apps\Cygnus\cygwin-B20\H-I586-CYGWIN32\BIN\cygtcl80.dll - os=4.0 img=1.0
> sys=4.0
>                   "cygtcl80.dll" v0.0 ts=1998/12/1 0:25
>     5k 1998/12/01
> d:\apps\Cygnus\cygwin-B20\H-I586-CYGWIN32\BIN\cygtclpip80.dll - os=4.0
> img=1.0 sys=4.0
>    10k 1998/12/01
> d:\apps\Cygnus\cygwin-B20\H-I586-CYGWIN32\BIN\cygtclreg80.dll - os=4.0
> img=1.0 sys=4.0
>                   "cygtclreg80.dll" v0.0 ts=1998/12/1 0:25
>   600k 1998/12/01
> d:\apps\Cygnus\cygwin-B20\H-I586-CYGWIN32\BIN\cygtk80.dll - os=4.0 img=1.0
> sys=4.0
>                   "cygtk80.dll" v0.0 ts=1998/12/1 0:28
>   446k 1998/12/04
> d:\apps\Cygnus\cygwin-B20\H-I586-CYGWIN32\BIN\cygwin1.dll - os=4.0 img=1.0
> sys=4.0
>                   "cygwin1.dll" v0.0 ts=1998/12/3 20:39
> Use -h to see help about each section

Please read the information on my pages.


=====
Earnie Boyd < mailto:earnie_boyd@yahoo.com >
Newbies, please visit
< http://www.freeyellow.com/members5/gw32/index.html >
__________________________________________________
Do You Yahoo!?
Bid and sell for free at http://auctions.yahoo.com

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

RE: C compilation slow on NT

[Earnie Boyd]

Hi Emmanuel,

You have several problems with your setup.  I've highlighted below.

--- Emmanuel STAPF <manus@eiffel.com> wrote:
> > Please paste in a `cygcheck -s -v -r'.  You've a setup problem
> > that you need to resolve.
> 
> Below is the result of the command as typed on my machine.
> 
> Regards,
> Manu
> 
> 
> Cygnus Win95/NT Configuration Diagnostics
> Current System Time: Sun Oct 31 09:26:11 1999
> 
> WinNT Ver 4.0 build 1381 Service Pack 3
> 
> Path:	/WINNT/system32
> 	/WINNT
> 	/Program Files/Mts
> 	//D/tmp/jacques/BIN
> 	//d/apps/matisse/bin
> 	/APPS/InstallShield/InstallShield 5.5 Professional Edition/Program
> 	/PROGRA~1/Tcl/bin
> 	//D/APPS/MSVC/COMMON/TOOLS/WINNT
> 	//D/APPS/MSVC/COMMON/MSDEV98/BIN
> 	//D/APPS/MSVC/COMMON/TOOLS
> 	//D/APPS/MSVC/VC98/BIN
> 	/BIN
> 	//D/APPS/BORLAND/CBUILD~1/PROJECTS/BPL
> 	//D/APPS/BORLAND/CBUILD~1/BIN
> 	//D/APPS/VIM
> 	//D/APPS/GNU
> 	//d/apps/Cygnus/cygwin-B20/H-I586-CYGWIN32/BIN
> 	//D/APPS/MATISSE/BIN
> 

First of all the //d/apps/Cygnus/cygwin-B20/H-I586-CYGWIN32/BIN should be
listed first in the PATH.  Also, remove the directories that you don't plan to
use while in bash with cygwin.

Second, you have the root directory mounted on C: and the cygwin product on D:.
  This could have been because you installed on C: and then moved it to D:. 
The package will run this way but could be an unconfirmed cause for your slow
down.  If you wish to change this, change to the directory contain the mount
and umount binaries and then do sh -c './umount / && mount d:\\ /'.
 
Third, you should also `mount d:\\ /d' so that you don't end up looking for a
UNC path.

> SysDir: C:\WINNT\System32
> WinDir: C:\WINNT
> 
> GCC_EXEC_PREFIX = `d:\apps\Cygnus\cygwin-B20\H-i586-cygwin32\lib\gcc-lib\'

You shouldn't need the GCC_EXEC_PREFIX variable if you have things setup
correctly.

> TCL_LIBRARY = `d:\apps\Cygnus\cygwin-B20\share\tcl8.0\'
> 
-8<-
> 
> Found: d:\apps\Cygnus\cygwin-B20\H-I586-CYGWIN32\BIN\bash.exe
> Found: d:\apps\Cygnus\cygwin-B20\H-I586-CYGWIN32\BIN\cat.exe
> Found: d:\apps\Cygnus\cygwin-B20\H-I586-CYGWIN32\BIN\cpp.exe
> Found: d:\apps\Cygnus\cygwin-B20\H-I586-CYGWIN32\BIN\find.exe
> Found: d:\apps\Cygnus\cygwin-B20\H-I586-CYGWIN32\BIN\gcc.exe
> Found: d:\apps\Cygnus\cygwin-B20\H-I586-CYGWIN32\BIN\gdb.exe
> Found: d:\apps\Cygnus\cygwin-B20\H-I586-CYGWIN32\BIN\ld.exe
> Found: d:\apps\Cygnus\cygwin-B20\H-I586-CYGWIN32\BIN\ls.exe
> Found: D:\APPS\BORLAND\CBUILD~1\BIN\make.exe
> Found: d:\apps\Cygnus\cygwin-B20\H-I586-CYGWIN32\BIN\make.exe
> Warning: D:\APPS\BORLAND\CBUILD~1\BIN\make.exe hides
> d:\apps\Cygnus\cygwin-B20\H-I586-CYGWIN32\BIN\make.exe

So you wish to use Borland's make instead of the cygwin make?  This is due to
the PATH variable.

> Found: C:\BIN\sh.exe
> Found: d:\apps\Cygnus\cygwin-B20\H-I586-CYGWIN32\BIN\sh.exe
> Warning: C:\BIN\sh.exe hides
> d:\apps\Cygnus\cygwin-B20\H-I586-CYGWIN32\BIN\sh.exe
> 
>   371k 1998/12/01
> d:\apps\Cygnus\cygwin-B20\H-I586-CYGWIN32\BIN\cygtcl80.dll - os=4.0 img=1.0
> sys=4.0
>                   "cygtcl80.dll" v0.0 ts=1998/12/1 0:25
>     5k 1998/12/01
> d:\apps\Cygnus\cygwin-B20\H-I586-CYGWIN32\BIN\cygtclpip80.dll - os=4.0
> img=1.0 sys=4.0
>    10k 1998/12/01
> d:\apps\Cygnus\cygwin-B20\H-I586-CYGWIN32\BIN\cygtclreg80.dll - os=4.0
> img=1.0 sys=4.0
>                   "cygtclreg80.dll" v0.0 ts=1998/12/1 0:25
>   600k 1998/12/01
> d:\apps\Cygnus\cygwin-B20\H-I586-CYGWIN32\BIN\cygtk80.dll - os=4.0 img=1.0
> sys=4.0
>                   "cygtk80.dll" v0.0 ts=1998/12/1 0:28
>   446k 1998/12/04
> d:\apps\Cygnus\cygwin-B20\H-I586-CYGWIN32\BIN\cygwin1.dll - os=4.0 img=1.0
> sys=4.0
>                   "cygwin1.dll" v0.0 ts=1998/12/3 20:39
> Use -h to see help about each section

Please read the information on my pages.


=====
Earnie Boyd < mailto:earnie_boyd@yahoo.com >
Newbies, please visit
< http://www.freeyellow.com/members5/gw32/index.html >
__________________________________________________
Do You Yahoo!?
Bid and sell for free at http://auctions.yahoo.com

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

Make question

[Emmanuel STAPF]

In my makefile, I have the following statement:

.c.obj:
	$(CC) $(CFLAGS) -c $<

and I'm using my makefile to generate a `file.obj' from a `file.c' which
will be using to create a `library.lib' file.

However, make fails with the following output:
make: *** No rule to make target `file.obj', needed by `library.lib'.  Stop.

Is there something special to do to allow my implicit rule.

Thanks in advance,
Regards,
Manu


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

Re: Make question

[Heinz-Juergen Oertel]

[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1199 bytes --]

Emmanuel STAPF wrote:
> 
> In my makefile, I have the following statement:
> 
> .c.obj:
>         $(CC) $(CFLAGS) -c $<
> 
> and I'm using my makefile to generate a `file.obj' from a `file.c' which
> will be using to create a `library.lib' file.
> 
> However, make fails with the following output:
> make: *** No rule to make target `file.obj', needed by `library.lib'.  Stop.
> 
> Is there something special to do to allow my implicit rule.
> 
> Thanks in advance,
> Regards,
> Manu

It's not a Cygwin question, anyway, this works when I am using
Borland C or KEIL-C

.SUFFIXES: .obj
%.obj : %.c
        $(CC) $(CFLAGS) -o $@ -c $<


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

-- 
with best regards / mit freundlichen Grüßen

   Heinz-Jürgen Oertel

===========================================
Heinz-Jürgen Oertel
port GmbH            phone +49 345 77755-0
Regensburger Str. 7c fax   +49 345 77755-20
D-06132 Halle/Saale  mailto:oe@port.de
Germany              http://www.port.de
===========================================


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

Re: Make question

[Steve Kelem]

You need to include the line

.SUFFIXES: .obj

so that make knows about this new suffix.

Steve

Emmanuel STAPF wrote:

> In my makefile, I have the following statement:
>
> .c.obj:
>         $(CC) $(CFLAGS) -c $<
>
> and I'm using my makefile to generate a `file.obj' from a `file.c' which
> will be using to create a `library.lib' file.
>
> However, make fails with the following output:
> make: *** No rule to make target `file.obj', needed by `library.lib'.  Stop.
>
> Is there something special to do to allow my implicit rule.
>
> Thanks in advance,
> Regards,
> Manu
>
> --
> Want to unsubscribe from this list?
> Send a message to cygwin-unsubscribe@sourceware.cygnus.com

RE: Make question

[Emmanuel STAPF]

Thanks for the suggestions, this was indeed a missing .SUFFIXES clause which
was causing the make behavior.

Manu


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

RE: C compilation slow on NT

[Earnie Boyd]

--- Emmanuel STAPF <manus@eiffel.com> wrote:
> > Are you executing from the DOS prompt to do "something" or from
> > bash?  I would
> > suggest that you start your make process from within bash to avoid the
> > cygwin1.dll instantiation for each process.  You might want to supply the
> > output of `cygcheck -s -v -r' either pasted or attached in a
> > plain text file.
> 
> I was launching it from the DOS prompt. I cannot launch it from the bash
> prompt, because in it for some reasons gcc cannot read path containing "/",
> whereas in DOS it can.
> 

Please paste in a `cygcheck -s -v -r'.  You've a setup problem that you need to resolve.

=====
Earnie Boyd < mailto:earnie_boyd@yahoo.com >
Newbies, please visit
< http://www.freeyellow.com/members5/gw32/index.html >
__________________________________________________
Do You Yahoo!?
Bid and sell for free at http://auctions.yahoo.com

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

C compilation slow on NT

[Emmanuel STAPF]

Sorry to bother you guys. I read  a thread not too long ago about the poor
performance of gcc on Windows NT. I was trying to find the solution given in
the mailing list archive, but it is not easy due to the poor search
possibilities offered by the web page.

Can someone send me what has to be modified so that gcc does not do lookup
on the network? Thanks in advance.

Otherwise, I notice that make was slow too. Any idea?

Regards,
Manu


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

Re: C compilation slow on NT

[Mumit Khan]

"Emmanuel STAPF" <manus@eiffel.com> writes:
> Sorry to bother you guys. I read  a thread not too long ago about the poor
> performance of gcc on Windows NT. I was trying to find the solution given in
> the mailing list archive, but it is not easy due to the poor search
> possibilities offered by the web page.
> 
> Can someone send me what has to be modified so that gcc does not do lookup
> on the network? Thanks in advance.
> 
> Otherwise, I notice that make was slow too. Any idea?
> 

The trick is to make sure that network drives are not in your PATH, and also
that you have HOME defined correctly and it's not '/'. On NT, these could be 
in the registry and can stay hidden.

The trouble with HOME is the following: let's say you HOME=/ defined
in the environment. Some of the tools, eg. gdb, tries to find startup files
in $HOME/<startupfile>, and some of these append an extra '/' and so it
expands to '//<startupfile>' and that's a UNC path. Takes a while before
it times out.

Regards,
Mumit


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

RE: C compilation slow on NT

[Mike MacDonald]

Hmm..  I do have a huge path..

-----Original Message-----
From: cygwin-owner@sourceware.cygnus.com
[ mailto:cygwin-owner@sourceware.cygnus.com]On Behalf Of Emmanuel STAPF
Sent: Friday, October 29, 1999 5:02 PM
To: cygwin@sourceware.cygnus.com
Subject: RE: C compilation slow on NT 


> > Otherwise, I notice that make was slow too. Any idea?

I found something very interesting. If my path is the following:

	set
PATH=d:\apps\cygnus\cygwin-b20\H-i586-cygwin32\bin;d:\apps\vim;d:\apps\gnu

It takes 10 seconds to start doing something in the makefile.

If the path is:

	set PATH=d:\apps\cygnus\cygwin-b20\H-i586-cygwin32\bin

It takes less than a second.
Any ideas? Something already known?

Regards,
Manu


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

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

RE: C compilation slow on NT

[Earnie Boyd]

--- Emmanuel STAPF <manus@eiffel.com> wrote:
> > > Otherwise, I notice that make was slow too. Any idea?
> 
> I found something very interesting. If my path is the following:
> 
> 	set
> PATH=d:\apps\cygnus\cygwin-b20\H-i586-cygwin32\bin;d:\apps\vim;d:\apps\gnu
> 
> It takes 10 seconds to start doing something in the makefile.
> 
> If the path is:
> 
> 	set PATH=d:\apps\cygnus\cygwin-b20\H-i586-cygwin32\bin
> 
> It takes less than a second.
> Any ideas? Something already known?

Are you executing from the DOS prompt to do "something" or from bash?  I would
suggest that you start your make process from within bash to avoid the
cygwin1.dll instantiation for each process.  You might want to supply the
output of `cygcheck -s -v -r' either pasted or attached in a plain text file.


=====
Earnie Boyd < mailto:earnie_boyd@yahoo.com >
Newbies, please visit
< http://www.freeyellow.com/members5/gw32/index.html >
__________________________________________________
Do You Yahoo!?
Bid and sell for free at http://auctions.yahoo.com

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

RE: C compilation slow on NT

[Emmanuel STAPF]

> Are you executing from the DOS prompt to do "something" or from
> bash?  I would
> suggest that you start your make process from within bash to avoid the
> cygwin1.dll instantiation for each process.  You might want to supply the
> output of `cygcheck -s -v -r' either pasted or attached in a
> plain text file.

I was launching it from the DOS prompt. I cannot launch it from the bash
prompt, because in it for some reasons gcc cannot read path containing "/",
whereas in DOS it can.

Manu


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

RE: C compilation slow on NT

[Emmanuel STAPF]

> > Otherwise, I notice that make was slow too. Any idea?

I found something very interesting. If my path is the following:

	set
PATH=d:\apps\cygnus\cygwin-b20\H-i586-cygwin32\bin;d:\apps\vim;d:\apps\gnu

It takes 10 seconds to start doing something in the makefile.

If the path is:

	set PATH=d:\apps\cygnus\cygwin-b20\H-i586-cygwin32\bin

It takes less than a second.
Any ideas? Something already known?

Regards,
Manu


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

RE: C compilation slow on NT

[Earnie Boyd]

--- Emmanuel STAPF <manus@eiffel.com> wrote:
> > Are you executing from the DOS prompt to do "something" or from
> > bash?  I would
> > suggest that you start your make process from within bash to avoid the
> > cygwin1.dll instantiation for each process.  You might want to supply the
> > output of `cygcheck -s -v -r' either pasted or attached in a
> > plain text file.
> 
> I was launching it from the DOS prompt. I cannot launch it from the bash
> prompt, because in it for some reasons gcc cannot read path containing "/",
> whereas in DOS it can.
> 

Please paste in a `cygcheck -s -v -r'.  You've a setup problem that you need to resolve.

=====
Earnie Boyd < mailto:earnie_boyd@yahoo.com >
Newbies, please visit
< http://www.freeyellow.com/members5/gw32/index.html >
__________________________________________________
Do You Yahoo!?
Bid and sell for free at http://auctions.yahoo.com

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

RE: C compilation slow on NT

[Emmanuel STAPF]

> Are you executing from the DOS prompt to do "something" or from
> bash?  I would
> suggest that you start your make process from within bash to avoid the
> cygwin1.dll instantiation for each process.  You might want to supply the
> output of `cygcheck -s -v -r' either pasted or attached in a
> plain text file.

I was launching it from the DOS prompt. I cannot launch it from the bash
prompt, because in it for some reasons gcc cannot read path containing "/",
whereas in DOS it can.

Manu


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

RE: C compilation slow on NT

[Earnie Boyd]

--- Emmanuel STAPF <manus@eiffel.com> wrote:
> > > Otherwise, I notice that make was slow too. Any idea?
> 
> I found something very interesting. If my path is the following:
> 
> 	set
> PATH=d:\apps\cygnus\cygwin-b20\H-i586-cygwin32\bin;d:\apps\vim;d:\apps\gnu
> 
> It takes 10 seconds to start doing something in the makefile.
> 
> If the path is:
> 
> 	set PATH=d:\apps\cygnus\cygwin-b20\H-i586-cygwin32\bin
> 
> It takes less than a second.
> Any ideas? Something already known?

Are you executing from the DOS prompt to do "something" or from bash?  I would
suggest that you start your make process from within bash to avoid the
cygwin1.dll instantiation for each process.  You might want to supply the
output of `cygcheck -s -v -r' either pasted or attached in a plain text file.


=====
Earnie Boyd < mailto:earnie_boyd@yahoo.com >
Newbies, please visit
< http://www.freeyellow.com/members5/gw32/index.html >
__________________________________________________
Do You Yahoo!?
Bid and sell for free at http://auctions.yahoo.com

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

RE: C compilation slow on NT

[Mike MacDonald]

Hmm..  I do have a huge path..

-----Original Message-----
From: cygwin-owner@sourceware.cygnus.com
[ mailto:cygwin-owner@sourceware.cygnus.com]On Behalf Of Emmanuel STAPF
Sent: Friday, October 29, 1999 5:02 PM
To: cygwin@sourceware.cygnus.com
Subject: RE: C compilation slow on NT 


> > Otherwise, I notice that make was slow too. Any idea?

I found something very interesting. If my path is the following:

	set
PATH=d:\apps\cygnus\cygwin-b20\H-i586-cygwin32\bin;d:\apps\vim;d:\apps\gnu

It takes 10 seconds to start doing something in the makefile.

If the path is:

	set PATH=d:\apps\cygnus\cygwin-b20\H-i586-cygwin32\bin

It takes less than a second.
Any ideas? Something already known?

Regards,
Manu


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

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

RE: C compilation slow on NT

[Emmanuel STAPF]

> > Otherwise, I notice that make was slow too. Any idea?

I found something very interesting. If my path is the following:

	set
PATH=d:\apps\cygnus\cygwin-b20\H-i586-cygwin32\bin;d:\apps\vim;d:\apps\gnu

It takes 10 seconds to start doing something in the makefile.

If the path is:

	set PATH=d:\apps\cygnus\cygwin-b20\H-i586-cygwin32\bin

It takes less than a second.
Any ideas? Something already known?

Regards,
Manu


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

Re: C compilation slow on NT

[Mumit Khan]

"Emmanuel STAPF" <manus@eiffel.com> writes:
> Sorry to bother you guys. I read  a thread not too long ago about the poor
> performance of gcc on Windows NT. I was trying to find the solution given in
> the mailing list archive, but it is not easy due to the poor search
> possibilities offered by the web page.
> 
> Can someone send me what has to be modified so that gcc does not do lookup
> on the network? Thanks in advance.
> 
> Otherwise, I notice that make was slow too. Any idea?
> 

The trick is to make sure that network drives are not in your PATH, and also
that you have HOME defined correctly and it's not '/'. On NT, these could be 
in the registry and can stay hidden.

The trouble with HOME is the following: let's say you HOME=/ defined
in the environment. Some of the tools, eg. gdb, tries to find startup files
in $HOME/<startupfile>, and some of these append an extra '/' and so it
expands to '//<startupfile>' and that's a UNC path. Takes a while before
it times out.

Regards,
Mumit


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

C compilation slow on NT

[Emmanuel STAPF]

Sorry to bother you guys. I read  a thread not too long ago about the poor
performance of gcc on Windows NT. I was trying to find the solution given in
the mailing list archive, but it is not easy due to the poor search
possibilities offered by the web page.

Can someone send me what has to be modified so that gcc does not do lookup
on the network? Thanks in advance.

Otherwise, I notice that make was slow too. Any idea?

Regards,
Manu


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