GNOME Bugzilla – Bug 86739
use newer version of libtool [modules don't install correctly]
Last modified: 2004-12-22 21:47:04 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.
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.
It would be really cool if someone could just run libtoolize --force with the latest libtool. This problem is affecting the Debian packages seriously.
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