-
-
Notifications
You must be signed in to change notification settings - Fork 31.2k
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
configure: --with-dbmliborder=gdbm
no longer satisfies _dbm
#98636
Comments
I'll file a PR in a minute. |
mgorny
added a commit
to mgorny/cpython
that referenced
this issue
Oct 25, 2022
Fix the gdbm_compat library detection logic to set have_gdbm_compat=yes, as expected by `--with-dbmliborder=` handler. This fixes the build failure with `--with-dbmliborder=gdbm`, and implicit fallback to ndbm with the default value.
mgorny
added a commit
to mgorny/cpython
that referenced
this issue
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
added a commit
to mgorny/cpython
that referenced
this issue
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
added a commit
to mgorny/cpython
that referenced
this issue
Dec 18, 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
added a commit
to mgorny/cpython
that referenced
this issue
Dec 31, 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.
erlend-aasland
pushed a commit
that referenced
this issue
Jan 11, 2023
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.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Bug report
It seems that the
configure
script is no longer able to build_dbm
module fromgdbm_compat
.Excerpts from configure log (full log: configure.txt):
It seems that the problem is in the following snippet:
However,
have_gdbm_compat
is not declared anymore, probably because of:declaring
have_ndbm=yes
in this case.Seems to have been introduced in ec5e253 by @tiran.
Your environment
Linked PRs
The text was updated successfully, but these errors were encountered: