%% [EMAIL PROTECTED] writes:
rw> Sorry for the missing information, but I use (a part of ) the
rw> precompiled cygwin toolset
Ah. The Cygwin version of GNU make is not identical to the standard GNU
make distributed by the FSF. You should talk to the people at Cygwin
about it.
I know next
Dear Paul,
Sorry for the missing information, but I use (a part of ) the precompiled cygwin
toolset,
I was pleasantly surprised that make 3.79 did not pass the /cygdrive/c in the
pathname,
but this VPATH problem remained.
Reading your mail, I may have addressed the problem to the wrong
If you've built your Windows version of make for Windows32 then I think
this is (or should be) all handled automatically.
See the README.W32 file for a discussion of how GNU make tries to handle
drive specifiers.
--
---
Hi,
I am a very happy user of the gnu tools. I encountered a problem I hope
you have a solution for.
I have software that is built on Unix machines and on PCs and use cygwin to
emulate the Unix environment. I use native compilers, and for the PC this
is the CL compiler from Microsoft's visual
%% Russell Smiley <[EMAIL PROTECTED]> writes:
No need for HTML on the mailing list; thanks.
rs> Please find attached a very simple project that I believe may
rs> illustrate a problem with make and its use of vpath.
It's not a bug; this is how VPATH was designed by those who designed it;
GNU
Please find attached a very simple project that I believe may illustrate
a problem with make and its use of vpath. The README file contains
a description of the problem, and make.log shows the make error output.
I hope it is helpful.
Russell.
--
Russell Smiley
[EMAIL PROTECTED]
makebug.tar.
