You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the GNU makefiles, WINDOWS is defined when building on Windows, and WINDOWS_BUILD is defined when building for Windows. The selection of Python (python on Windows, python3 elsewhere — a practical choice that works for us) is based on WINDOWS_BUILD but should be based on WINDOWS.
This does not currently cause any CI failure or uncaught failure, but it's very fragile.
This causes an error when building with mingw on Linux, as in tests/scripts/all.sh build_mingw. Since PYTHON is python, which is Python 2.7, all Python code invoked from makefiles runs with Python 2. For generate_test_code.py, this still works because this script was last modified a long time ago when we ensured that our scripts worked with both Python 2.x and Python 3.x. In the development branch, tests/Makefile runs $(PYTHON) scripts/generate_psa_tests.py --list to enumerate potentially generated test data files, which results in the error
This is currently harmless on the CI because the error occurs in a $(shell …) make function which does not check the command's return status, and all the generated test data is pre-generated before doing the build.
The text was updated successfully, but these errors were encountered:
The makefiles look for python3 on Unix-like systems where python is often
Python 2. This uses sh code so it doesn't work on Windows. On Windows, the
makefiles just assume that python is Python 3.
The code was incorrectly deciding not to try python3 based on WINDOWS_BUILD,
which indicates that the build is *for* Windows. Switch to checking WINDOWS,
which indicates that the build is *on* Windows.
FixMbed-TLS#4774
Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
The makefiles look for python3 on Unix-like systems where python is often
Python 2. This uses sh code so it doesn't work on Windows. On Windows, the
makefiles just assume that python is Python 3.
The code was incorrectly deciding not to try python3 based on WINDOWS_BUILD,
which indicates that the build is *for* Windows. Switch to checking WINDOWS,
which indicates that the build is *on* Windows.
FixMbed-TLS#4774
Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
The makefiles look for python3 on Unix-like systems where python is often
Python 2. This uses sh code so it doesn't work on Windows. On Windows, the
makefiles just assume that python is Python 3.
The code was incorrectly deciding not to try python3 based on WINDOWS_BUILD,
which indicates that the build is *for* Windows. Switch to checking WINDOWS,
which indicates that the build is *on* Windows.
FixMbed-TLS#4774
Signed-off-by: Gilles Peskine <Gilles.Peskine@arm.com>
In the GNU makefiles,
WINDOWS
is defined when building on Windows, andWINDOWS_BUILD
is defined when building for Windows. The selection of Python (python
on Windows,python3
elsewhere — a practical choice that works for us) is based onWINDOWS_BUILD
but should be based onWINDOWS
.This does not currently cause any CI failure or uncaught failure, but it's very fragile.
This causes an error when building with mingw on Linux, as in
tests/scripts/all.sh build_mingw
. SincePYTHON
ispython
, which is Python 2.7, all Python code invoked from makefiles runs with Python 2. Forgenerate_test_code.py
, this still works because this script was last modified a long time ago when we ensured that our scripts worked with both Python 2.x and Python 3.x. In the development branch,tests/Makefile
runs$(PYTHON) scripts/generate_psa_tests.py --list
to enumerate potentially generated test data files, which results in the errorThis is currently harmless on the CI because the error occurs in a
$(shell …)
make function which does not check the command's return status, and all the generated test data is pre-generated before doing the build.The text was updated successfully, but these errors were encountered: