[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [bug #54529] [Makefile:5: foobar] Segmentation fault

From: Mark Galeck
Subject: Re: [bug #54529] [Makefile:5: foobar] Segmentation fault
Date: Tue, 21 Aug 2018 06:32:14 +0000 (UTC)

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 <address@hidden>
To: Mark Galeck <address@hidden>; address@hidden; address@hidden; address@hidden
Sent: Monday, August 20, 2018 12:44 AM
Subject: Re: [bug #54529] [Makefile:5: foobar] Segmentation fault

On Aug 17 2018, Mark Galeck <address@hidden> 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 Schwab, SUSE Labs, address@hidden
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE  1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."

reply via email to

[Prev in Thread] Current Thread [Next in Thread]