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

Fix zlib_installed not using the correct flags #131

Merged
merged 2 commits into from
May 30, 2023

Conversation

BlackDex
Copy link
Contributor

The zlib_installed function does not use the correct compiler flags when checking if there already is a libz library pre-build.

This causes libz-sys to build the internal libz version, which might be different from the pre-build libz version, and might cause issues with other libraries which also used the pre-build libz wether or not it's static or shared.

I came across this when using my custom toolchain build images to build static musl binaries. And this crate seemed to build the built-in version anyways. Which is an other issue, not addressed in this PR.

The `zlib_installed` function does not use the correct compiler flags
when checking if there already is a libz library pre-build.

This causes libz-sys to build the internal libz version, which might be
different from the pre-build libz version, and might cause issues with
other libraries which also used the pre-build libz wether or not it's
static or shared.

I came across this when using my custom toolchain build images to build
static musl binaries. And this crate seemed to build the built-in
version anyways. Which is an other issue, not addressed in this PR.
@BlackDex BlackDex changed the title Fix zlib_installed not using the correct flags Fix zlib_installed not using the correct flags May 29, 2023
Save two lines without being less descriptive.
Copy link
Member

@Byron Byron left a comment

Choose a reason for hiding this comment

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

Thanks a lot for the fix! Even though I have no experience with the build system used, but judging from the documentation of to_command() it should be the correct way to go from compiler tool to invocable command.

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