mirror/autoconf
2
0
Fork 0
mirror of git://git.sv.gnu.org/autoconf synced 2025-01-18 10:45:15 +08:00
Code Issues Packages Projects Releases Wiki Activity

* doc/autoconf.texi (Limitations of Make): `foo=bar make -e'

Browse Source 
is not portable inside Makefile.
This commit is contained in:
Alexandre Duret-Lutz 2003-02-20 17:19:55 +00:00
parent 13984e2d07
commit e547c06fa2
2 changed files with 17 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
ChangeLog
View File

@ -1,3 +1,8 @@
2003-02-20 Alexandre Duret-Lutz <adl@gnu.org>
* doc/autoconf.texi (Limitations of Make): `foo=bar make -e'
is not portable inside Makefile.
2003-02-20 Akim Demaille <akim@epita.fr>
* lib/autoconf/headers.m4 (_AC_CHECK_HEADER_MONGREL): When

17
doc/autoconf.texi
View File

@ -10811,8 +10811,8 @@ line with @code{#}, not only the first.
A command-line variable definition such as @code{foo=bar} overrides any
definition of @code{foo} in the @file{Makefile}. Some @command{make}
implementations (such as @acronym{GNU} @command{make}) will propagate this
override to sub-invocations of @command{make}. This is allowed but not
required by @acronym{POSIX}.
override to sub-invocations of @command{make}. Some other implementation
will not pass the substitution along to sub-@command{make}s.
@example
% @kbd{cat Makefile}
@ -10849,9 +10849,16 @@ and since the environment is inherited between @command{make}
invocations, the @code{foo} macro will be overridden in
sub-@code{make}s as expected.
Using @code{-e} could have unexpected side-effects if your environment
contains some other macros usually defined by the Makefile. (See
also the note about @code{make -e} and @code{SHELL} below.)
This syntax (@code{foo=bar make -e}) is portable only when used
outside a @file{Makefile}, for instance from a script or from the
command line. When run inside a @command{make} rule, GNU
@command{make} 3.80 and prior versions forget to propagate the
@code{-e} option to sub-@command{make}s.
Moreover, using @code{-e} could have unexpected side-effects if your
environment contains some other macros usually defined by the
Makefile. (See also the note about @code{make -e} and @code{SHELL}
below.)
Another way to propagate overrides to sub-@command{make}s is to do it
manually, from your @file{Makefile}: