-
Notifications
You must be signed in to change notification settings - Fork 157
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
Do not link -ldl and -lpthread unconditionally #2949
Do not link -ldl and -lpthread unconditionally #2949
Conversation
bd03e12
to
9721ca7
Compare
Yes, that's going in the right direction. 👍 At least partially, this again (like #2942 "Check for cargo when building rust language") needs to go into the top-level |
9721ca7
to
6d95466
Compare
yeah, I saw that Jakub had mentioned this but it does seem a bit too late to make such a change, no? Jakub had also mentioned erroring out, which is what I chose to do here |
It's late no matter whether in the top-level |
Gracefully disable for implicit "rust" in |
Only |
right, so add
so you're forcing me to do more autotools work, do you like seeing me suffer or something? :P will work on this next |
The implicit vs. explicit thing should be really easy ;-) in the top-level |
df478ee
to
7399ae7
Compare
@tschwinge I've made the required changes and pushed them :) tested locally and it seems to work fine on a system where glibc < 2.34. tested with |
67cad72
to
c34b0b2
Compare
Should we merge this ? Has it already been merged upstream ? It requires a rebase anyway. |
c34b0b2
to
f8d2770
Compare
ChangeLog: * Makefile.tpl: Add CRAB1_LIBS variable. * Makefile.in: Regenerate. * configure: Regenerate. * configure.ac: Check if -ldl and -lpthread are needed, and if so, add them to CRAB1_LIBS. gcc/rust/ChangeLog: * Make-lang.in: Remove overazealous LIBS = -ldl -lpthread line, link crab1 against CRAB1_LIBS.
f8d2770
to
00669b6
Compare
I'm going to merge this PR because it has been merged upstream, sadly it introduce a regression because I'm too stupid for autotools and shell scripting in general, so I'll open a follow-up PR shortly |
turns out that the bug/issue does not actually prevent the build from completing, it's just noisy but the build completes. I'll still push the fix ASAP |
No description provided.