Ralf Wildenhues wrote:
Hallo Ralf,
We advertise Autoconf-2.50 and Automake-1.4 compatibility within branch-1-5. branch-2-0 does not do that any more, neither has it (most of) your warnings. IIRC there was only one left and it could only be solved with CVS autoconf, not sure ATM.
Great! Thanks a lot, that's excellent news, making me look happily forward to 2.0. :)
Unfortunately, while it is possible to simply autoupdate configure.ac and ltdl.m4 (by calling it configure.ac) [1], it is not possible to autoupdate libtool.m4 as the hacks around the lack of support for the java language in autoconf seem to whack autoupdate into some endless m4 loop. Well, at least 17 h long loop that I chose to terminate this morning :)
This is a bug. Could you please post a recipe to reproduce it so we may at least find out which tool (M4, Autoconf, Automake, Libtool) is buggy?
Sure. Get libtool 1.5.16-tar.gz. In libtool 1.5.16 source code dir:
mkdir break-autoupdate && cp libtool.m4 break-autoupdate/configure.ac && cd break-autoupdate && autoupdate
The definition of what constitues a bug fix is being bent ways at times, but if you ask me, no such reordering should take place, be it only because then we'd have to increase libtool.m4's serial which then made the universe collapse because our serial numbering would break. :->
That's a pretty good reason, I wouldn't want the universe to collapse :)
Please look at branch-2-0 or even HEAD if you consider involved changes.
I think I'll wait for 2.0 to see if making such involved changes makes sense any more. It sounds like 2.0 will solve my main pedantic -Wall warning gripe, anyway, so ...
cheers, dalibor topic