input): Fix regression in handling macro
without arguments as last token in file; debian bug 385720.
(next_token): Always consume an input character.
Reported by Andreas Schultz.
* configure.ac (AC_INIT): Bump version number.
* NEWS: Document this fix.
Eric Blake <[EMAIL PROTECTED]> writes:
> In the meantime, perhaps Autoconf should document that
> all autom4te input files should always end in newline.
Nh. Let's just fix the bug in M4. It's clearly a bug.
The GNU tradition is to handle arbitrary input files,
and not to insist on "text" fi
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[adding autoconf to cc]
According to Santiago Vila on 9/3/2006 6:55 AM:
> Andreas Schultz <[EMAIL PROTECTED]> writes:
>
> m4 crashes with "m4: INTERNAL ERROR: recursive push_string"
>
> Later, he adds:
>
> It seems that the problem is reproduci
severity 385720 serious
thanks
Just in case, I'm raising the severity to serious to keep m4 1.4.4 in testing,
as we don't know how much this bug might affect other packages.
[ However, this should not be considered RC for etch, as 1.4.4 is in a
releaseable state ].
--
To UNSUBSCRIBE, email t
On Saturday 02 September 2006 18:03, Santiago Vila wrote:
[...]
> You don't have to pinpoint the source of the problem, as m4 has upstream
> maintainers who know the code very well.
>
> What I need (before forwarding this report to them) is a way to reproduce
> it, something like "when I run m4 o
On Sat, 2 Sep 2006, Andreas Schultz wrote:
> Subject: m4: INTERNAL ERROR: recursive push_string
> Package: m4
> Version: 1.4.6-1
> Severity: important
>
> *** Please type your report below this line ***
>
> m4 crashes with "m4: INTERNAL ERROR: recursive push_string"
>
> I don't know how to pinp
Subject: m4: INTERNAL ERROR: recursive push_string
Package: m4
Version: 1.4.6-1
Severity: important
*** Please type your report below this line ***
m4 crashes with "m4: INTERNAL ERROR: recursive push_string"
I don't know how to pinpoint the exact source of this problem, please advice
Andreas
-
7 matches
Mail list logo
