Skip to main content
Unix & Linux

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

9
  • No that's entirely not the case, entire PATH seems not propagated. Commented May 10, 2016 at 9:03
  • But with a tilde inside and that tilde gets expanded to $HOME later in the shell in case you add PATH=$(PATH). Commented May 10, 2016 at 11:23
  • Yes, so there is totally no problem with expansion. Commented May 10, 2016 at 12:10
  • So you now understand my answer that explains why you need to pass the PATH= assignment to the shell? Commented May 10, 2016 at 12:17
  • And you seem missed, totally, that is the problem here. Observed behavior is because any variable is not propagated to shell's environment automatically. If you do $(shell var=$(var) command) you just execute string in shell 'var=value_of_gmake_var command' which is interpreted by shell as 'set var to value_of_gmake and execute command', so that effectively propagation of single variable. Hope now it is clear? Commented May 10, 2016 at 12:53