On Wed, 2016-04-06 at 13:28 -0700, Dale Stimson wrote:
> I suggest the patch below. I have tested this and it works for me.
Ah, that was my bad with a recent change. It only shows up if your
makefile path is sufficiently long, which unfortunately none of the
regression test suite paths are. Tha
Using make 4.1.90 from the gnu git repoository with current HEAD commit ==
5bd7ad2b225bf9229ca96ba63b90f8094a2becde, the following diagnostic message
was received.
make: output.c:667: error: Assertion `fmtbuf.buffer[len-1] == '\0'' failed.
Investigation showed that in job.c, function child_error,
I believe this bug has been fixed in the source code for GNU make. It
will be available in the next release.
--
---
Paul D. Smith <[EMAIL PROTECTED]> Find some GNU make tips at:
http://www.gnu.org
Ok...
I'm just a beginner with make, but while I was trying to make the
following makefile, make aborted the compilation complaining about
an assertion failed in its code (not mine). Maybe I did something nasty, but I
believe it should report my error instead of saying 'assert
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I was able to create a core dump by using make version 3.79.1. It was part of
SuSE 7.2. Afterwards I recompiled it with debug symbols and could reproduce
it. Here is the call I use:
snsrv053:nardmann[libcryptdev]>make
(cd include; ln -sf "../../ker
This is PR/1586. It has been fixed in GNU make 3.79 which was just
released; however it's so new that it hasn't been moved to the GNU ftp
site yet.
You can wait a few days for it to show up, or you can apply this patch,
from the bug report above (hopefully not too mangled by various cuts and
pas
*
When running GNU make 3.77 OR 3.78 I get the following.
Config.h and the makefile it's referencing
follow below.
******
Assertion failed: *p2 != '\0', file r
