On Fri, Jul 11, 2003 at 07:55:38PM -0700, Christopher Seawood wrote: >Christopher Faylor wrote: > >> Then, we need to know *how*you*are*running*make*. > >We're just typing 'make', which unless something changed, should be the >same as 'make --unix'. 'make -p | grep MAKE_MODE' returns 'MAKE_MODE = >unix'. Hmm. I do see that /etc/profile is setting MAKE_MODE=unix so >that may not be make's default.
If you are just running make, then how could VPATH be expected to translate MS-DOS paths into UNIX paths? >> You don't have to go into exhaustive detail about how mozilla works. >> You just need a (probably) three line makefile and a copy of the make >> command line and, if you are using it, description of the MAKE_MODE >> environment variable setting. >> >> I am not trying to be difficult. I have tried to construct my own test >> case and, AFAICT, it works fine. >> >> I run it like thist: >> >> make --win32 -f mkfile >> >> mkfile contains: >> >> VPATH=c:/tmp >> all: remount.bat >> echo $? >> >> remount.bat exists in c:/tmp. > >That example works fine if I do 'make --win32' but fails when just using >'make'. That is a change in behavior from the previous version of make. > The testcase works with either of --unix & --win32 when using make >3.79.1-7 . As it should. Colon is a path separator. So, to answer your question, yes it is by design that VPATH is not translating MS-DOS paths. If it was doing so before, it was clearly a bug. cgf -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://cygwin.com/docs.html FAQ: http://cygwin.com/faq/
