Skip to content

Remove dylib from atomic linking #123

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

Merged
merged 1 commit into from
Jun 9, 2024

Conversation

BlackDex
Copy link
Contributor

@BlackDex BlackDex commented Jun 7, 2024

The dylib addition breaks static binaries causing them not never be static again, because the atomic lib is always added as a dynamic library.

Removing the dylib should not be an issue, since the compiler will either add it dynamically or statically based upon the compiler settings.

The `dylib` addition breaks static binaries causing them not never be
static again, because the atomic lib is always added as a dynamic
library.

Removing the `dylib` should not be an issue, since the compiler will
either add it dynamically or statically based upon the compiler
settings.
@BlackDex
Copy link
Contributor Author

BlackDex commented Jun 7, 2024

@octavonce could you check this PR please. It currently breaks static builds of Vaultwarden for example.

@BlackDex
Copy link
Contributor Author

BlackDex commented Jun 7, 2024

Also, as a reference, the same happened with rust-openssl sfackler/rust-openssl#2094

@octavonce
Copy link
Collaborator

Good catch

@octavonce octavonce merged commit 992c9da into purpleprotocol:master Jun 9, 2024
5 checks passed
@BlackDex BlackDex deleted the remove-dylib branch June 10, 2024 06:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants