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: make question

[Earnie Boyd]

--- CGuerra@brocker.co.nz wrote:
> Hi all,
> 
> I'm trying to compile Java files.  Then I have
> 
> .SUFFIXES = .java .class
> 
> all: Base.class
> 
> .java.class:
>      javac $<
> 
> My question is, how can I tell "make" to look NOT in the current directory
> for Base.class for the comparison??  I like to separate source code from
> classes.  But I don't like 'make' to remake the whole thing because it
> couldn't find the target class.
> 
> THanks in advance,
> 
> Carlos.
> cguerra@brocker.nz.co
> 
> PS: please reply to my email as well ;-)
> 

Check the make documentation for a variable called VPATH.

Cheers,

=====
Earnie Boyd
mailto:earnie_boyd@yahoo.com

---         < http://earniesystems.safeshopper.com >         ---
--- Cygwin: POSIX on Windows < http://gw32.freeyellow.com/ > ---
---   Minimalist GNU for Windows < http://www.mingw.org/ >   ---

__________________________________________________
Do You Yahoo!?
Thousands of Stores.  Millions of Products.  All in one Place.
http://shopping.yahoo.com/

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

make question

[CGuerra]

Hi all,

I'm trying to compile Java files.  Then I have

.SUFFIXES = .java .class

all: Base.class

.java.class:
     javac $<

My question is, how can I tell "make" to look NOT in the current directory
for Base.class for the comparison??  I like to separate source code from
classes.  But I don't like 'make' to remake the whole thing because it
couldn't find the target class.

THanks in advance,

Carlos.
cguerra@brocker.nz.co

PS: please reply to my email as well ;-)


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

Re: Make question

[Earnie Boyd]

export MAKE_MODE=win32 or remove the MAKE_MODE variable.  This will
use the DOS path style.  You can also execute make from the DOS shell.



---Andrew Cowan <rxst50@email.sps.mot.com> wrote:
>
> Why does the following makefile fail to build 'foo.lib2'???
> 
> I thought I read somewhere that cygwin make would understand
> Dos style pathnames - is this incorrect????
> 
> > # If the lib file exists in c:\temp, copy
> > # it to cwd.
> > 
> > %.lib1 :: //c/temp/%.lib
> > 	@echo xcopy /d /i /f /r $^ $@
> > %.lib2 :: c:\temp\%.lib
> > 	@echo xcopy /d /i /f /r $^ $@
> > %.lib3 :: /temp/%.lib
> > 	@echo xcopy /d /i /f /r $^ $@
> > 
> > bash-2.01$ make -k -f a.mak -r --win32 foo.lib1 foo.lib2 foo.lib3
> > xcopy /d /i /f /r //c/temp/foo.lib foo.lib1
> > make: *** No rule to make target `foo.lib2'.
> > xcopy /d /i /f /r /temp/foo.lib foo.lib3
> 
> If it is true that Dos pathnames are not allowed, then the
> previous example demonstrates the problem with using Unix
> style pathnames: you can't call a Windows program with Unix
> style pathnames.  For example if I remove the "echo" from
> the last target (so that it calls xcopy), then run the makefile
> I get a syntax error (because xcopy does not like the Unix
> style pathname it was given):
> 
> > bash-2.01$ make -k -f a.mak -r --win32 foo.lib1 foo.lib2 foo.lib3
> > xcopy /d /i /f /r //c/temp/foo.lib foo.lib1
> > make: *** No rule to make target `foo.lib2'.
> > Invalid switch - /foo.lib
> > make: *** [foo.lib3] Error 4
> 
> Please send a clue: I need to use GNU Make in --win32 mode, and
> use Dos style pathnames in target-depend rules so that I can
> call commands using the target and dependency paths.  Am I hosed?
> Is there a magical way to convert Unix paths to Dos paths built-in
> to cygwin make?
> 
> -Andy Cowan
> -
> For help on using this list (especially unsubscribing), send a
message to
> "gnu-win32-request@cygnus.com" with one line of text: "help".
> 

_________________________________________________________
DO YOU YAHOO!?
Get your free @yahoo.com address at http://mail.yahoo.com

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

Make question

[Andrew Cowan]

Why does the following makefile fail to build 'foo.lib2'???

I thought I read somewhere that cygwin make would understand
Dos style pathnames - is this incorrect????

> # If the lib file exists in c:\temp, copy
> # it to cwd.
> 
> %.lib1 :: //c/temp/%.lib
> 	@echo xcopy /d /i /f /r $^ $@
> %.lib2 :: c:\temp\%.lib
> 	@echo xcopy /d /i /f /r $^ $@
> %.lib3 :: /temp/%.lib
> 	@echo xcopy /d /i /f /r $^ $@
> 
> bash-2.01$ make -k -f a.mak -r --win32 foo.lib1 foo.lib2 foo.lib3
> xcopy /d /i /f /r //c/temp/foo.lib foo.lib1
> make: *** No rule to make target `foo.lib2'.
> xcopy /d /i /f /r /temp/foo.lib foo.lib3

If it is true that Dos pathnames are not allowed, then the
previous example demonstrates the problem with using Unix
style pathnames: you can't call a Windows program with Unix
style pathnames.  For example if I remove the "echo" from
the last target (so that it calls xcopy), then run the makefile
I get a syntax error (because xcopy does not like the Unix
style pathname it was given):

> bash-2.01$ make -k -f a.mak -r --win32 foo.lib1 foo.lib2 foo.lib3
> xcopy /d /i /f /r //c/temp/foo.lib foo.lib1
> make: *** No rule to make target `foo.lib2'.
> Invalid switch - /foo.lib
> make: *** [foo.lib3] Error 4

Please send a clue: I need to use GNU Make in --win32 mode, and
use Dos style pathnames in target-depend rules so that I can
call commands using the target and dependency paths.  Am I hosed?
Is there a magical way to convert Unix paths to Dos paths built-in
to cygwin make?

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