-
Notifications
You must be signed in to change notification settings - Fork 331
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
libsect283k1_ubuntu.so: cannot open shared object file #7
Comments
This is because you've not setup BTW, be aware that the lib will still not work for you because you're in centos instead of ubuntu. We've not supported centos yet. |
where do i get this library from? i appreciate that it won't work on Centos7 but the container i assume should have this library installed. Is this library custom or is it provided by Ubuntu repositories? I do not see much reference outside of this project |
Yes, this is our custom library. |
is it available on a repository somewhere, a bit stuck without it. |
It's under |
I only see Header files here, is there C file to compile to Shared library? I assume i would need to do something like the following assuming i had the C
|
So temporary work around
We can set this in Dockerfile ENV
|
|
The problem should have been fixed. |
How can i compile the library for centos, are we missing the C files. It works as expected now for Docker container i can start iotex-server without shared library. |
You're actually using the shared library. You don't need to setup |
How can i build it for Centos though ? |
We currently only ship the library binary, so that you're not able to build it on centos. We're still testing it with different linux distributions. |
i assume sect283k1 is your lightweight ECC implementation ? |
copy /go/src/github.com/iotexproject/iotex-core/crypto/lib/ibsect283k1_ubuntu.so /usr/lib problem solved. |
@wyh136 bit of a hack but yes that will work, if you get any updates to this library in future you need to ensure you are using latest version so that should be done within your build, Iotex actually have a working Docker image (sort of most recent has bug) From Dockerfile
As this is part of Dockerfile it is updated each time you pull latest and re-run docker build |
built the server as per instructions and ran
make server
I tried this both on a dedicated Centos7 build as well as using Docker container
There is also no running process in docker container, by running the following inside of container or in my build directory
The text was updated successfully, but these errors were encountered: