[SOLVED] Ogre3D bad build

Arsakes · 2017-04-03 10:55:58

It seems latest ogre 1.9.0.16 is build against old boost library:

OgreXMLConverter: error while loading shared libraries: libboost_thread.so.1.62.0: cannot open shared object file: No such file or directory
    bash:OgreXMLConverter:: nie znaleziono polecenia

$>ldd OgreXMLCOnverter

gives:

        *
	libboost_thread.so.1.62.0 => not found
	libboost_date_time.so.1.62.0 => not found
	libboost_system.so.1.62.0 => not found
	libboost_atomic.so.1.62.0 => not found
	libboost_chrono.so.1.62.0 => not found

Current boost version is 1.63

Same stuff with any other ogre executable.
Solutions?

Last edited by Arsakes (2017-04-03 11:44:56)

Trilby · 2017-04-03 11:08:19

It would seem you are doing partial upgrades, or you have a broken mirror. Properly upgrade your system.

EDIT: I see you included version numbers, and that is the correct version. So it looks instead like you've done something locally with ogre. Are you using ogre from the repos, or your owb build? Do you have any LD_PRELOAD hacks somewhere? Your ldd output does not match that of the binary from the repos. Are you using i686 by chance (I've only checked x86_64)?

Arsakes · 2017-04-03 11:36:10

No hacks, I'm using x86_64, I'm using Ogre from our repos.

I've a local build of ogre for Worldforge project but it is supposed to be contained to one directory in home directory and libs are indead in this single directory.
What else could be messed...
Hmm
`ldconfig -v 2>/dev/null | grep -v ^$'\t'`

/opt/cuda/lib64:
/opt/cuda/nvvm/lib64:
/usr/lib/libfakeroot:
/usr/lib32:
/usr/lib/opencollada:
/home/pietrko/projekty/worldforge/hammer/work/local/lib:  # Other ogre version
/usr/lib:
/usr/lib32/tls: (hwcap: 0x8000000000000000)
/usr/lib/tls: (hwcap: 0x8000000000000000)

How can I list search path for pkg-config?

Ok I've removed: /home/pietrko/projekty/worldforge/hammer/work/local/lib:
from search of linker and now things are ok....

Not a perfect solution though, why linker was mislead? And picked the old lib instead of new one?

Last edited by Arsakes (2017-04-03 11:44:34)

Trilby · 2017-04-03 11:54:21

Arsakes wrote:

Ok I've removed: /home/pietrko/projekty/worldforge/hammer/work/local/lib:
from search of linker and now things are ok....

How did you add it to the linker search path? If you added it globally to /etc/ld.so.conf{.d/*} then that was the wrong way to do it and would explain the problem.

I'm not sure what the best approach would be, but it would certainly be to not muck up your root installation for that one locally installed program. Instead, change how you call that one program. One approach would be to use LD_PRELOAD with that locally installed stuff (in a script, function, or alias).

EDIT: Setting LD_LIBRARY_PATH when running that locally installed version would probably be cleaner and much easier than LD_PRELOAD, but note I have no direct experience with this - I think the following should work:

LD_LIBRARY_PATH=/home/pietrko/projekty/worldforge/hammer/work/local/lib /home/pietrko/path_to_ogre_bin/program

And that could readily be made into an alias. The above will set that library path only for that invocation, so it will not interfere with every other program you try to run.

Last edited by Trilby (2017-04-03 11:58:27)

Arch Linux

#1 2017-04-03 10:55:58

[SOLVED] Ogre3D bad build

#2 2017-04-03 11:08:19

Re: [SOLVED] Ogre3D bad build

#3 2017-04-03 11:36:10

Re: [SOLVED] Ogre3D bad build

#4 2017-04-03 11:54:21

Re: [SOLVED] Ogre3D bad build

Board footer