All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ross Burton <ross.burton@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/4] Don't use create_wrapper to short-circuit interpretters
Date: Wed, 12 Jun 2013 17:49:38 +0100	[thread overview]
Message-ID: <cover.1371055550.git.ross.burton@intel.com> (raw)

Hi,

create_wrapper was previously abused to invoke the Python/Perl interpretters
directly instead of relying on #! parsing, which is read into a 128 byte buffer
so breaks with deep build directories.

The new create_wrapper is stricter about it's input so this trick doesn't work
anymore.  Luckily there's already a "nativeperl" binary in the sysroot's
/usr/bin, so by adding a "nativepython" alongside it[1] recipes that used
create_wrapper can be changed to munge the #! line to e.g. /usr/bin/env
nativeperl.

(this series obsoletes 3 of the patches that Saul sent earlier involve
create_wrapper)

Ross

[1] The existing nativeperl is a wrapper, the new nativepython is a
symlink. Both seem to work and I can't see a good reason for a wrapper instead
of a relative symlink.

The following changes since commit b87429fdb45f82ebe4060fea8c4ecd6e4bc1ae52:

  bitbake: Add missing file that went out of sync (2013-06-12 13:13:21 +0100)

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib ross/wrap

for you to fetch changes up to 8237763ebcc3cfe4388690056a7c0fed8d65a6c2:

  gnome-doc-utils: drop the usage of create_wrapper (2013-06-12 17:44:39 +0100)

----------------------------------------------------------------
Ross Burton (4):
      dpkg: drop the usage of create_wrapper
      python-native: add nativepython symlink
      createrepo: drop the usage of create_wrapper
      gnome-doc-utils: drop the usage of create_wrapper

 meta/recipes-devtools/dpkg/dpkg.inc                  |   10 +---------
 meta/recipes-devtools/python/python-native_2.7.3.bb  |    6 ++++++
 meta/recipes-gnome/gnome/gnome-doc-utils.inc         |    2 +-
 meta/recipes-support/createrepo/createrepo_0.4.11.bb |    2 +-
 4 files changed, 9 insertions(+), 11 deletions(-)

Ross Burton (4):
  dpkg: drop the usage of create_wrapper
  python-native: add nativepython symlink
  createrepo: drop the usage of create_wrapper
  gnome-doc-utils: drop the usage of create_wrapper

 meta/recipes-devtools/dpkg/dpkg.inc                  |   10 +---------
 meta/recipes-devtools/python/python-native_2.7.3.bb  |    6 ++++++
 meta/recipes-gnome/gnome/gnome-doc-utils.inc         |    2 +-
 meta/recipes-support/createrepo/createrepo_0.4.11.bb |    2 +-
 4 files changed, 9 insertions(+), 11 deletions(-)

-- 
1.7.10.4



             reply	other threads:[~2013-06-12 16:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-06-12 16:49 Ross Burton [this message]
2013-06-12 16:49 ` [PATCH 1/4] dpkg: drop the usage of create_wrapper Ross Burton
2013-06-12 16:49 ` [PATCH 2/4] python-native: add nativepython symlink Ross Burton
2013-06-12 16:49 ` [PATCH 3/4] createrepo: drop the usage of create_wrapper Ross Burton
2013-06-12 16:49 ` [PATCH 4/4] gnome-doc-utils: " Ross Burton

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=cover.1371055550.git.ross.burton@intel.com \
    --to=ross.burton@intel.com \
    --cc=openembedded-core@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.