Accidentally using 32 bit library on 64 bit system?

[daviddoria]

When trying to run google-chrome, I am getting:

error while loading shared libraries: libnss3.so.1d: wrong ELF class: ELFCLASS32

I am on a 64bit system and downloaded the 64bit google-chrome. I believe the error above means it is trying to use a 32bit library? That file is a symlink I made to /usr/lib/libnss3.so - why would this not be 64bit?

Thanks,

David

[marko]

Originally Posted by daviddoria

When trying to run google-chrome, I am getting:

error while loading shared libraries: libnss3.so.1d: wrong ELF class: ELFCLASS32

I am on a 64bit system and downloaded the 64bit google-chrome. I believe the error above means it is trying to use a 32bit library? That file is a symlink I made to /usr/lib/libnss3.so - why would this not be 64bit?

Thanks,

David

Because /usr/lib/libnss3.so is the 32bit library, the 64bit you want is in /usr/lib64/libnss3.so

Fedora in general puts the 32bit compatibility libraries in /usr/lib and 64bit ones in /usr/lib64

[daviddoria]

Ah, great. This is my first day on a 64 bit system

An unrelated question (maybe I should make a new thread):
Some programs seem to look for libraries with extra extensions. E.g. I had libnss3.so in /usr/lib64, but it was looking for libnss3.so.1d, so I had to make a symlink. Is there a reason for this (i.e. what does the exension 1d or 0d mean?) and is there a way to tell it "just use the one without the extension" so I don't have to make symlinks for so many libraries?

Thanks,

David

[marko]

Lots of packages will make the symlinks for you but some aren't set up for it. So in those cases you'll have to make some symlinks. The number is a version number, it's for when a library changes in a way so that the new API is incompatible with the old one. Since other programs might still need the old version of the library, that stays on disk as libnss3.so.1 and the new one libnss3.so.2 is for the new app.
This covers a lot of this topic if you want to see more on how libraries work:

http://tldp.org/HOWTO/Program-Librar...libraries.html

especially sections 3.1.1 and 3.2