Skip to content

Conversation

@mgorny
Copy link
Contributor

@mgorny mgorny commented Oct 25, 2022

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.

@mgorny
Copy link
Contributor Author

mgorny commented Nov 4, 2022

Ping.

@mgorny
Copy link
Contributor Author

mgorny commented Dec 7, 2022

Another ping. It would be really nice to have this 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 ndbm with the default value.
@mgorny
Copy link
Contributor Author

mgorny commented Dec 31, 2022

@erlend-aasland, updated as requested.

@erlend-aasland
Copy link
Contributor

Does this need a backport?

@mgorny
Copy link
Contributor Author

mgorny commented Jan 11, 2023

Does this need a backport?

Unless I'm mistaken, no. The issue was introduced in ec5e253, and FWICS this in 3.12 only.

@erlend-aasland
Copy link
Contributor

Thanks, and sorry for the delay!

If you want to pursue the AC refactorings discussed, please open an issue/PR.

@mgorny
Copy link
Contributor Author

mgorny commented Jan 12, 2023

Thank you! I'm happy enough having the immediate problem fixed.

@mgorny mgorny deleted the gdbm_compat-98636 branch January 12, 2023 06:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

3 participants