-
Notifications
You must be signed in to change notification settings - Fork 168
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
Building on 32-bit systems fail #494
Comments
This is related to #492. I added some comments over there where I suggest we could probably change all The actual failing part is here: https://github.com/search?q=repo%3Adedis%2Fprotobuf+32bit&type=code, because if you would use the DKG in a mixed 32/64 bit environment, it will fail. However, following Merlin -> opaque, and looking how it is used there, I don't think it's using the DKG part of kyber at all. So if you can skip the tests, I think you should be safe. You don't need to open issues for each failure. @pierluca now that we have an actual failing use-case for #492, shall we try to fix it by putting |
I was trying to skip all of the tests, however, while skipping them, I ran into the genDistSecrets in an init function, and this was causing a segfault; I'm not familiar enough with go, so for now, we just skip all of the tests, and hopefully we can re-enable them once there is a release with the 32bit support :) |
Thanks for the comment. Can you elaborate a bit more, please? You wrote that you skipped all the tests, but then ran into a call to |
Hi, it's And, what I attempted to do was
but what i couldn't figure out was which test this was associated with as it was between |
That might be Instead of What architecture are you working on? |
I work with amd64, arm64, armhf, armel and i386 - so 2 64-bit and 3 32-bit :) I think overall though, maybe the constraints are overkill, and this all goes away when 492 is taken care of, so maybe not focus on this at all? |
If we can fix it with a build constraint it can be solved in So, yes, #492 is the way to go. But it'll take time. Speak up if you're looking for a project... @pierluca what do you think about adding some build constraints in the dkg directories? We either add explicitly working 64-bit architectures, or exclude 32-bit ones. I have a small preference for excluding, as I believe it's more rare to have 32-bit nowadays, than seeing a new 64-bit popping up where we'd need to add a new entry. |
Sorry for the slow response. |
It currently panics on 32-bit architectures, so there is no compatibility to be kept :)
I thought adding some comments in the package itself. Do you want also comments in the main README.md? And yes, if there is a v4, this should definitely be addressed at that moment. @steev do you have some cycles to make a first PR for this? It should contain:
Else I think later this month I can also do it. |
Fixed in #529 |
We have kyber in our Kali Linux repositories as a dependency of Merlin and one thing that has come up in our CI is that kyber does not build on 32-bit systems.
You can see our build logs for armel, armhf, and i386 at each of the links; the basic gist is that while it compiles fine on 32-bit, the tests are failing.
This is only one example of the failures, and I'm not sure if I should open one for each individually or not.
The text was updated successfully, but these errors were encountered: