-
-
Notifications
You must be signed in to change notification settings - Fork 30.9k
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-98636: Fix detecting gdbm_compat for _dbm module #98643
Conversation
896c212
to
894ada5
Compare
894ada5
to
72a9700
Compare
Ping. |
Another ping. It would be really nice to have this fixed. |
72a9700
to
7f446f0
Compare
Fix the gdbm_compat library detection logic to actually check for -lgdbm_compat independently of the ndbm detection. This fixes the build failure with `--with-dbmliborder=gdbm`, and implicit fallback to ndbm with the default value.
7f446f0
to
15510e8
Compare
@erlend-aasland, updated as requested. |
Does this need a backport? |
Unless I'm mistaken, no. The issue was introduced in ec5e253, and FWICS this in 3.12 only. |
Thanks, and sorry for the delay! If you want to pursue the AC refactorings discussed, please open an issue/PR. |
Thank you! I'm happy enough having the immediate problem fixed. |
Fix the gdbm_compat library detection logic to actually check for
-lgdbm_compat independently of the ndbm detection. This fixes the build
failure with
--with-dbmliborder=gdbm
, and implicit fallback to ndbmwith the default value.
--with-dbmliborder=gdbm
no longer satisfies_dbm
#98636