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

bpo-21622: ctypes.util find_library walk LD_LIBRARY_PATH #10453

wants to merge 2 commits into
base: master


None yet
3 participants
Copy link

jcastillo2nd commented Nov 10, 2018

Originally, issue was open for case where SONAME wasn't part of binary.

Updates to the posix case did include LD_LIBRARY_PATH, but reliance on gcc and ldconfig behavior breaks in some cases. e.g. musl on alpine builds

This provides a find method that walks the LD_LIBRARY_PATH, checks for ELF bytes, and returns the name when found or None, matching the other behavior.

This runs after all prior cases fail, does not rely on SONAME entry, gcc or ldconfig -p behavior.

Issue #21622 Walk LD_LIBRARY_PATH for library
FIXES bpo-21622 for 3.7

This comment has been minimized.

Copy link

the-knights-who-say-ni commented Nov 10, 2018

Hello, and thanks for your contribution!

I'm a bot set up to make sure that the project can legally accept your contribution by verifying you have signed the PSF contributor agreement (CLA).

Unfortunately we couldn't find an account corresponding to your GitHub username on (b.p.o) to verify you have signed the CLA (this might be simply due to a missing "GitHub Name" entry in your b.p.o account settings). This is necessary for legal reasons before we can look at your contribution. Please follow the steps outlined in the CPython devguide to rectify this issue.

You can check yourself to see if the CLA has been received.

Thanks again for your contribution, we look forward to reviewing it!

@jcastillo2nd jcastillo2nd deleted the jcastillo2nd:37/bpo-21622 branch Nov 11, 2018


This comment has been minimized.

Copy link

jcastillo2nd commented Nov 11, 2018

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment