-
-
Notifications
You must be signed in to change notification settings - Fork 31.7k
gh-127604: ensure -ldl
is passed to the linker when dladdr1
is found
#133040
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
gh-127604: ensure -ldl
is passed to the linker when dladdr1
is found
#133040
Conversation
-ldl
is passed to the linker when dladdr1
is found-ldl
is passed to the linker when dladdr1
is found
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.
LGTM, but let's run buildbots to make sure we didn't break anything.
🤖 New build scheduled with the buildbot fleet by @ZeroIntensity for commit 3d22310 🤖 Results will be shown at: If you want to schedule another build, you need to add the 🔨 test-with-buildbots label again. |
Co-authored-by: Victor Stinner <[email protected]>
Co-authored-by: Peter Bierma <[email protected]>
@picnixz This seems to have resulted in the |
Looks like it's not just macOS and iOS; Ubuntu builds now include compilation statements like |
Aaaaaah I don't understand:( Why would it include it twice I'll investigate |
Mmh, it's actually in Python/traceback.c. A bit more annoying. |
Hum. I also forgot removing |
faulthandler is built as a built-in module, since Py_FatalError() uses it (dump the backtrace and than turns off faulthandler). |
I found the issue. Because of |
PR is ready: #133071.
And yes, that's why I didn't see the warnings. I use gcc and not clang |
I was wondering if autoreconf was smart enough to deal with the extra flags. Buildbots passed so I figured it was ok :(. |
See https://man7.org/linux/man-pages/man3/dladdr.3.html#LIBRARY for details.
faulthandler
#127604