On Fri, 27 Jan 2006, Thomas Dickey wrote:
On Fri, 27 Jan 2006, Doug Kaufman wrote:
One other thought - aclocal.m4 seems to be misnamed. This can't
be derived from other macros in the code and so should be named
acinclude.m4, with the name aclocal.m4 being used for a wrapper around
it.
no - that's a detail of "recent" autoconf. aclocal.m4 works fine (unless
of course one uses automake).
What I meant was that if anyone tries to reconfigure lynx and runs
"aclocal", it will clobber the "aclocal.m4" file. If you rename it to
"acinclude.m4", then running "aclocal" doesn't do any harm. Now anyone
doing that would have to re-extract "aclocal.m4" from the source code
to recover.
I am not sure that I understand the comment about automake. I have
never seen a "makefile.am" for lynx. Has anyone tried to get automake
to work with lynx? Why would you want to?