-
Notifications
You must be signed in to change notification settings - Fork 193
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
Build broken for musl targets #359
Comments
jean-airoldie/zeromq-src-rs#22 upstream will fix this issue as long as the resulting release is consumed. |
I think this is the same problem that broke my builds, since last night. Full log:
I'm on macos and
|
@andrewdavidmackenzie I don't think that's the same issue. Are you on MacOS Intel or ARM64 running the build? Is the build running in a container or on your hardware directly? Wherever that build is running, what version of the git submodule in |
I'll try forcing it back in a while when back at keyboard. I'm on macos (EDIT: Intel) and it fails native and in docker (with "act") and fails identically on my Linux laptop too, and in GHAction, without any code change from me overnight. |
Looking at the released versions, I think the releaser forgot to package the vendored code. The size of the most recent release is a fraction of the old sizes. |
When I looked in the path reported in the error, only lib.rs was there. |
I opened jean-airoldie/zeromq-src-rs#23, I think it was a mistake in the release process. If you pin to |
OK, this is interesting. In my .lock file it is already 0.2.2
but the path in the error is 0.2.3!!! |
Appears in $HOME/.cargo/ ...
Something is up with my install by the looks of it? |
Cargo update, and it's now 0.2.3 in Cargo.lock, but the error is the same off-course.. :-( |
I |
In a new project, Adding "zeromq-src", version = "0.2.2+4.3.4" as a dependency in Cargo.toml, leads to it appearing as "zeromq-src", "0.2.3+4.3.4" in the Cargo.lock file !! :-( I'm lost I think. |
Deleted binary files in .cargo and completely rebuilt cargo's cache and index. no fix. |
Just found this issue, looks like I'm not the only person suddenly getting these errors! I had builds working last night that are now failing with errors like |
jean-airoldie/zeromq-src-rs#23 |
I'm not sure if you have any features taking advantage of the most recent
zeromq-src-rs
, but I opened an upstream issue about the problem there.zeromq-src 0.10.0
doesn't have this build issue. This broke our downstream builds, when we started consumingzmq 0.10.0
.The text was updated successfully, but these errors were encountered: