KxSystems / pyq

PyQ — Python for kdb+
http://code.kx.com/q/interfaces
Apache License 2.0
191 stars 49 forks source link

pyq-config.q reference libpython3.7m.a not libpython3.7m.so #112

Closed eepgwde closed 4 years ago

eepgwde commented 5 years ago

Questions

Steps to reproduce the issue

pyq

Expected result

Python 3.7.1 (default, Dec 14 2018, 19:51:47) [GCC 7.3.0] :: Anaconda custom (32-bit) on linux Type "help", "copyright", "credits" or "license" for more information.

Actual result

339$ pyq '2019.06.11T08:57:46.293 /misc/share/5/anaconda32/lib/libpython3.7m.a: invalid ELF header [4] /home/share/src/q-site/p.k:2: (:./pyq 2:(p_init;1)).pyq.python_dl

Workaround

If you know workaround, please provide it here.

Manual edit of ~/src/q/pyq-config.q so that the libpython3.7m.a is changed to .so

\d .pyq // python_dll:"/misc/share/5/anaconda32/lib/libpython3.7m.a\000" python_dll:"/misc/share/5/anaconda32/lib/libpython3.7m.so\000" pyq_executable:"/misc/share/5/anaconda32/bin/pyq"

sashkab commented 5 years ago

Which operating system are you using? I unable to decipher uname -a. Either provide better name, or output of the cat /etc/*release. In addition to this, please Please provide output of:

ldconfig -p | grep -i python

Thanks.

eepgwde commented 5 years ago

This is from a Debian Stretch system.

The ldconfig might be confusing. This is a 32-bit conda installation running on a 64 bit host where there are two Pythons. Don't tell me this is a 32 bit product and won't run on a 64 bit!

        libqgispython.so.3.4.4 (libc6,x86-64) => /usr/lib/libqgispython.so.3.4.4
        libqgispython.so.2.18.16 (libc6,x86-64) => /usr/lib/libqgispython.so.2.18.16
        libpython3.5m.so.1.0 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libpython3.5m.so.1.0
        libpython3.5m.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libpython3.5m.so
        libpython2.7.so.1.0 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libpython2.7.so.1.0
        libpython2.7.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libpython2.7.so
        libpyglib-2.0-python2.7.so.0 (libc6,x86-64) => /usr/lib/libpyglib-2.0-python2.7.so.0
        libboost_python-py35.so.1.62.0 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_python-py35.so.1.62.0
        libboost_python-py35.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_python-py35.so
        libboost_python-py27.so.1.62.0 (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_python-py27.so.1.62.0
        libboost_python-py27.so (libc6,x86-64) => /usr/lib/x86_64-linux-gnu/libboost_python-py27.so

 ldd lib/libpython*
lib/libpython3.7m.a:
        not a dynamic executable
lib/libpython3.7m.so:
        linux-gate.so.1 (0xf7701000)
        libpthread.so.0 => /lib32/libpthread.so.0 (0xf7353000)
        libc.so.6 => /lib32/libc.so.6 (0xf719b000)
        libdl.so.2 => /lib32/libdl.so.2 (0xf7193000)
        libutil.so.1 => /lib32/libutil.so.1 (0xf718b000)
        librt.so.1 => /lib32/librt.so.1 (0xf717b000)
        libm.so.6 => /lib32/libm.so.6 (0xf7123000)
        /lib/ld-linux.so.2 (0xf7703000)
lib/libpython3.7m.so.1:
        linux-gate.so.1 (0xf77f4000)
        libpthread.so.0 => /lib32/libpthread.so.0 (0xf741b000)
        libc.so.6 => /lib32/libc.so.6 (0xf7263000)
        libdl.so.2 => /lib32/libdl.so.2 (0xf725b000)
        libutil.so.1 => /lib32/libutil.so.1 (0xf7253000)
        librt.so.1 => /lib32/librt.so.1 (0xf7243000)
        libm.so.6 => /lib32/libm.so.6 (0xf71eb000)
        /lib/ld-linux.so.2 (0xf77cb000)
lib/libpython3.7m.so.1.0:
        linux-gate.so.1 (0xf77c4000)
        libpthread.so.0 => /lib32/libpthread.so.0 (0xf73eb000)
        libc.so.6 => /lib32/libc.so.6 (0xf7233000)
        libdl.so.2 => /lib32/libdl.so.2 (0xf722b000)
        libutil.so.1 => /lib32/libutil.so.1 (0xf7223000)
        librt.so.1 => /lib32/librt.so.1 (0xf7213000)
        libm.so.6 => /lib32/libm.so.6 (0xf71bb000)
        /lib/ld-linux.so.2 (0xf779b000)

Thanks. There's no need to keep this open.

sashkab commented 5 years ago

Thanks for the information. We will look into this.

github-actions[bot] commented 4 years ago

Stale issue message