-
Notifications
You must be signed in to change notification settings - Fork 53
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Could not load liboqs shared library in fedora 36 #51
Comments
i am having openssl 3.0.3 and python3 setup.py gives warnings :- zipsafe flag not set analyzing contents. usr/1ib/python3.10/site-packages/setuptools/command/easy_install.py:156: EasyInstallDeprecationWarning: easy install command is deprecated. Use build |
To better understand your issue, could you please provide output of these commands on your installation:
|
@baentsch output of above commands: - ls $PYTHONPATH displays contents of liboqs-python folder and additionally build , dist , liboqs-python.egg-info folders ls $LD_LIBRARY_PATH displays ls: cannot access ':/usr/local/lib': no such file or directory ldd $LD_LIBRARY_PATH/liboqs.so displays ldd: :/usr/local/lib/liboqs.so': no such file or directory |
Well, then you have the answer to your question: You did not install Alternatively, find the location of |
thank you. |
I have already set oqs.dll to system path still cant load shared library |
@vsoftco @dstebila @baentsch I followed the instructions in liboqs python wrapper to install as a shared library (make -GNinja -DBUILD_SHARED_LIBS=ON ..). Then I cloned liboqs-python and setup a venv called test inside. I then installed setup.py. I then tried to run the kem example with python3 examples/kem.py but the code breaks because it could not load the liboqs library. I have tried multiple variants of liboqs shared library command but I have not gotten any of them to work. Am I doing something wrong or missing a step?
i am using fedora 36 with openssl-devel package instead of libssl-dev , everything compiles really well and checked env and followed all precaution measures in issue #28
The text was updated successfully, but these errors were encountered: