On Wed, Jul 17, 2019 at 12:38 PM Paul Smith wrote:
...
> The only idea I have so far is to try to detect when this situation
> occurs (by looking for the 127 exit status) then using stat() to check
> to see if the binary exists (I suppose I need to check for executable
> status) and generating
So over the weekend I started some testing on different systems just to
get a feel for where the code is, portability-wise.
I discovered that the enhancement to use posix_spawn instead of
fork/exec results in a number of failed regression tests on older
systems.
The problem doesn't appear on
Evidently, assignments to pattern-specific simple variables don't build on
top of each other, but in fact only the last one wins. So, for instance:
CFLAGS := -Wall
%.o: CFLAGS := $(CFLAGS) -march=haswell
%.o: CFLAGS := $(CFLAGS) -Werror
foo.o: foo.c
$(CC) $(CFLAGS) -c $< -o $@
drops
