[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: libtool-2.2.6a breaks build of guile-1.8.5, libtool-1.5.26 is OK

From: Ralf Wildenhues
Subject: Re: libtool-2.2.6a breaks build of guile-1.8.5, libtool-1.5.26 is OK
Date: Tue, 11 Nov 2008 06:37:31 +0100
User-agent: Mutt/1.5.18 (2008-05-17)

* Sergei Steshenko wrote on Mon, Nov 10, 2008 at 11:26:45PM CET:
> > 
> > I should note that I had to employ some force in order to
> > get guile to use updated autotools.  I used something like this:
> > 
> >   autoreconf -vif       # to let libtoolize do its job in subdirs
> >                         # but this fails in toplevel due to some error
> >   rm -f ltmain.sh
> >   cp $libtool_install_tree/share/libtool/config/ltmain.sh
> > build-aux/ltmain.sh
> >   LIBTOOLIZE=true autoreconf -vif --no-recursive #
> > regenerate the toplevel

> Do I reed you correctly, i.e. can your statement be expressed this way:
> guile can _not_ be built by libtool-2.2.6a out of the box using the
> standard
> ./configure
> make
> procedure ?

Wrong.  guile *can* be built with libtool-2.2.7a out of the box,
*once* somebody has updated guile to correctly use the new libtool.

> Regarding your assumption about mixed libtool version - again, _very_
> unlikely.

Look, I gave you several proofs already.  Why don't you start checking
the facts rather than replying with more doubts on your side?
You should also be able to see that
  cd .../libguile
  ../libtool --version

shows the wrong version.

> This is because whenever a target is built, it is built _from scratch_,
> i.e. the old build directory - in this case
> build/guile-1.8.5
> is _completely_ removed using "\rm -rf build/guile-1.8.5", then the tarball
> is again unpacked using "cd build; tar zxvf guile-1.8.5.tar.gz", and only
> then the standard
> ./configure
> make
> ...
> procedure is applied.

This has nothing to do with the bootstrap procedure, which happens
*before* configure is run.

> So, for your hypothesis to hold my tool needs to be stubborn enough to
> do something libtool-1.5.26-specific when it is told to use libtool-2.2.6a,
> and as you could see in the command line I've provided, there is no 
> reference to libtool-1.5.26.

I haven't said anything about your tool, no?

> - so what does _my_ tool have to do with the fact that guile-1.8.5 comes
> with libtool "VERSION=1.5.26" and relies on it ?
> Don't you think it's a bug in guile-1.8.5 ?

The fact that guile doesn't cleanly bootstrap with
  autoreconf -vif

is something you can discuss with the guile people.  They may accept is
as a bug, or not, it's up to how they usually bootstrap their sources.
(There are no portability requirements for bootstrapping.)

Whether there is a bug in your tool or not is completely outside of my
scope.  I've showed the bug not to be in Libtool.


reply via email to

[Prev in Thread] Current Thread [Next in Thread]