Hi, (on-list)
On Mon, Mar 26, 2012 at 12:15:06PM +0200, Alon Bar-Lev wrote:
> >> configure.ac:328: error: possibly undefined macro: AC_LIBTOOL_WIN32_DLL
> >> If this token and others are legitimate, please use m4_pattern_allow.
> >> See the Autoconf documentation.
> >> configure.ac:329: error: possibly undefined macro: AC_LIBTOOL_RC
> >> configure.ac:330: error: possibly undefined macro: AC_PROG_LIBTOOL
> >> autoreconf-2.68: /usr/local/bin/autoconf-2.68 failed with exit status: 1
> >
> > OK, David had an idea: this machine did not have libtool installed
> > ("because we didn't need it before").
>
> Right.
> Usually you do autoreconf -ivf && ./configure && make dist at
> development machine or central build server and send the tarball to
> build machines, this way you don't need to install the autotools
> components on all build machines.
Yep. Can we improve the error message here, so people running buildbot
or doing development can see that they are missing libtool?
> > I have now installed libtool 2.2.10, and with that, "autoreconf -vi"
> > does not return an error anymore.
> >
> >
> > "configure" still fails looking for "libdl", though.
>
> Yes, this results of strange development procedure, merge first then test...
> :)
Well, we did test, but not on all platforms yet - that's what we have
the buildbot armada for, and they need the merge first :-)
> Can you please send me the config.log?
> I will fix that.
I'll send the config.log off-list.
gert
--
USENET is *not* the non-clickable part of WWW!
//www.muc.de/~gert/
Gert Doering - Munich, Germany g...@greenie.muc.de
fax: +49-89-35655025 g...@net.informatik.tu-muenchen.de
pgpBZ08taHsmb.pgp
Description: PGP signature
