GNOME Bugzilla – Bug 305544
Please use current libtool
Last modified: 2005-05-27 10:56:10 UTC
I have Gnome installed with prefix /opt/gnome2. When I build gnome-vfs, the build fails because of some inter-library dependencies. The build works if I use a newer libtool. I'd be glad if you could upgrade libtool on the host where you make releases. Version 1.5.6 from 2003 is really too old. I raised the priority to get the message through.
Actually, I found out there are two ways to fix the problem: 1) running "make LIBTOOL=libtool" which replaces the distributed libtool script with the current version I have installed on my machine 2) running "aclocal && autoconf && automake" before ./configure; This replaces Automake 1.6 by version 1.9. But the combination of old tools was deadly for my environment. Besides upgrading libtool on the machine used to make dists, I suggest that you use automake 1.9 for dist tarballs. (Gnumeric does this, I think.) Unfortunately, because current gnome-autogen has a tendency to prefer older automake, you have to temporarily change REQURED_AUTOMAKE_VERSION to 1.9 in your autogen.sh before making the distribution.
Thanks for your bug report. Nautilus simply invokes gnome-autogen.sh, this should be solved for all packages using it. As far as I know, it was planned to require more recent autotools/libtool versions in new gnome-common versions. From what I can see from CVS, it still requires 1.4, though, which is very lax. Reassigning to gnome-common.
What kind of system are you using to get libtool issues? Can you be more precise about the issues you are getting? Released tarballs happen to use whatever autotools are available on the machine of the developer doing the release. At least on debian and ubuntu, the latest libtool package available is 1.5.6, so getting a more up to date package in distros would help I guess ;) Another possibility is also to enforce using a "not too old" libtool in gnome-common, but that may annoy people making releases if the necessary libtool version isn't easy to get.
what the issue with libtool 1.5.6?
Linking programs/gnomevfs-cat failed, stating that it cannot find from libbonobo-2.so and libORBitCosNaming-2.so. At that moment, gnomevfs-cat is linked against not-yet-installed library libgnomevfs-2.so. With newer automake or newer libtool, you get explicit /opt/gnome2/lib/libbonobo-2.so and /opt/gnome2/lib/libORBitCosNaming-2.so on the gcc command line generated by libtool. OK, it really takes more then 9 months for libtool to get to unstable. This is yet another reason why we should upgrade automake, stay tuned...
OK, this should be solved in gnome-autogen.sh . Because my original bug report was confused, I started a new bug, #305641. So I close this one. *** This bug has been marked as a duplicate of 305641 ***