autoconf-patches
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

using older m4 (was: [PATCH] Fix treatment of --enable-assert in AC_HEAD


From: Eric Blake
Subject: using older m4 (was: [PATCH] Fix treatment of --enable-assert in AC_HEADER_ASSERT)
Date: Tue, 9 Dec 2008 15:18:46 +0000 (UTC)
User-agent: Loom/3.14 (http://gmane.org/)

William Pursell <bill.pursell <at> gmail.com> writes:

> I assumed Bill did the full run...
> 
> The only failure I get is an "unbalanced m4_divert_push", which
> I believe is a spurious error coming from other changes in my
> source dir.  (Or rather, 'believed'.)  How is it that this
> patch causes that error?

What version of m4 are you using?

> -script.4s:2: error: m4_init: unbalanced m4_divert_push:
> +:0: error: m4_init: unbalanced m4_divert_push:

Thanks for the bug report.  The testsuite is (wrongly) assuming that you are 
using m4 1.4.8 or newer, where errors issued during the context of m4wrap bear 
the file and line of the point that issued the wrap.  But since we claim to 
work with m4 1.4.5, I need to beef up the testsuite (and probably also m4sugar, 
since ":0:" instead of "file:line:" looks bogus) to handle older m4, where 
m4wrap did not carry useful location information.

-- 
Eric Blake






reply via email to

[Prev in Thread] Current Thread [Next in Thread]