Follow-up Comment #6, bug#65359 (group make):
Hi, Martin,
Yes, you are right. My previous understanding was wrong. Exported variables in
makefile can be seen by the recipes, as stated in make manual,
"To pass down, or export, a variable, make adds the variable and its value to
the environment fo
Follow-up Comment #5, bug#65359 (group make):
Hi, Dmitry,
Got it. This explains the test result well.
[comment #3 comment #3:]
> Exporting a make variable makes it available for shell in recipes.
>
> Removal of a semicolon allows make to avoid shell. Instead makes calls
posix_spawn or fork and
Follow-up Comment #4, bug#65359 (group make):
As demonstrated by eg:
martind@stormy:~/tmp/make-65359$ cat Makefile
export BADGER = wombat
default:; echo BADGER = $$BADGER
martind@stormy:~/tmp/make-65359$
Variables are communicated to subprocesses, be they Make, the shell or
otherwise, via the
Follow-up Comment #3, bug#65359 (group make):
Exporting a make variable makes it available for shell in recipes.
Removal of a semicolon allows make to avoid shell. Instead makes calls
posix_spawn or fork and exec.
___
Reply to this item a
Follow-up Comment #2, bug#65359 (group make):
Hi, Martin,
Normally make variables are different with shell variables. Exported shell
variables can be seen by make. However, exported make variables cannot be seen
by shell in recipes.
I don't know whether submake gets make exported variables via sh
