pyrcc5 builds against system library path, not virtualenv's

Ludovic Bellière <[email protected]>
Newsgroups gmane.comp.python.pyqt-pykde
Message-ID <[email protected]>
Hello nal,

Using PyQt5 5.14.0 in a pyenv/pipenv environment, and thus supposed to
be system agnostic, pyrcc5 and its library (pyrcc.abi3.so) seems to be
built against the system's library, where as the other included
libraries properly point towards the venv library location.

Let me include the ldd output to be less confusing. I'm sorry about the
wrap of the long lines, I'm unfamiliar with thunderbird and formatting
in plaintext.

$ pwd
/home/xrogaan/.local/share/virtualenvs/MyQtProject-BgHdZiUT/lib/python3.7/site-packages/PyQt5

$ ldd pyrcc.abi3.so
./pyrcc.abi3.so: /usr/lib/x86_64-linux-gnu/libQt5Core.so.5: version
`Qt_5.14' not found (required by ./pyrcc.abi3.so)
	linux-vdso.so.1 (0x00007fff89387000)
	libQt5Xml.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Xml.so.5
(0x00007f72c4b9f000)
	libQt5Core.so.5 => /usr/lib/x86_64-linux-gnu/libQt5Core.so.5
(0x00007f72c4311000)
	libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
(0x00007f72c40f4000)
	libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6
(0x00007f72c3d72000)
	libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f72c3a6e000)
	libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f72c3857000)
	libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f72c34b8000)
	libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f72c329e000)
	libicui18n.so.57 => /usr/lib/x86_64-linux-gnu/libicui18n.so.57
(0x00007f72c2e23000)
	libicuuc.so.57 => /usr/lib/x86_64-linux-gnu/libicuuc.so.57
(0x00007f72c2a7b000)
	libpcre16.so.3 => /usr/lib/x86_64-linux-gnu/libpcre16.so.3
(0x00007f72c2812000)
	libdouble-conversion.so.1 =>
/usr/lib/x86_64-linux-gnu/libdouble-conversion.so.1 (0x00007f72c2601000)
	libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f72c23fd000)
	libglib-2.0.so.0 => /lib/x86_64-linux-gnu/libglib-2.0.so.0
(0x00007f72c20e9000)
	librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f72c1ee1000)
	/lib64/ld-linux-x86-64.so.2 (0x00007f72c49ee000)
	libicudata.so.57 => /usr/lib/x86_64-linux-gnu/libicudata.so.57
(0x00007f72c0464000)
	libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x00007f72c01f1000)

$ ldd QtXml.abi3.so
	linux-vdso.so.1 (0x00007ffdcc9cf000)
	libQt5Xml.so.5 =>
/home/xrogaan/.local/share/virtualenvs/MyQtProject-BgHdZiUT/lib/python3.7/site-packages/PyQt5/./Qt/lib/libQt5Xml.so.5
(0x00007f33274ee000)
	libQt5Core.so.5 =>
/home/xrogaan/.local/share/virtualenvs/MyQtProject-BgHdZiUT/lib/python3.7/site-packages/PyQt5/./Qt/lib/libQt5Core.so.5
(0x00007f3326d17000)
	libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
(0x00007f3326afa000)
	libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6
(0x00007f3326778000)
	libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f3326474000)
	libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f332625d000)
	libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f3325ebe000)
	libz.so.1 => /lib/x86_64-linux-gnu/libz.so.1 (0x00007f3325ca4000)
	libicui18n.so.56 =>
/home/xrogaan/.local/share/virtualenvs/MyQtProject-BgHdZiUT/lib/python3.7/site-packages/PyQt5/./Qt/lib/libicui18n.so.56
(0x00007f332580b000)
	libicuuc.so.56 =>
/home/xrogaan/.local/share/virtualenvs/MyQtProject-BgHdZiUT/lib/python3.7/site-packages/PyQt5/./Qt/lib/libicuuc.so.56
(0x00007f3325453000)
	libicudata.so.56 =>
/home/xrogaan/.local/share/virtualenvs/MyQtProject-BgHdZiUT/lib/python3.7/site-packages/PyQt5/./Qt/lib/libicudata.so.56
(0x00007f3323a70000)
	libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f332386c000)
	libgthread-2.0.so.0 => /usr/lib/x86_64-linux-gnu/libgthread-2.0.so.0
(0x00007f332366a000)
	libglib-2.0.so.0 => /lib/x86_64-linux-gnu/libglib-2.0.so.0
(0x00007f3323356000)
	/lib64/ld-linux-x86-64.so.2 (0x00007f3327974000)
	libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x00007f33230e3000)


This message might be related to the message about [pylupdate][1], as
pylupdate.abi3.so show the same binding issues.


[1]:
https://www.riverbankcomputing.com/pipermail/pyqt/2019-December/042398.html
_______________________________________________
PyQt mailing list    [email protected]
https://www.riverbankcomputing.com/mailman/listinfo/pyqt
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.