Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

MACOSX build fail with zlib-ng, upcoming fix upstream. #477

Closed
iago-lito opened this issue Mar 11, 2025 · 0 comments
Closed

MACOSX build fail with zlib-ng, upcoming fix upstream. #477

iago-lito opened this issue Mar 11, 2025 · 0 comments

Comments

@iago-lito
Copy link

Our CI broke, possibly because of this issue in zlib-ng now resolved although the fix hasn't landed yet.

In the meantime, I though I could bump zlib-ng myself within my own clone of flate2-rs, just to test whether their develop branch would fix it, but I think I'm confused how it works.

Is this line in src/ffi/c.rs not the only one that needs bumping? What does the one in Cargo.toml mean then?
Does flate2-rs download and compile its own version of zlib-ng from sources? Does it rely on system libs instead? Do we have control over that?

Anyway, happy to help, but unsure where to start ^ ^"

@rust-lang rust-lang locked and limited conversation to collaborators Mar 15, 2025
@Byron Byron converted this issue into discussion #479 Mar 15, 2025

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant