Here's what I am doing:
Under the BASH shell I cannot get the "bash configure --disable-shared"
command to get pass testing the object suffix. What's more strange is
that if I run the same command in a DOS shell, the makefile gets
created, although one line of the bash configure output was:
checking whether make sets ${MAKE}... Bad command or filename
no
Then it completes and creates the Makefile okay. I have then added the
VPATH variable. Running this makefile with "make -f Makefile" in the
DOS shell produces different results from running in the BASH shell:
Under DOS shell:
The makefile tries to compile each C file into an object file, and
after each compile line the error: "Bad command or filename" keeps
occuring. Then when it eventually tries to compile the static library
it falls over since none of the object files have been created. I
can't help but think that this problem may be related to the earlier
problem when creating the Makefile, i.e. that ${MAKE} line.
cl -help gives me all the C/C++ compiler options - so my cl.exe is
pathed okay.
Any ideas what this could be?
Under BASH shell:
The first compile line causes an error: Command Line error: D2030
INTERNAL COMPILER ERROR in D:/......../cl.exe. Please call Technical
Support, etc, etc. I presume from this that you are NOT supposed to
run the make file from the BASH shell.
I am using MSVC 6.0 Enterprise Edition. The makefile does not run with
NMAKE in VC++ itself.
Thanks for any help,
--Ben
--
Ben Wimpory
ARC Cores Ltd.
email: ben.w...@arccores.com
http://www.arccores.com
Sent via Deja.com http://www.deja.com/
Share what you know. Learn what you don't.