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

2018-08-20 Thread Andreas Schwab
On Aug 17 2018, Mark Galeck 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 som

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

2018-08-20 Thread Paul D. Smith
Update of bug #54529 (project make): Status:None => Not A Bug Open/Closed:Open => Closed ___ Follow-up Comment #4: This message: $ make

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

2018-08-20 Thread Mark Galeck
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 To: Mark Galeck ; psm...@gnu.org; bo...@kolpackov.net; bug-make@gnu.org Sent: Monday, August 2

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

2018-08-20 Thread Mark Galeck
No problem, thank you for explaining.  I still think that Make if it invokes a program directly, and the program crashes, Make should say something that will help the user understand it is not Make bug.  There has to be a way to print a more informative error message.  Does the error message as