> The configure scripts generated by the newest versions of Autoconf > leave a configure.lineno file sitting around after running the > configure script. Is this intentional?
First of all, I knew about this behavioral change (and it was also pointed out by Akim on the patches mailing list, but considered something we could bear), and it should have been myself fixing this, but I've been distracted by many other things lately. Sorry.
However, it is not as easy as it looks. :-(
bash reports a $LINENO relative to the start of the function inside shell functions. So I see only three ways out:
1) revert to the old __oline__ mechanism that was used in autoconf 2.13 (not very aesthetic)
2) always use configure.lineno (slow)
3) implement __oline__ in m4 2.0, and rever to configure.lineno when configure scripts are created with an older m4 (who knows the timeline for m4 2.0 and libtool 1.6, on which m4 depends?).
What's the best one?
Paolo
