diff options
author | Tom Zanussi <tom.zanussi@intel.com> | 2011-11-04 20:25:03 -0500 |
---|---|---|
committer | Richard Purdie <richard.purdie@linuxfoundation.org> | 2011-11-08 21:44:23 +0000 |
commit | 25fae81538a92e15eab3fc169ebce44505f67839 (patch) | |
tree | b2850b3d5693e4aa1aee87b3a7eed61f8c07e78d /meta/recipes-devtools/python/python-2.7-manifest.inc | |
parent | 5be9785f344ec4d7580f7ec68e29dba9fceb0a0a (diff) | |
download | openembedded-core-25fae81538a92e15eab3fc169ebce44505f67839.tar.gz openembedded-core-25fae81538a92e15eab3fc169ebce44505f67839.tar.bz2 openembedded-core-25fae81538a92e15eab3fc169ebce44505f67839.tar.xz openembedded-core-25fae81538a92e15eab3fc169ebce44505f67839.zip |
python: skip setup.py 'import check' when cross-compiling
build_extension() in setup.py, as part of the build process, does an
'import check' on the built extension. The import check in turn
dlopen()'s the shared library associated with the extension, which
isn't something that makes sense if that library was cross-compiled
for a different architecture.
This was noticed with an x86_64 target that was compiled with avx
support, because it caused 'illegal instruction' exceptions:
| /bin/sh: line 1: 14575 Illegal instruction ... -E ./setup.py -q build
For other target architectures, it doesn't necessarily cause illegal
instruction exceptions, but still fails. For example, on arm, the
failure pathway causes this warning:
*** WARNING: renaming "cmath" since importing it failed: .../cmath.so:
wrong ELF class: ELFCLASS32
This patch to setup.py and the associated recipe changes allow the
whole 'import check' logic to be skipped when cross-compiling.
Signed-off-by: Tom Zanussi <tom.zanussi@intel.com>
Diffstat (limited to 'meta/recipes-devtools/python/python-2.7-manifest.inc')
0 files changed, 0 insertions, 0 deletions