On 11. 07. 21 21:05, Richard Shaw wrote:
Trying this with python-pyside2...
+ /usr/bin/python3 -c 'import PySide2'
PySide2/__init__.py: Unable to import shiboken2 from ,
Traceback (most recent call last):
File "<string>", line 1, in <module>
line 107, in <module>
line 58, in _setupQtDirectories
line 27, in <module>
from .shiboken2 import *
ImportError: libshiboken2.cpython-310-x86_64-linux-gnu.so.5.15: cannot open
shared object file: No such file or directory
Worked fine once installed. The 5.15 file is a symlink to 5.15.2 which is the
actual library file name, but I don't see why it would follow symlinks once
installed but not here?
Is it possible that the symbolic link is absolute and hence not resolvable
during the build (because it does not lead to the buildroot)?
Not sure how the macro could compensate for that.