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

Brian, the only thing that got "lost" was the tab before the recipe.  Everything else is as intended, I checked that.   Yes it is the nature of an SSCCE that it "does not make sense", that is intentional, because the example is pared down to the smallest possible that reproduces the problem.   Y

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

I forgot to finish before hitting send. I'm unable to reproduce this in RHEL6 with make 4.1 or Solaris 10 with make 4.2.1. Generally it's considered a bad idea / poor form to use LD_LIBRARY_PATH. This could easily explain why we cannot reproduce it. If you have something in that path that someh

[bug #52697] More varieties to -j switch

Follow-up Comment #3, bug #52697 (project make): I'm pretty sure something like this was already proposed, discussed and/or even implemented somewhere, but anyway: here is a quick and dirty hack I'm using to successfully compile gcc (together with some other required measures) on my raspberry pi

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

> OK, the only system for which this bugs actually shows up, is work build > server, and unfortunately, the IT guy does not know where the cores are, and > gdb is not working. Let me talk to him about fixing gdb and I will get back > to you what I find from it. This may depend on the distribution

[bug #54533] Touching an archive member leaves a NUL byte after date field

URL: Summary: Touching an archive member leaves a NUL byte after date field Project: make Submitted by: None Submitted on: Sat 18 Aug 2018 03:01:18 PM UTC Severity: 3 - Normal