On 13 November 2015 at 20:44, Burton, Ross <[email protected]> wrote:
> This failed on the autobuilder in the world-lsb target: > > | ./Programs/_freeze_importlib \ > | > /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-world-lsb/build/build/tmp/work/x86-pokymllib32-linux/lib32-python3/3.5.0-r1.0/ > Python-3.5.0/Lib/importlib/_bootstrap.py Python/importlib.h > | ./Programs/_freeze_importlib \ > | > /home/pokybuild/yocto-autobuilder/yocto-worker/nightly-world-lsb/build/build/tmp/work/x86-pokymllib32-linux/lib32-python3/3.5.0-r1.0/ > Python-3.5.0/Lib/importlib/_bootstrap_external.py Python > /importlib_external.h > | ./Programs/_freeze_importlib: error while loading shared libraries: > libz.so.1: cannot open shared object file: No such file or directory > | ./Programs/_freeze_importlib: error while loading shared libraries: > libz.so.1: cannot open shared object file: No such file or directory > > Considering zlib is a DEPENDS I have no idea why this happens. :( > The problem appears to be that _freeze_importlib is a binary compiled and ran at build time but using the target compiler. For you your build environment and the target environment were probably close enough that it works, on some ABs the loader paths are different, and obviously if you build for a different architecture it just fails. | ./Programs/_freeze_importlib: 1: ./Programs/_freeze_importlib: Syntax error: word unexpected (expecting ")") $ file _freeze_importlib _freeze_importlib: ELF 32-bit LSB executable, ARM, EABI5 version 1 (SYSV), dynamically linked, interpreter /lib/ld-linux.so.3, for GNU/Linux 2.6.32, BuildID[sha1]=f5defa61a5f1e65c6be7219dc1bfff59d510cd78, not stripped Yeah running an ARM binary on x86 isn't going to work. Ross
-- _______________________________________________ Openembedded-core mailing list [email protected] http://lists.openembedded.org/mailman/listinfo/openembedded-core
