same soname but different type

acidjuice · 05-11-2005, 06:45 AM

dear all,

i did some massive compiling of libraries and get the following error when updating the shared libraries (at boot):

same soname but different type

the concerned libraries are:

libpango
libglib2
libgthread
libgobject
libgmodule

...anyone knows what is this and what should i do?...

thanks,

aj.

keefaz · 05-11-2005, 06:58 AM

Maybe you have more than one library installed, I mean different version
of the same library

Assuming your locate db is up to date, what is the output with
locate libpango-
(for example)

acidjuice · 05-11-2005, 07:02 AM

can you please tell me how to ensure my locate db is up to date so i can give you the outcomes?

thank you...

keefaz · 05-11-2005, 07:06 AM

As root, run : updatedb (and go take a coffee or chocolate...)

acidjuice · 05-11-2005, 07:51 AM

here is the complete error when i run ldconfig:

Code:

:~# ldconfig
ldconfig: libraries libpangoxft-1.0.so.0 and libpangoxft-1.0.so.0.399.1 in directory /usr/lib have same soname but different type.
ldconfig: libraries libpangoft2-1.0.so.0 and libpangoft2-1.0.so.0.399.1 in directory /usr/lib have same soname but different type.
ldconfig: libraries libglib-2.0.so.0 and libglib-2.0.so.0.400.2 in directory /usr/lib have same soname but different type.
ldconfig: libraries libgthread-2.0.so.0.400.2 and libgthread-2.0.so.0.600.4 in directory /usr/lib have same soname but different type.
ldconfig: libraries libpango-1.0.so.0 and libpango-1.0.so.0.399.1 in directory /usr/lib have same soname but different type.
ldconfig: libraries libgobject-2.0.so.0 and libgobject-2.0.so.0.400.2 in directory /usr/lib have same soname but different type.
ldconfig: libraries libgmodule-2.0.so.0 and libgmodule-2.0.so.0.400.2 in directory /usr/lib have same soname but different type.
ldconfig: libraries libpangox-1.0.so.0 and libpangox-1.0.so.0.399.1 in directory /usr/lib have same soname but different type.

the locate libpango- gives:

Code:

~# locate libpango-
/usr/lib/libpango-1.0.so.0
/usr/lib/libpango-1.0.so.0.399.1
/usr/lib/libpango-1.0.so.0.800.1
/usr/lib/libpango-1.0.la
/usr/lib/libpango-1.0.so

...any ideas? i am actually compiling some gnome sources on an amd64 arch.

keefaz · 05-11-2005, 07:56 AM

On my system, locate libpango- gives :

Code:

/usr/lib/libpango-1.0.so.0
/usr/lib/libpango-1.0.so.0.800.1
/usr/lib/libpango-1.0.la
/usr/lib/libpango-1.0.so

And /usr/lib/libpango-1.0.so is a symlink to /usr/lib/libpango-1.0.so.0.800.1
Check all your .so symlinks to see if there is some weird mix, and if you compile
your librairies, maybe you should deinstall the old ones before

acidjuice · 05-11-2005, 12:07 PM

hi,

i actually compiled and used upgradepkg --install-new MYPACKAGE.tgz, therefore the others should have normally been removed (upgradepkg is removepkg + installpkg combined together)...

anyone?

gbonvehi · 05-11-2005, 01:04 PM

Maybe they had a different package name.. take a look at /var/log/packages

acidjuice · 05-11-2005, 01:44 PM

not sure i understand... the error statest that they do have a same name... no? what whould i look for there?

gbonvehi · 05-11-2005, 05:35 PM

Maybe the package name was malformed and upgradepkg thought they were different so you could've ended with two pango packages.
Try:

Code:

ls -l /var/log/packages/*pango*

jong357 · 05-11-2005, 06:36 PM

Yea, I bet that is what's going on. I have a sneaking suspicion that your not naming packages properly when you use makepkg. Therefore pkgtool gets confused and thinks it's an entirely different package.. Maybe?

package-$VERSION-$ARCH-$BUILD.tgz

And "package" has to be the same as whats already on your system before upgradepkg will work. Just a stab in the dark anyway...

acidjuice · 05-12-2005, 03:41 AM

Quote:

Originally posted by jong357
Yea, I bet that is what's going on. I have a sneaking suspicion that your not naming packages properly when you use makepkg. Therefore pkgtool gets confused and thinks it's an entirely different package.. Maybe?

package-$VERSION-$ARCH-$BUILD.tgz

And "package" has to be the same as whats already on your system before upgradepkg will work. Just a stab in the dark anyway...

i do use this standard renaming, i just add at the end the releaser:

package-$VERSION-$ARCH-$BUILDacid.tgz

but this surely does not do any difference. i've seen that i have a prior error when running my gnome script, who knows this might be related to this prior error. i am posting a new post for this and see if i can find a solution to that instead.

thank you.