Re: GNU Make 4.3: Makefile rule spooky action at a distance

2020-10-05 Thread Henrik Carlqvist
On Mon, 5 Oct 2020 22:48:56 +0200 Danny Milosavljevic wrote: > Hi, > > On Mon, 05 Oct 2020 15:41:52 -0400 > Paul Smith wrote: > > > It would be interesting to know if adding an explicit export solves the > > problem. > > I tried adding an explicit export at the toplevel makefile right befor

Re: GNU Make 4.3: Makefile rule spooky action at a distance

2020-10-05 Thread Danny Milosavljevic
Hi, On Mon, 05 Oct 2020 15:41:52 -0400 Paul Smith wrote: > It would be interesting to know if adding an explicit export solves the > problem. I tried adding an explicit export at the toplevel makefile right before the invocation of the submake--it does not solve the problem. Behavior is ex

Re: GNU Make 4.3: Makefile rule spooky action at a distance

2020-10-05 Thread Paul Smith
On Mon, 2020-10-05 at 15:14 -0400, Jeffrey Walton wrote: > > $ CFLAGS=ok make > > I think you need to export CFLAGS. Or that is where I would look. > CFLAGS is set in the first shell, but it is not inherited in child > shells. It should be: the value is set in the environment when make starts and

Re: GNU Make 4.3: Makefile rule spooky action at a distance

2020-10-05 Thread Jeffrey Walton
On Sun, Oct 4, 2020 at 9:32 AM Danny Milosavljevic wrote: > > Hi, > > I just got a build failure in lz4. I've isolated it and made a minimal test > case, see below. > > This is on GNU Guix on a x86_64 machine. > > The reason is that apparently one Makefile rule can unwittingly change how > anot