Follow-up Comment #11, bug #9062 (project make):
A reminder: this bug is a request for a variable whose value is the full path
of the directory containing the Makefile, regardless of what the current
directory is or how it got that way with -C, etc.
There has been much discussion of the current
Follow-up Comment #10, bug #9062 (project make):
GNU make does not and has never supported a built-in variable $(PWD).
Of course, GNU make does now and has always (just like every other make)
imported environment variables exported from the invoking process into GNU
make variables, and some shel
Follow-up Comment #9, bug #9062 (project make):
What is the difference between ${PWD}, which was supported by
GNU make for many years, and ${CURDIR}, which was introduced in
release 3.76.1? If there is no difference, why the new variable
was introduced? It is not just my curiosity :-). We plan to
Follow-up Comment #8, bug #9062 (project make):
Even simpler is to look at the NEWS file; all user-visible changes should be
documented there:
Version 3.80
...
* A new built-in variable is defined, $(MAKEFILE_LIST). [...]
...
Version 3.77
...
* Make defines a new variable, "CURDIR"
Follow-up Comment #7, bug #9062 (project make):
>From the make ChangeLog:
2002-10-03 Paul D. Smith <[EMAIL PROTECTED]>
Version 3.80 released.
2002-06-06 Paul D. Smith <[EMAIL PROTECTED]>
...
* read.c (read_all_makefiles): Create a new built-in variable,
MAKEFILE_LIS
Follow-up Comment #6, bug #9062 (project make):
I tried to use ${CURDIR} and ${MAKEFILE_LIST} with a GNU make
on Solaris, but these variables are empty. In what version of
GNU make they appear? I think they work in 1.80, correct?
Here is what I tried:
% uname -a
SunOS volga2 5.9 Generic_112233
