Skip to content

Conversation

@mgorny
Copy link
Contributor

@mgornymgorny 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
ContributorAuthor

Ping.

@mgorny
Copy link
ContributorAuthor

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
ContributorAuthor

@erlend-aasland, updated as requested.

@erlend-aasland
Copy link
Contributor

Does this need a backport?

@mgorny
Copy link
ContributorAuthor

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
ContributorAuthor

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

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants

@mgorny@erlend-aasland@bedevere-bot