Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: "S. Lockwood-Childs" <sjl@vctlabs.com>
To: openembedded-devel@lists.openembedded.org
Subject: meta-python: outrageously long cython shebang with pyro
Date: Fri, 12 May 2017 23:34:15 -0700	[thread overview]
Message-ID: <20170513063415.GQ9767@vctlabs.com> (raw)

The recipe-specific sysroots in pyro are a wonderful thing for uncovering 
missing dependencies, but they also make it easier than ever to break
the cython scripts by exceeding the measly 128-byte limit on shebang lines. 

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

Does anybody know of a recommended strategy for solving the shebang problem,
now that it has been exacerbated by the sysroot move? I'll be happy to submit a
corresponding cython patch if so. 


             reply	other threads:[~2017-05-13  6:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-13  6:34 S. Lockwood-Childs [this message]
2017-05-15 11:58 ` meta-python: outrageously long cython shebang with pyro Alexander Kanavin
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=20170513063415.GQ9767@vctlabs.com \
    --to=sjl@vctlabs.com \
    --cc=openembedded-devel@lists.openembedded.org \
    /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