On 05/13/2017 09:34 AM, S. Lockwood-Childs wrote:
The cython recipe builds fine -- this is runtime breakage from recipes that
depend on cython. This was always a danger when using lengthy toplevel
directory names (e.g. as tends to happen in jenkins auto-builds), but
now I managed to get the dreaded "bad interpreter: No such file or directory"
failure from cython despite a not-ridiculously-long toplevel path:

#!/var/data/sjl/poky/build/tmp/work/armv7a-neon-oe-linux-gnueabi/libplist/git-r0/recipe-sysroot-native/usr/bin/python-native/python

We typically patch the upstream code to use

#!/usr/bin/env python

There is some PATH environment variable magic that will ensure that the correct version of python will come first in the PATH, so it should be safe to do. There's a ton of examples in oe-core.


Alex

--
_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.openembedded.org/mailman/listinfo/openembedded-devel

Reply via email to