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

.github: Fix Rust version for release to 1.58 #3961

Conversation

rbradford
Copy link
Member

Unfortunately Rust 1.59 produces binaries that segfault when compiled
with musl-gcc wrappers. Which is exactly how we produce out aarch64 and
musl binaries for the release.

See: rust-lang/rust#95926

Signed-off-by: Rob Bradford robert.bradford@intel.com

Unfortunately Rust 1.59 produces binaries that segfault when compiled
with musl-gcc wrappers. Which is exactly how we produce out aarch64 and
musl binaries for the release.

See: rust-lang/rust#95926

Signed-off-by: Rob Bradford <robert.bradford@intel.com>
@rbradford
Copy link
Member Author

rbradford commented Apr 11, 2022

I'm not 100% sure if we are affected by this issue at the moment due to the complexity within the GH actions for cross building. As such I think it's a good precaution as we are heading into our release later this week.

@joshtriplett
Copy link

@rbradford You can also work around the problem by passing -C relocation-model=static everywhere you use musl-gcc (or any of the cross-compiler target-prefixed versions of musl-gcc).

@michael2012z
Copy link
Member

I'm not 100% sure if we are affected by this issue at the moment due to the complexity within the GH actions for cross building. As such I think it's a good precaution as we are heading into our release later this week.

This is a good idea.

@rbradford rbradford merged commit 6a09925 into cloud-hypervisor:main Apr 11, 2022
@rbradford rbradford deleted the 2022-04-11-fix-rust-version-for-release-binaries branch April 11, 2022 21:53
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.

4 participants