Hi Paul,
* Paul Eggert wrote on Wed, May 17, 2006 at 12:30:26AM CEST:
> Ralf Wildenhues <[EMAIL PROTECTED]> writes:
>
> > * lib/Autom4te/Configure_ac.pm (find_configure_ac): Use
> > `$configure_in' instead of `configure.in', to preserve
> > directory component.
> > * lib/Automake/
Ralf Wildenhues <[EMAIL PROTECTED]> writes:
> * lib/Autom4te/Configure_ac.pm (find_configure_ac): Use
> `$configure_in' instead of `configure.in', to preserve
> directory component.
> * lib/Automake/Configure_ac.pm: Add note that Automake owns
> this file.
> * l
I've updated the generated files (so that `autoreconf -f' with CVS
autotools works more nicely with new features in Autoconf and Libtool).
Cheers,
Ralf
* INSTALL, lib/config.guess, lib/config.sub, lib/texinfo.tex:
New upstream versions.
update.patch.bz2
Description: Binary data
Hi Olly, all,
* Olly Betts wrote on Tue, May 16, 2006 at 07:45:38AM CEST:
> autoreconf is documented to work outside the current directory, and used
> to in autoconf 2.59. The patch below fixes that.
Confirmed. Thanks very much for the bug report!
> To reproduce, pick any autoconf-ed project,
* Ralf Wildenhues wrote on Tue, May 16, 2006 at 12:56:27PM CEST:
>
> While working on this, I again forgot to note which files are imported
> from Automake. So I propose the following two patches against Automake
> and Autoconf, respectively, to make me not forget again, fix Olly's bug,
> my foll
