-
-
Notifications
You must be signed in to change notification settings - Fork 31.7k
cross-building python 3.6 with an older interpreter fails #71621
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
Comments
Cross-building the 3.6 source with PYTHON_FOR_BUILD using archlinux python 3.5.1 as found in PATH, fails with: _PYTHON_PROJECT_BASE=/home/xavier/src/android/pyona/build/python3.6-android-21-x86 _PYTHON_HOST_PLATFORM=linux-x86 PYTHONPATH=/home/xavier/src/packages/android/cpython/Lib:/home/xavier/src/packages/android/cpython/Lib/plat-i386-linux-gnu python3 -S -m sysconfig --generate-posix-vars ;\
if test $? -ne 0 ; then \
echo "generate-posix-vars failed" ; \
rm -f ./pybuilddir.txt ; \
exit 1 ; \
fi
Could not import runpy module
Traceback (most recent call last):
File "/home/xavier/src/packages/android/cpython/Lib/runpy.py", line 15, in <module>
import importlib.util
File "/home/xavier/src/packages/android/cpython/Lib/importlib/util.py", line 25
raise ValueError(f'no package specified for {repr(name)} '
^
SyntaxError: invalid syntax
generate-posix-vars failed The reason is that the syntax of formatted string literals is unknown to python 3.5. |
yes, I think we have to limit the choice of the interpreter for the build to the same major version. |
With this patch, cross-building the 3.6 source with only python 3.5.1 on the PATH, produces the following configure error:
|
New patch that gets rid of the changes in configure made by my version of autoconf. This version is 2.69 though, i.e. the same as the generated configure file that is under control of mercurial in the default branch. |
restrict_interp_2.patch: LGTM. not ... == '...' can be written ... != '...', no? |
I think the way the condition was written previously is more expressive, so the patch does not change that. The 'not' here expresses the fact that in the shell syntax, the condition is true when the test returns 0 [1], but we still want to express the fact that the 'break' is taken when the interpreter version matches $PACKAGE_VERSION. |
New changeset 62802d373e9f by Xavier de Gaye in branch 'default': |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
bugs.python.org fields:
The text was updated successfully, but these errors were encountered: