-
Notifications
You must be signed in to change notification settings - Fork 160
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
Update bzip2-sys in order to use "static" feature #628
Conversation
9c5ab30
to
014aa72
Compare
From the PR's description, seems the |
Yes, but |
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.
LGTM
Please fix the sign-off |
It should be good to go now. |
How about fork it to TiKV org and introduce the feature directly? So that only thing we need to do is using a patch in TiKV's Cargo.toml. |
It's possible, yes. Here I just wanted to fix the build and not create forks and other moving parts 😅 . |
trifectatechfoundation/bzip2-rs#78 is merged, you can use the patch directly in TiKV now. |
I can update the PR when the change is included in the next release https://crates.io/crates/bzip2-sys. |
This is necessary in order to guarantee that it'll be statically linked. Signed-off-by: Arthur Silva <[email protected]>
PR updated to the latest crates.io version with the |
/merge |
/run-all-tests |
Due to trifectatechfoundation/bzip2-rs#58
bzip2-sys
versions above 0.1.8 do not guarantee that bzip2 is statically linked.Which in turn causes the build to fail depending if pkg-config says bzip2 is available.