-
Notifications
You must be signed in to change notification settings - Fork 29
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
Support for Debian based distros ?! #8
Comments
These messages indicate that you have not installed the License for Kunpeng Accelerator. To get more information about How to install the License, please refer the follow location at In addition, since your OpenSSL is a custom installation, you need to specify the OpenSSL installation path when compiling KAE. cd KAE |
I see. It would be nice to add this info to the README..
Yes, I've done this. Same for Still I am doing something wrong because it links to the global libssl.so:
not to the one in the custom build:
Due to the license issue I won't be able to continue testing this on Ubuntu. I am doing it out of curiosity. Feel free to close this issue! Thank you! |
This problem is because the OpenSSL you installed does not link to the correct dynamic library at runtime, please reinstall your OpenSSL via ./config -Wl, -rpath=/your/custom/path/ . If symbol EVP_mdc2 not defined still occurs, please upgrade OpenSSL to version 1.1.1a or later |
I use 1.1.1d. With
it is still the same:
I will read carefully OpenSSL's INSTALL file in the coming evenings to see what I do wrong. |
-Wl, -rpath should specify the correct location of OpenSSL libcrypto.so, please try the config as follow: |
This fixed it! Thank you! |
Hi,
Is KAE supported for Debian based distros ? Because the README seems to be about RedHat based ones.
I've tried to install it on Ubuntu 18.04.4 LTS aarch64 with the following changes:
But those:
fail with
No such device
.I was not able to finish the setup because I've installed OpenSSL in a custom path, so that it does not override the one installed from Ubuntu packages, but now I face some linking errors. I'll report here if I face any issues with KAE!
The text was updated successfully, but these errors were encountered: