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 73142 - library versions not incremented, which breaks galeon > 1.1.0
library versions not incremented, which breaks galeon > 1.1.0
Status: RESOLVED FIXED
Product: nautilus
Classification: Core
Component: general
1.1.x
Other All
: Normal minor
: ---
Assigned To: Nautilus Maintainers
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2002-03-01 18:58 UTC by norman
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description norman 2002-03-01 18:58:29 UTC 
The library versions (e.g. libnautilus.so.0.0.0) have not been incremented
from the gnome1 values. This prevents the old and new versions of
nautilus from co-existing on the same machine. It also causes problems
for galeon (which uses the libnautilus library).
Comment 1 Darin Adler 2002-03-01 19:01:01 UTC 
I don't know the right libtool incantations for this.

Can someone provide a patch?
Comment 2 Luis Villa 2002-03-02 06:17:53 UTC 
Does it actually impact galeon? It seems to work fine here, and there
is definitely no parallel install here.
Comment 3 Ricardo Fernández Pascual 2002-03-02 22:47:53 UTC 
It will impact galeon only if it is built with the nautilus view
enabled (this is the defalut for versions > 1.1.0)
Comment 4 maxx 2002-03-02 22:54:38 UTC 
Just a more concrete example of the problem (using galeon 1.1.3 and
nautilus 1.1.6).

Running galeon under gnome 2 (installed using garnome 0.7.5) I get the
following output:
 
         /usr/bin/galeon-bin: relocation error:
         /home/maxx/garnome/lib/libnautilus.so.0: undefined symbol:
         TC_CORBA_string_struct
 
This indicated to me that libnautilus has changed some interfaces or
something, and that galeon was trying to use the new library instead
of the old, since the new libraries come first in LD_LIBRARY_PATH.

To get galeon running all I had to do was set LD_LIBRARY_PATH to
nothing in a term, and run galeon from there.
Comment 5 Luis Villa 2002-03-03 06:01:40 UTC 
I assume a recompile will fix the problem? Or has the API changed as
well?
Comment 6 Alexander Larsson 2002-03-04 05:21:46 UTC 
Ok. I fixes this:
2002-03-04  Alexander Larsson  <alla@lysator.liu.se>

	* libnautilus-adapter/Makefile.am:
	* libnautilus-private/Makefile.am:
	* libnautilus/Makefile.am:
	Bump major soname version to 2. Should fix bug #73142.