[I don't know how to make nabble cc the OP, and I didn't get the original message to do a reply-all from my inbox]
> > I made sure my autoconf was up-to-date and did an autoreconf -f. > > Still isn't right. Correct. The bug is not what version of autoconf you are using, but what version of m4/m4.m4 used in the copy of bison you are using. And has already been pointed out in this thread, you can use ./configure M4=/path/to/m4 to work around the bug. > > > > Do you know which version of m4 is the lowest that works? I could > > write a macro that checks the m4 version and pitch it to the autoconf > > team. M4 1.4.5 or newer. The autoconf team already has this macro written, and in fact, the latest bison already uses it. -- Eric Blake -- View this message in context: http://www.nabble.com/Detecting-%28g%29m4-tp24510063p24548008.html Sent from the Gnu - Bison - Bugs mailing list archive at Nabble.com.
