By my reading of the documentation, when SHELL is /bin/bash, defining a make
target having BASH_ENV exported as a target-specific variable should cause that
target's recipe to be executed in an shell where the file BASH_ENV points has
been sourced.
And indeed this works in my hands.
However, b
On 2023-12-04 08:50, Cook, Malcolm wrote:
> .PHONY: myTarget
> myTarget: private export BASH_ENV:=desiredEnvironment.sh
I don't have the answer, but I'm just wondering whether order
makes any difference here: what if you write "export private"
rather than "private export"?
I.e. are these just Bo
> I don't have the answer, but I'm just wondering whether order makes any
> difference here: what if you write "export private"
> rather than "private export"?
I had wondered and tested that too. It does not make a difference.
> Might it be that "export" and "private" are just sort of semantic o
Hello,
I now believe this to be a manifestation of [bug #61463: private does not
suppress inheritance on exported target specific
variables](https://savannah.gnu.org/bugs/index.php?61463)
which I now discover has been fixed in [GNU Make 4.4.1
released!](https://lists.gnu.org/archive/html/info-
> I now believe this to be a manifestation of [bug #61463: private does not
> suppress inheritance on exported target specific
> variables](https://savannah.gnu.org/bugs/index.php?61463)
> which I now discover has been fixed in [GNU Make 4.4.1
> released!](https://lists.gnu.org/archive/html/info-gn
