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

attempt to use pkg-config to get include path for zlib and openssl #170

Merged
merged 1 commit into from
Mar 4, 2020
Merged

attempt to use pkg-config to get include path for zlib and openssl #170

merged 1 commit into from
Mar 4, 2020

Conversation

MagicalTux
Copy link
Contributor

...if not set in env.

This fixes #169 and I believe should not have any negative impact. Do not take my word for it however, I haven't done anything in rust until today.

Copy link
Collaborator

@wez wez left a comment

Choose a reason for hiding this comment

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

Looks good, thanks!

@wez wez merged commit 7a9b0a0 into alexcrichton:master Mar 4, 2020
wez added a commit that referenced this pull request Apr 26, 2020
This caused fairly widespread problems and it seems that the original
issue that led to this change (rust-lang/rust#69552)
should really be fixed by better defining the data exported from eg:
libz-sys rather than having downstream crates replicating the same logic
from inside that crate.

refs: #174
refs: #170
refs: #169
refs: rust-lang/rust#69552
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.

Build fails if zlib is not installed in default location, despite being available through pkg-config
2 participants