-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Remove link directives for libutil on linux-gnu targets #2046
Conversation
These are all handled in src/unix/mod.rs now, which also addresses the crt-static case; no linux-gnu target should have any link directives in any other module. This fixes static linking with glibc for various architectures.
r? @Amanieu (rust-highfive has picked a reviewer for you, use r? to override) |
r? @JohnTitor |
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.
Thanks for the follow-up, Josh!
@bors r+ |
📌 Commit 6859d47 has been approved by |
Remove link directives for libutil on linux-gnu targets These are all handled in src/unix/mod.rs now, which also addresses the crt-static case; no linux-gnu target should have any link directives in any other module. This fixes static linking with glibc for various architectures.
💔 Test failed - checks-actions |
Failure looks like a transient network issue. Retrying. @bors retry |
Looks like we're now hitting rust-lang/cargo#9101 , which was caused by a change in serde. |
#2048 should fix the CI issue. |
☀️ Test successful - checks-actions, checks-cirrus-freebsd-11, checks-cirrus-freebsd-12, checks-cirrus-freebsd-13 |
These are all handled in src/unix/mod.rs now, which also addresses the
crt-static case; no linux-gnu target should have any link directives in
any other module.
This fixes static linking with glibc for various architectures.
Fixes #2033