All of lore.kernel.org
 help / color / mirror / Atom feed
From: brian avery <brian.avery@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/2] runqemu-extract-sdk: Fixes for RSS
Date: Tue,  4 Apr 2017 15:22:09 -0700	[thread overview]
Message-ID: <cover.1491344268.git.brian.avery@intel.com> (raw)


RSS removed the "giant native sysroot" so now we need a modify how tools like runqemu and
runqemu-extract-sdk find the native tools they need to run.  This patch uses the result of
meta-ide-support which has pseudo as well as tools like unfsd in it's usr/bin to run.
Since the meta-ide-support make a usr/bin dir in tmp/work and rm_work sibsequently removes it,
we exlude meta-ide-support from the rm_work set.

-brian

The following changes since commit eff56e4f0d59b1d965a68e4f009b7f07717b7edd:

  bitbake: bitbake-user-manual: Fixed special character in -D output (2017-04-03 22:32:02 +0100)

are available in the git repository at:

  git://git.yoctoproject.org/poky-contrib bavery/sadpseudo/bug11119
  http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=bavery/sadpseudo/bug11119

brian avery (2):
  scripts: change way we find native tools (pseudo)
  meta-ide-support: exclude this recipe from rm_work

 meta/recipes-core/meta/meta-ide-support.bb | 1 +
 scripts/oe-find-native-sysroot             | 8 ++++----
 2 files changed, 5 insertions(+), 4 deletions(-)

--
1.9.1


             reply	other threads:[~2017-04-04 22:19 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-04 22:22 brian avery [this message]
2017-04-04 22:22 ` [PATCH 1/2] scripts: change way we find native tools (pseudo) brian avery
2017-04-04 22:33   ` Seebs
2017-04-06 10:26   ` Robert Yang
2017-04-07  2:48     ` Brian Avery
2017-04-07  3:18       ` Robert Yang
2017-04-04 22:22 ` [PATCH 2/2] meta-ide-support: exclude this recipe from rm_work brian avery

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.1491344268.git.brian.avery@intel.com \
    --to=brian.avery@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.