On Tuesday, July 06, 2010 00:13:55 Eric Blake wrote:
> - "Mike Frysinger" wrote:
> > i believe a recent autoconf update triggered a bug in m4 while
> > processing
> > crappy m4 code. the project in question is "rezound":
> > http://rezound.sf.net/ (version 0.12.3_beta to be exact)
> >
> > th
- "Mike Frysinger" wrote:
> > That's a bug in the user's configure.ac script for not quoting
> things
> > correctly in the first place. Autoconf can't work around every
> > piece of bad code thrown at it, and my recommendation would
> > be to fix rezound rather than trying to throw more worka
On Tuesday, July 06, 2010 08:56:12 Eric Blake wrote:
> "Mike Frysinger" wrote:
> > but i think m4 should be smarter about infinite loops. this could just as
> > easily been a typo and about the only way to track it down is to literally
> > start commenting out things in the source until it stops
- "Mike Frysinger" wrote:
> > What you're asking for is a solution to the halting problem.
> you obviously know better than i as ive never looked at the m4
> internals but
> you cant even use the existing nesting-limit option ? autoconf
> already runs
> m4 with --nesting-limit=1024 which m
