How to cope with Python module putting .so files into lib64 instead of lib?

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
1 message Options
Reply | Threaded
Open this post in threaded view
|

How to cope with Python module putting .so files into lib64 instead of lib?

Arrigo Marchiori
Dear List,

I am going forward in building OpenOffice on openSUSE Leap 15.2.

I am encountering problems with the pyuno modules and I think they may
be due to an incomplete installation of the "python" module.

Just to clarify: I am not talking about my system Python, but rather
the "python" module from AOO sources directory main/python.

openSUSE has a long tradition of putting 64-bit libraries in
/usr/lib64 and, on my system, the Python version compiled as "python"
module is doing the same:

$ find path/main/python/unxlngx6.pro -name libpython*.so*
path/main/python/unxlngx6.pro/misc/build/Python-2.7.18/libpython2.7.so
path/main/python/unxlngx6.pro/misc/build/Python-2.7.18/libpython2.7.so.1.0
path/main/python/unxlngx6.pro/misc/build/python-inst/lib64/libpython2.7.so
path/main/python/unxlngx6.pro/misc/build/python-inst/lib64/libpython2.7.so.1.0

However, file path/main/python/prj/d.lst seem to explicitly look for
files in "lib" rather than "lib64":

[line 86]
..\%__SRC%\misc\build\python-inst\lib\libpython2.7.so.1.0 %_DEST%\lib%_EXT%\libpython2.7.so.1.0
                                 ^^^^^

Can anyone please confirm that it is possible to carry out a 64-bit
build on a 64-bit Linux system that keeps its 64-bit libraries in
/lib64 ?

Or has anyone ever addressed this kind of problem in the OpenOffice
build system?

Thank you in advance!
--
rigo

http://rigo.altervista.org

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]