diff options
| author | Alexandru Ardelean <aa@ocedo.com> | 2014-10-17 16:34:12 +0300 |
|---|---|---|
| committer | Alexandru Ardelean <aa@ocedo.com> | 2014-10-20 18:08:55 +0300 |
| commit | 8c4da0367b50cf7b4fc8941ba7af3008d86b6daf (patch) | |
| tree | 8304262524243827ae1ff36eed378b6c83431b90 /lang/python3 | |
| parent | 885fe99cd29ea6b056e816ff78dd750b0e7dde8b (diff) | |
python3: patch setup.py so that it does not include system include dirs
Seems that the Python C extensions were being
(or at least trying to be) build using '/usr/include' as the first
include folder.
Seems this issue was already fixed on MacOS X and now we've extended
it for our case.
Signed-off-by: Alexandru Ardelean <ardeleanalex@gmail.com>
Diffstat (limited to 'lang/python3')
| -rw-r--r-- | lang/python3/patches/120-do-not-add-include-dirs-when-cross-compiling.patch | 14 |
1 files changed, 14 insertions, 0 deletions
diff --git a/lang/python3/patches/120-do-not-add-include-dirs-when-cross-compiling.patch b/lang/python3/patches/120-do-not-add-include-dirs-when-cross-compiling.patch new file mode 100644 index 000000000..44be1c8ff --- /dev/null +++ b/lang/python3/patches/120-do-not-add-include-dirs-when-cross-compiling.patch @@ -0,0 +1,14 @@ +diff --git a/setup.py b/setup.py +index 93f390f..ace1494 100644 +--- a/setup.py ++++ b/setup.py +@@ -461,7 +461,8 @@ class PyBuildExt(build_ext): + add_dir_to_list(dir_list, directory) + + if os.path.normpath(sys.base_prefix) != '/usr' \ +- and not sysconfig.get_config_var('PYTHONFRAMEWORK'): ++ and not sysconfig.get_config_var('PYTHONFRAMEWORK') \ ++ and not cross_compiling: + # OSX note: Don't add LIBDIR and INCLUDEDIR to building a framework + # (PYTHONFRAMEWORK is set) to avoid # linking problems when + # building a framework with different architectures than |