Then why does the error say "make: ***" ? Shouldn't Make be more robust and
assertive in such a case, if a child crashes, to inform the user that it is not
Make code?
From: Andreas Schwab <sch...@suse.de>
To: Mark Galeck <mark_gal...@pacbell.net>; psm...@gnu.org;
bo...@kolpackov.net; bug-make@gnu.org
Sent: Monday, August 20, 2018 12:44 AM
Subject: Re: [bug #54529] [Makefile:5: foobar] Segmentation fault
On Aug 17 2018, Mark Galeck <invalid.nore...@gnu.org> wrote:
> For this Makefile:
>
> ROOT := ${shell echo
> /home/mgaleck/ws/mgaleck_build/mgaleck_build_refactor2/target | sed s/t/t/}
> export LD_LIBRARY_PATH := ${ROOT}/usr/lib64:${LD_LIBRARY_PATH}
>
> foobar:
> touch $@
>
>
> and file foobar missing, then on some Linux distributions, I get this:
>
> $ make-4.2.1/make
> touch foobar
> make: *** [Makefile:5: foobar] Segmentation fault (core dumped)
Which means that the executed command has crashed, probably because of
some incompatible libraries in the LD_LIBRARY_PATH as set above.
Nothing to do with make.
Andreas.
--
Andreas Schwab, SUSE Labs, sch...@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
_______________________________________________
Bug-make mailing list
Bug-make@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-make
