Missing libs.

[Xordan]

I am aware that there may be some missing libs in the package that some people here may need. If you get a missing lib error,  then please report in this thread.

You can update your libs dir by running the fixlibs.sh script found in your PS dir. This may resolve your problem.

[Ogu]

I\'m missing the libstdc++.so.6 library too... could you post that here too?

Thanks for your hard work :-)

[Xordan]

hmm, that\'s quite a important core C library. It\'s best if you can get that yourself, although I can provide it if really necessary. What disto and version are you using?

[Ogu]

I\'m using Suse 9.1 professional

[Xordan]

Check to see if you can install libstdc++ 6 from your package manager. Or gcc 3.4.

[Ogu]

Ehm... I have both already installed, but the version in my distro is only 3.3.3

So I guess that\'s the problem... couldn\'t you make the necessary library files available in a ftp folder, that people may add to their planeshift/lib folder if needed?

Or if you make a zip of all the files, I could make them available as well on my site.

I may be talking nonsense, and if so, I apologize. I\'m not exactly an expert on the matter. ;-)

[LigH]

According to a chat with Bereror ... he wonders why those libraries are necessary at all, Xordan. No CrystalSpace source, and neither the PlaneShift source, uses them at all. The only reason he can imagine is: They are on your computer where you compiled the package. And for any strange reason, the package builder included them because they were installed - not because the game depends on them.

[Wired_Crawler]

I hope You are talking about libk5crypto
Applications are not linked directly to this one. Some libraries in \"libs\" subdirectory were build with kerberos support so they require libk5crypto.

EDIT: just checked - updater is linked directly to this library.

[Xordan]

If it requests the lib then it, or one of it\'s dependancies is linked to it.

Ogu: I\'ll upload it here for you then. You should really be able to get it from your distro though.

[Ogu]

Ok, I\'ve put the libraries in my lib folder, and PS now works fine! :-D

Thank you so much, Xordan :-)

[Xordan]

No problem.

[Rolf Blacksmith]

the new updater Xordan posted in the other Thread is looking for an ssl library I don\'t have, openssl is installed.

Code: [Select]


/opt/planeshift/updater: error while loading shared libraries: libssl.so.4: cannot open shared object file: No such file or directory


[Araye]

OK, on my SuSE 9.1 install I have had the

libk5crypto
libstdc++

problems, with the added note, that I had to force the crypto rpm because it conflicts with the heimdal stuff (no longer used in SuSE 9.3)...

On my 9.3 install I just had the libstdc++ issue.

In these instances I installed the rpms then sym linked the libstdc++ to the /usr/lib/gcc/ library that I needed.  I don\'t know why the rpm I used put it there, but it did...  (Note:  I downloaded my own rpm\'s as Xordan didn\'t have them available yet and I may have dl\'d different ones.)

For the updater, I also got the libssl error.  I just sym linked to solve that one..  I think I used

ln -s /usr/lib/libssl.so.0.9.7 /usr/lib/libssl.so.4


then I got a crypto error...  I fixed it with...

ln -s /usr/lib/libcrypto.so.0.9.7 /usr/lib/libcrypto.so.4

That seems to have fixed everything and can now run the programs.

Remember, this is all for a standard SuSE 9.1 and 9.3 install.

Araye


EDIT:  Yes Xordan, I only run the scripts ./pssetup for example
EDIT #2:  After reading some more in this thread I realize now that I screwed up and replaced ./updater (script) with up (binary)...  ooppsie  So the above libssl and libcrypto stuff was probably not necessary after all.  I will verify on my next install.
EDIT #3:  Nope, I had to make the symlinks...

[Xordan]

I provided libssl and libcrypto with the binaries afaik. I assume you were running the scripts (psclient/pssetup/updater) and not the binaries directly?

[Rolf Blacksmith]

I ran the binaries ...

Actually, I replaced the updater script with the downloaded up binary because I assumed the updater itself was the program itself and therefore never checked.