Uh oh!
There was an error while loading.Please reload this page.
- Notifications
You must be signed in to change notification settings - Fork249
Ensure that Hacl_Hash_SHA2 does not appear as a library to link to#312
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Ensure that Hacl_Hash_SHA2 does not appear as a library to link to#312
Uh oh!
There was an error while loading.Please reload this page.
Conversation
zanieb left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Makes sense to me if the builds pass.
zanieb commentedSep 6, 2024
Can you share a diff of the |
ntamas commentedSep 6, 2024
Sure! I'm attaching two diffs here; Both diffs are attached in a ZIP file here:diffs.zip |
zanieb commentedSep 9, 2024
Thanks! The change in the metadata makes sense to me but I don't fully understand why it was written this way in the first place? |
ntamas commentedSep 9, 2024
I don't know either -- maybe@indygreg remembers? I think he was the one who initially wrote the code for supporting Python 3.12 where the pre-3.12 hash functions were replaced with implementations from HACL*. |
When trying to update PyOxidizer and PyOxy to support standalone builds of Python 3.12, I noticed that the build attempted to link to a library named
Hacl_Hash_SHA2whenpyoxywas linked (with-lHacl_Hash_SHA2). This PR fixes the metadata inPYTHON.json.