Closed ppatel26 closed 5 years ago
- Changes in steup.py #80
Why was this required — are you using Python 3.7?
This is being tracked in internal-1028
.
- Changes in steup.py #80
Why was this required — are you using Python 3.7?
@sashkab Yes using 3.7
I finally go it working after removing all the CFLAGS as recommended by @sitsang
Now every time I sun >pyq
I get the following error
Welcome to kdb+ 32bit edition
For support please see http://groups.google.com/d/forum/personal-kdbplus
Tutorials can be found at http://code.kx.com
To exit, type \\
To remove this startup msg, edit q.q
'2019.01.29T21:08:09.241 dlopen(/Users/parvpatel/q/m32/p.so, 2): no suitable image found. Did find:
/Users/parvpatel/q/m32/p.so: mach-o, but wrong architecture
/Users/parvpatel/q/m32/p.so: mach-o, but wrong architecture
[4] /Users/parvpatel/q/p.k:3: (`p 2:(`p_init;1))python_dll
/Users/parvpatel/q/m32/p.so: mach-o, but wrong architecture
Most likely you're using 64-bit python with 32-bit kdb+.
You need 32-bit python in order to use 32-bit kdb+.
Questions
[ ] Which operating system are you using (if Linux, please provide flavour of it, i.e RedHat, CentOS or Ubuntu), is it 32-bit, or 64-bit?
[ ] Which version of PyQ are you running? Please provide output of
pyq --versions
, if PyQ isn't operational, please provide Python interpreter version and PyQ versionpython -V; python3 -V; pip list | grep pyq
:[ ] Which version of kdb+ are you using, is it 32-bit or 64-bit?
[ ] If on 64-bit, is your
QLIC
set? Please provide outputenv | grep QLIC
on linux/macOS, orset|grep QLIC
on Windows.[ ] Did you use virtual environment to install PyQ? If not, why?
[ ] Where is your
QHOME
? Please provide outputenv | grep QHOME
on linux/macOS, orset|grep QHOME
on Windows.[ ] Do you use Conda? If so, what version?
Steps to reproduce the issue
Expected result
Should Install pyq
Actual result
Workaround
If you know workaround, please provide it here.