make-w32
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Bug in the expansion of $(MAKE) in GNU make 3.81


From: Benoit Sigoure
Subject: Re: Bug in the expansion of $(MAKE) in GNU make 3.81
Date: Fri, 17 Nov 2006 16:17:45 +0100
User-agent: Internet Messaging Program (IMP) H3 (4.0.2)

Quoting Earnie Boyd <address@hidden>:

Quoting Eli Zaretskii <address@hidden>:

Date: Thu, 16 Nov 2006 12:42:49 +0100
From: Benoit Sigoure <address@hidden>

However if the absolute path is Windows-style, something very weird happens:

$ C:/cygwin/usr/local/bin/make
echo /tmp/mk/3/C:/cygwin/usr/local/bin/make
/tmp/mk/3/C:/cygwin/usr/local/bin/make
/tmp/mk/3/C:/cygwin/usr/local/bin/make foo
make: /tmp/mk/3/C:/cygwin/usr/local/bin/make: Command not found
make: *** [all] Error 127

where "/tmp/mk/3" is the current working directory.

Thank you for your report.  I will try in a few days to find where
this problem happens.  If you could step through the relevant code
with a debugger and tell what you see, it will help (I don't have
Cygwin installed, so cannot do this myself).


FWIW, you're barking at a long standing Cygwin issue. The mix of POSIX and Win32 paths in the Makefile will cause issues. Do you have a sample Makefile that gives this?



I'm not sure to understand your question... If you're wondering where does all
this come from, check out this thread from ML-Libtool:
http://lists.gnu.org/archive/html/libtool/2006-11/msg00018.html

--
SIGOURE Benoit aka Tsuna
  _____
 /EPITA\ Promo 2008, LRDE





reply via email to

[Prev in Thread] Current Thread [Next in Thread]