Hello

Recently I got task to setup 3rd party software to run on different Linux distros, including Slackware.

The problem is: it uses python, and when I start it I got message of unresolved symbol PyUnicodeUCS4_DecodeUTF8

Well, solution is to rebuild python with extra flag --enable-unicode=ucs4 . So I did it - modified original slackbuild, rebuilt and installed new package(replaced original python). Now I have not such error, but:

Should I except problems? Sure.

Question: is there any tool which allows me examine binaries (so's and executables) for unresolved symbols? ldd doesn't works here, because it is stupid enough to check library names only, but to not ensure all required symbols imported(it failed to show me absence of unresolved symbol when I ldd-ed each and every binary file of package). I need them because new python lacks of PyUnicodeUCS2_DecodeUTF8, and it can be problem for other software.

Or alternative: how I can isolate software and reconfigured python so do not influence system and vice versa?

PS: 3rd party software does not provides sources. All I have received from stupid developers is a few Ubuntu-specific(sick) .deb packages(actually I received deb repo link), which I unar-untar-ungzip-ed merged and makepkg-ed into .txz, so all I can do is change environment, not package itself.

you can install python (your own build) anywhere you want (and leave the original intact).

No, I can't. All I can to do is 'installpkg --root /path/to/somewhere/else python*.t?z', i.e. install it into offline system. It gives me nothing.

https://www.linuxquestions.org/quest...rt-4175473344/

according to the googling I have done at the time of this other thread, I suppose you're using IBM's cplex...

@ponce, no, (un)fortunately no. It is another kind of TS-player from here, but they redistribute only packages for Ubuntu

Install the rebuilt python package in some other location. Use wrapper scripts to launch the programs that need to use that rebuilt version. Those scripts set the PATH environmental variable to have /path/to/somewhere/else/usr/bin at the front of the list prior to running whatever it is that needs python.

If your normal environment has the environmental variable PYTHONPATH set, then you'll need to change that in a similar fashion.

This discussion of python virtual environments can give you an idea of what has to be changed to get things to work (since that's what virtualenv has to do when you set it up). There's a slackware package of virtualenv available at slackbuilds.org.