From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: "S. Lockwood-Childs" <sjl@vctlabs.com>,
openembedded-devel@lists.openembedded.org
Subject: Re: meta-python: outrageously long cython shebang with pyro
Date: Mon, 15 May 2017 14:58:33 +0300 [thread overview]
Message-ID: <4bbb34e6-8970-8b4e-7d2f-03d0b9a7b549@linux.intel.com> (raw)
In-Reply-To: <20170513063415.GQ9767@vctlabs.com>
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
next prev parent reply other threads:[~2017-05-15 12:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-13 6:34 meta-python: outrageously long cython shebang with pyro S. Lockwood-Childs
2017-05-15 11:58 ` Alexander Kanavin [this message]
2017-05-19 22:27 ` [meta-python][master][pyro][PATCH] python-cython: mangle scripts to use /usr/bin/env python S. Lockwood-Childs
2017-05-19 23:45 ` [meta-python][master][pyro][PATCH, v2] " S. Lockwood-Childs
2017-05-20 0:13 ` [meta-python][master][pyro][PATCH, v3] " S. Lockwood-Childs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4bbb34e6-8970-8b4e-7d2f-03d0b9a7b549@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=sjl@vctlabs.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox