[Top][All Lists]

[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: Bill Hoffman
Subject: Re: Bug in the expansion of $(MAKE) in GNU make 3.81
Date: Thu, 16 Nov 2006 13:53:44 -0500
User-agent: Thunderbird (Windows/20061025)

Benoit Sigoure wrote:
Hello people,

I am under cygwin and compiled my own GNU make 3.81 from source with this patch

$ uname -a
CYGWIN_NT-5.1 bf-winxp 1.5.21(0.156/4/2) 2006-07-30 14:21 i686 Cygwin
$ make --version
GNU Make 3.81
Copyright (C) 2006  Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A

This program built for i686-pc-cygwin
$ cat Makefile
        echo $(MAKE)
        $(MAKE) foo

        echo foo

Calling make with an absolute UNIX path works as expected:
$ /usr/local/bin/make
echo /usr/local/bin/make
/usr/local/bin/make foo
make[1]: Entering directory `/tmp/mk/3'
echo foo
make[1]: Leaving directory `/tmp/mk/3'

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 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.

In case you'd need it, I put the output of make --debug=a @


I see the same thing, and have seen this with mingw make as well.
The MAKE variable seems to get the current directory added to it for some reason.


reply via email to

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