Skip to content
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

[openssl] Fix build for Android x86. #24801

Conversation

AenBleidd
Copy link
Contributor

OpenSSL3 uses atomics that are broken on clang for Android x86.
This commit fixes the build by disabling usage of these atomics on Android x86 only.

This fixes #24021.

Signed-off-by: Vitalii Koshura [email protected]

OpenSSL3 uses atomics that are broken on clang for Android x86.
This commit fixes the build by disabling usage of these atomics on Android x86 only.

This fixes microsoft#24021.

Signed-off-by: Vitalii Koshura <[email protected]>
@AenBleidd
Copy link
Contributor Author

This PR is tested using overlay ports here: BOINC/boinc#4749

@Adela0814 Adela0814 added info:reviewed Pull Request changes follow basic guidelines category:community-triplet A PR or issue related to community triplets not officially validated by the vcpkg team. labels May 20, 2022
@talregev
Copy link
Contributor

follow

Copy link

@github-actions github-actions bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a new experimental fast check for PR issues. Please let us know if this bot is helpful!

PRs must add only one version and must not modify any published versions

When making any changes to a library, the version or port-version in vcpkg.json or CONTROL must be modified.

error: checked-in files for openssl have changed but the version was not updated
version: 3.0.3#3
old SHA: f72e602e3fde9d592c2f8d01c4ca0ed21c4df63b
new SHA: 03f8e7e77fd71aaf31af19896c07deaa58b02662
Did you remember to update the version or port version?
Use --overwrite-version to bypass this check
***No files were updated***

@talregev
Copy link
Contributor

Please hold for this fix. I want to investigate another solution.
@AenBleidd Can you put this PR on draft? Thank you.

Copy link
Contributor

@talregev talregev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There is another solution for update the ndk version (the clang version) and it solve the bug.
@AenBleidd please put this PR on draft.

@AenBleidd
Copy link
Contributor Author

@BillyONeal, sorry for 'not nice' words. Didn't know you have such a policy. Next time I'll try to be more polite.
@talregev, I remember I tried with NDK update, and failed, but of course you can try again. Previous build took 11 hours, so you have enough time to test your fix

@talregev
Copy link
Contributor

@BillyONeal, sorry for 'not nice' words. Didn't know you have such a policy. Next time I'll try to be more polite. @talregev, I remember I tried with NDK update, and failed, but of course you can try again. Previous build took 11 hours, so you have enough time to test your fix

Please review my PR:
BOINC/boinc#4751

@talregev
Copy link
Contributor

@BillyONeal, sorry for 'not nice' words. Didn't know you have such a policy. Next time I'll try to be more polite. @talregev, I remember I tried with NDK update, and failed, but of course you can try again. Previous build took 11 hours, so you have enough time to test your fix

Because of your comment I understand the problem.

@BillyONeal
Copy link
Member

@BillyONeal, sorry for 'not nice' words.

No problem!

@talregev
Copy link
Contributor

talregev commented May 20, 2022

@BillyONeal, sorry for 'not nice' words. Didn't know you have such a policy. Next time I'll try to be more polite. @talregev, I remember I tried with NDK update, and failed, but of course you can try again. Previous build took 11 hours, so you have enough time to test your fix

I fix #24021 issue in this PR BOINC/boinc#4751 without this PR fix.

@AenBleidd
Copy link
Contributor Author

@talregev, congratulations with the fix.
@BillyONeal, I'm closing this PR because looks like my previous assumption was not correct and tests were not correct either. I was just using an NDK with an incomplete implementation of atomics for x86.

@AenBleidd AenBleidd closed this May 20, 2022
@AenBleidd AenBleidd deleted the vko_fix_openssl3_issue_on_android_x86 branch May 20, 2022 22:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
category:community-triplet A PR or issue related to community triplets not officially validated by the vcpkg team. info:reviewed Pull Request changes follow basic guidelines
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[openssl] build failure on Android x86
4 participants