After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 86739 - use newer version of libtool [modules don't install correctly]
use newer version of libtool [modules don't install correctly]
Status: RESOLVED FIXED
Product: gnome-vfs
Classification: Deprecated
Component: Build
2.0.x
Other other
: Normal major
: ---
Assigned To: gnome-vfs maintainers
gnome-vfs maintainers
Depends on:
Blocks:
 
 
Reported: 2002-06-28 15:41 UTC by Geoff Reedy
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: 2.0



Description Geoff Reedy 2002-06-28 15:41:42 UTC
In the process of make install libtool relinks the modules and it fails
claiming that libgnomevfs-2.so cannot be found.  I suspect that this may be
because of using DESTDIR to install in a different root when building an
RPM.  I suspect that the install process expects that libgnomvfs-2.so will
be installed in /usr/lib (or somewhere else that will be searched) and will
be able to be linked normally.  I don't know that much about automake and
libtool, so I don't know what can be done to fix it, but some of the other
packages correctly build modules in this fashion (pango, gdk-pixbuf)
perhaps they can be adapted.  I'm reporting this from work so can't give
details about versions of libtool or any other build tools, but they should
be all the standard redhat-7.3 packages.
Comment 1 Geoff Reedy 2002-06-29 01:19:50 UTC
It turns out to be a libtool problem.  Relinking with a buildroot 
(DESTDIR) doesn't work.  Other gnome packages include a fixed libtool 
that apparently have a patch from aoliva. Upgrading the libtool used 
with gnome-vfs should fix the problem.
Comment 2 Colin Walters 2002-10-08 01:21:42 UTC
It would be really cool if someone could just run libtoolize --force
with the latest libtool.  This problem is affecting the Debian
packages  seriously.
Comment 3 Christophe Fergeau 2003-04-15 20:04:31 UTC
This bug is quite old, and I guess everyone has upgraded to "sane"
libtool versions now, please reopen if there are still issues with that