python3: improve isolation of build environment and error handling
authorThomas Petazzoni <thomas.petazzoni@free-electrons.com>
Tue, 8 Jul 2014 20:17:53 +0000 (22:17 +0200)
committerPeter Korsgaard <peter@korsgaard.com>
Wed, 9 Jul 2014 11:19:20 +0000 (13:19 +0200)
commit5364b22b6c309073d59f593c3b5b1a9b3246e957
tree4940d9fd207169a5465d20d0e1c84afaf300c796
parent5476b7273f0e5e58b59da9bf6403366d08e6b585
python3: improve isolation of build environment and error handling

This commit mainly fixes bug #7268 by improving the isolation of
the build environment by making sure some host environment header
paths do not leak into the target build. The investigation was done by
David <buildroot-2014@inbox.com>. This is done by not calling the
add_multiarch_paths() function of setup.py when we're cross-compiling,
a change made in the newly introduced
python3-012-dont-add-multiarch-path.patch.

In addition to this, another patch is added to make sure the build is
aborted when one of the Python module fails to build. This is done in
python3-013-abort-on-failed-modules.patch. Without this, the Python
setup.py script simply logs which module failed to build, but doesn't
abort, so it's hard to notice when there is a problem.

[Peter: slightly reword commit message]
Cc: David <buildroot-2014@inbox.com>
Signed-off-by: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
package/python3/python3-012-dont-add-multiarch-path.patch [new file with mode: 0644]
package/python3/python3-013-abort-on-failed-modules.patch [new file with mode: 0644]