> Okay, I'll update autoconf soon :)

Well actually this HAS been fixed (I'm using autoconf 2.54)

Did you re-run autoconf with an old (<2.49) release ?