[Top][All Lists]

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

Re: FYI: fix m4_cdr

From: Ralf Wildenhues
Subject: Re: FYI: fix m4_cdr
Date: Thu, 9 Jun 2005 09:20:53 +0200
User-agent: Mutt/1.4.1i

Hi Paul,

* Paul Eggert wrote on Wed, Jun 08, 2005 at 11:13:37PM CEST:
> Ralf Wildenhues <address@hidden> writes:
> > Now while I've seen the recommendation for 1.4.3, this is still going to
> > bother people.
> That's unfortunate, but I'm afraid we'll have to bother them, if it's
> an M4 version issue.  In my experience M4 1.4.1 is seriously buggy, at
> least on some platforms, and it's not worth our time to attempt to
> work around the bugs.

Fair enough.

> I am assuming here that the problem you observed is related to M4
> versions.  If it's something else then we should fix it.

I've tested now (sorry for not doing that earlier).  It's something
else.  For now I can only presume it's bug in the Libtool m4 macros
(manifests itself with branch-2-0 and HEAD of Libtool).  Thanks for
making me look again!

I have no idea yet how to localize this guy, so here goes a copy for the
libtool-patches list:  This patch[1] causes bootstrapping of Libtool
branch-2-0/HEAD to fail.  I presume a bug in our macros.  The failure is
(./bootstrap output):

| autoreconf: Entering directory `.'
| autoreconf: not using Gettext
| autoreconf: running: aclocal --force -I m4
| /usr/local/bin/m4: ERROR: Recursion limit of 1024 exceeded, 
use -L<N> to change it
| autom4te: /usr/local/bin/m4 failed with exit status: 1



reply via email to

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