Skip to content

autoconf: Don't use generated file as sentinel #35

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

Merged
erlend-aasland merged 1 commit into from
Dec 17, 2024
Merged

autoconf: Don't use generated file as sentinel #35

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
autoconf: Don't use generated file as sentinel 
`autoreconf` generates `pyconfig.h.in` so it shouldn't be used to
sanity check the presence of the CPython source.
  • Loading branch information
@rhansen
rhansen committed Dec 4, 2024
commit 0bc2246254f67288d4661f3d59ea993fac45a22c
5 changes: 3 additions & 2 deletions autoconf/entry.sh
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,9 @@ AUTOCONF=$BIN/autoconf
AUTORECONF=$BIN/autoreconf

if [ "$#" = "0" ]; then
SENTINEL=/src/pyconfig.h.in
# This is the same sentinel used for AC_CONFIG_SRCDIR in CPython's
# configure.ac.
SENTINEL=/src/Include/object.h

if [ ! -e ${SENTINEL} ]; then
echo "ERROR: ${SENTINEL} not found "
Expand All @@ -24,4 +26,3 @@ if [ "$#" = "0" ]; then
fi

exec "$@"

Loading