Skip to content

Fix --with-python option not being honored when cache exists #41260

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.

Sign up for GitHub

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

Open
cxzhong wants to merge 2 commits into
base: develop
Choose a base branch
from
+7 −0
Open

Fix --with-python option not being honored when cache exists #41260

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
42c1974
Fix --with-python option not being honored when cache exists
cxzhong Dec 4, 2025
e5c3df5
Clarify cache clearing logic for --with-python option in spkg-configu…
cxzhong Dec 5, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions build/pkgs/python3/spkg-configure.m4
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -15,6 +15,12 @@ SAGE_SPKG_CONFIGURE([python3], [
[AC_MSG_ERROR([building Sage --without-python is not supported])])
ac_path_PYTHON3="$with_python"

dnl If --with-python was explicitly specified, clear the cache to force re-checking
dnl This fixes issue #41258 where changing --with-python would use stale cached values
AS_IF([test x"$ac_path_PYTHON3" != x], [
AS_UNSET([ac_cv_path_PYTHON3])
])

dnl Issue #30559: Removed the DEPCHECK for sqlite. We never use libsqlite3 from SPKG for anything
dnl other than building the python3 SPKG; so our libsqlite3 cannot create shared library conflicts.
dnl
Expand Down
Loading