* Paul Eggert wrote on Thu, Jun 21, 2007 at 09:15:56PM CEST:
> Ralf Wildenhues <[EMAIL PROTECTED]> writes:
>
> > I think this should be applied to HEAD and branch-1-10.
> > Would you like me to do it?
>
> Yes, please. And thanks for your review; your points all look right
> to me.
Thanks. This
On Thu, Jun 21, 2007 at 01:14:11AM +0200, Bruno Haible wrote:
> aclocal.m4:14: error: this file was generated for autoconf 2.61.
> You have another version of autoconf.
>
> is causing a major regression in the functioning of automake and the GNU
> build system. Namely, a change in Makefile
Ralf Wildenhues <[EMAIL PROTECTED]> writes:
> I think this should be applied to HEAD and branch-1-10.
> Would you like me to do it?
Yes, please. And thanks for your review; your points all look right
to me.
> So this is yet another reason to keep Autoconf version incompatibilities
> as few as p
Hello world,
* Eric Blake wrote on Thu, Jun 21, 2007 at 02:16:32PM CEST:
> According to Paul Eggert on 6/20/2007 11:36 PM:
> >
> > +[m4_warning([this file was generated for autoconf $ac_version.
> > +You have another version of autoconf. It may work, but it may not.
> > +If you have problems, yo
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
According to Paul Eggert on 6/20/2007 11:36 PM:
> Bruno Haible <[EMAIL PROTECTED]> writes:
>
>> Are we now supposed to edit Makefile.in by hand each time we modify
>> Makefile.am?
>
> I hope not. How about the following (untested) Automake patch?
L
Bruno Haible <[EMAIL PROTECTED]> writes:
> Are we now supposed to edit Makefile.in by hand each time we modify
> Makefile.am?
I hope not. How about the following (untested) Automake patch?
2007-06-20 Paul Eggert <[EMAIL PROTECTED]>
* aclocal.in (write_aclocal): Warn about autoconf
On Wednesday 20 June 2007, Bruno Haible wrote:
> Bob Proulx wrote:
> > I would follow that clue and regenerate everything.
> >
> > autoreconf
> > ./configure
>
> Doesn't work:
>
> $ pwd
> /build/libidn-0.6.14
> $ autoreconf
> configure.ac:41: error: possibly undefined macro: AC_LIBTOOL_
Bob Proulx wrote:
> I would follow that clue and regenerate everything.
>
> autoreconf
> ./configure
Doesn't work:
$ pwd
/build/libidn-0.6.14
$ autoreconf
configure.ac:41: error: possibly undefined macro: AC_LIBTOOL_WIN32_DLL
If this token and others are legitimate, please us
Hi Bruno,
Bruno Haible wrote:
> Or is there an "obvious" workaround that I'm not seeing?
I don't know how obvious this is because I am in many ways not very
knowledgeable about the internal workings of the autotools but in the
output was a clue.
> aclocal.m4:14: error: this file was generated fo
Hi,
This error message
aclocal.m4:14: error: this file was generated for autoconf 2.61.
You have another version of autoconf.
is causing a major regression in the functioning of automake and the GNU
build system. Namely, a change in Makefile.am does not cause a corresponding
change to Ma
10 matches
Mail list logo
