-
Notifications
You must be signed in to change notification settings - Fork 20
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
libsodium error #8
Comments
The most likely reason for that error is that the wrong compiler was used while building the client libsodium (x86_64 vs RISC-V). |
in Keystone i’m in : commit ab4e7580c541a7c9798648c5423b6729c82a4c21 (branch 'origin/dev’) |
I was able to reproduce this only by running You will, currently, run into another issue after that due to changes in the Keystone build system. I'll put together a fix for that part. (It currently will not correctly copy the demo binaries into the keystone overlay directory to be included in the image, this can be done manually) I will try to clean up some of the script to prevent this from happening if you run multiple times, or with a bad environment. |
See the changes pushed in #10
|
Please be sure to follow all directions the script gives. The binaries we not copied into the image. |
so is the binaries are not copied to the image, so the get attestation script will not work, because he need those files. |
I suspect you need to rebuild the image to include the binaries. The script says to do this after it runs correctly: Unfortunately, the build system, modules, etc in Keystone are changing right now, so the documentation in the demo isn't 100% up-to-date. When it stabilizes we'll update the docs here. |
hey,

i’m getting the following error when i compile (make command in quickstart.sh)
you got any solution or idea why i get this error?
The text was updated successfully, but these errors were encountered: