OK, just to clarify sorry, the issue here is that MAKEFLAGS are propagated down to any sub-shells from my main command line? So I can work around this by just clearing MAKEFLAGS in my call to subprocess.run() when I pass in the env. Is that the only way to run a "clean" make command from a sub-shell?
On Thu, May 6, 2021 at 5:08 PM Shareef Jalloq <shar...@jalloq.co.uk> wrote: > Ah ok, thanks all. I had no idea that command line args were treated > differently to environment variables. I'll read up on overrides. > > Cheers. > > On Thu, May 6, 2021 at 5:01 PM Paul D. Smith <invalid.nore...@gnu.org> > wrote: > >> Update of bug #60538 (project make): >> >> Status: None => Not A Bug >> >> Open/Closed: Open => Closed >> >> >> _______________________________________________________ >> >> Follow-up Comment #5: >> >> As Martin says, if the variable is set ON THE COMMAND LINE, it will >> absolutely >> take precedence over the setting in a makefile variable (unless overridden >> with override). >> >> But, you said you has set this IN THE ENVIRONMENT which is very different; >> values set in the environment should not take precedence over values set >> in >> the makefile (as long as -e is not set). >> >> So, you'll have to investigate why/how this variable assignment is >> appearing >> in your command line (in MAKEFLAGS). >> >> I'm going to close this; you can continue to post here but better would >> be to >> discuss on the mailing list, until/unless we discover a bug. >> >> Cheers! >> >> _______________________________________________________ >> >> Reply to this item at: >> >> <https://savannah.gnu.org/bugs/?60538> >> >> _______________________________________________ >> Message sent via Savannah >> https://savannah.gnu.org/ >> >>
