Update of bug #30323 (project make):
Severity: 3 - Normal => 2 - Minor
Item Group: Bug => Enhancement
Status: None => Wont Fix
Operating System: MS Windows => Any
Triage Status: None => Verified
_______________________________________________________
Follow-up Comment #8:
Your example exactly reproduces what the comment says: since the current
directory is implicitly always on PATH on Windows, the Make executable is
found in the current directory, and the Makefile does not work.
The same happens on GNU/Linux if you prepend "." to PATH:
$ mkdir mktest && cd mktest
$ cp -p /bin/make ./mak1
$ export PATH=.:"$PATH"
$ mkdir subdir
$ mak1 -f-
all:
cd subdir && $(MAKE)
^D
cd subdir && mak1
/bin/sh: mak1: not found
mak1: *** [all] Error 127
Therefore, I submit that the Windows port behaves exactly like Make behaves on
Posix platforms in this case. If the Posix code is modified to work around
this failure, I will then consider changing the Windows code to follow suit.
_______________________________________________________
Reply to this item at:
<http://savannah.gnu.org/bugs/?30323>
_______________________________________________
Message sent via/by Savannah
http://savannah.gnu.org/
_______________________________________________
Bug-make mailing list
Bug-make@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-make
