[bug #26593] Assertion failure when building glibc with CVS make

2009-06-03 Thread Paul D. Smith
Update of bug #26593 (project make): Status:None => Fixed Assigned to:None => psmith Open/Closed:Open => Closed Fixed Release:

[bug #26593] Assertion failure when building glibc with CVS make

2009-05-19 Thread Mark Seaborn
Follow-up Comment #2, bug #26593 (project make): Here's a smaller test case: $ cat test.make all: foo.suffix1 foo.suffix2 prefix1.foo prefix2.foo prefix1.% prefix2.%: %.original @echo $@ %.suffix1 %.suffix2: %.original @echo $@ .PHONY: foo.original # Expected output $ make -

[bug #26593] Assertion failure when building glibc with CVS make

2009-05-16 Thread Mark Seaborn
Follow-up Comment #1, bug #26593 (project make): I notice that this bug was reported previously but without a fix being proposed: http://www.mail-archive.com/bug-make@gnu.org/msg04620.html "Make fails on glibc build" By the way, the previous message was posted by me (m...@mythic-beasts.com) but

[bug #26593] Assertion failure when building glibc with CVS make

2009-05-16 Thread anonymous
URL: <http://savannah.gnu.org/bugs/?26593> Summary: Assertion failure when building glibc with CVS make Project: make Submitted by: None Submitted on: Sat 16 May 2009 14:19:19 UTC Severity: 3 - Normal

Re: make: expand.c:489: allocated_variable_append: Assertion failure

2002-02-21 Thread Paul D. Smith
I believe this patch fixes this problem. It does for me anyway. --- make-3.79.1/expand.cMon Jun 19 16:23:57 2000 +++ make/expand.c Wed Jan 17 13:28:41 2001 @@ -92,7 +92,7 @@ /* Recursively expand V. The returned string is malloc'd. */ -static char *allocated_variable_appen

make: expand.c:489: allocated_variable_append: Assertion failure

2002-02-21 Thread Manoj Srivastava
Hi, [Please retain the CC to [EMAIL PROTECTED] so that the Debian Bug Tracking system can record your input] This has been reported by a debian user. Consider this minimal makefile: == e

Re: assertion failure

2001-03-15 Thread Paul D. Smith
%% Eric Hanchrow <[EMAIL PROTECTED]> writes: eh> make version 3.78.1 eh> My Makefile contains exactly three characters -- a backslash, a eh> space, and a colon. eh> Typing `make' yields this: eh> make: read.c:892: read_makefile: Assertion `*p2 != '\0'' failed. eh> Aborted (core

assertion failure

2001-03-15 Thread Eric Hanchrow
make version 3.78.1 My Makefile contains exactly three characters -- a backslash, a space, and a colon. Typing `make' yields this: make: read.c:892: read_makefile: Assertion `*p2 != '\0'' failed. Aborted (core dumped) For what it's worth, I do not see this behavior with 3.79.1

Re: make assertion failure with target-specific variables

2001-02-01 Thread Paul D. Smith
%% Manoj Srivastava <[EMAIL PROTECTED]> writes: ms> make 3.79.1 fails with an assertion error when a target-specific ms> variable append is combined with setting the variable on the make ms> command line. Thanks for the report. This bug has already been fixed as a side-effect of another f

make assertion failure with target-specific variables

2001-01-30 Thread Manoj Srivastava
Hi, This may be a repeat for some of the people addressed by this message. I think I may have sent it out with the wrong addresses (that should teach me to try and deal with my packages at 3:30am) [Please retain a CC to [EMAIL PROTECTED], so that the Debian Bug tracking

Re: Assertion failure in make 3.78.1

2000-06-01 Thread Paul D. Smith
This is PR/1586, already fixed in the latest release of GNU make. -- --- Paul D. Smith <[EMAIL PROTECTED]> Find some GNU make tips at: http://www.gnu.org http://www.ultranet.com/~pauld/gma

Assertion failure in make 3.78.1

2000-06-01 Thread Evan Deaubl
We have run into a bug with GNU make 3.78.1 where it fails an assertion trying to parse a particular Makefile. As suggested, we have reduced the makefile to the smallest one possible that still exhibits the bug. That makefile is attached. The expected output (as per make 3.77) is: make: Nothin