All of lore.kernel.org
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: Phil Blundell <pb@pbcl.net>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: RSS difficulties
Date: Mon, 6 Feb 2017 12:54:37 -0800	[thread overview]
Message-ID: <CAMKF1sqKHdzCP3BW1AWZ+cVq+jhoL9=rTvnexKJz3bXyD59Ytw@mail.gmail.com> (raw)
In-Reply-To: <1486400123.22715.15.camel@pbcl.net>

On Mon, Feb 6, 2017 at 8:55 AM, Phil Blundell <pb@pbcl.net> wrote:
> On Mon, 2017-02-06 at 14:44 +0000, Phil Blundell wrote:
>
> But sadly the contents of libecj-bootstrap-native doesn't actually show up
> in gnujaf-native's recipe-sysroot-native.
>
>
> A bit of further sleuthing reveals that although this problem only started
> with rss the blame lies somewhere else. It transpires that meta-java's
> java-library.bbclass contains the somewhat epically unhelpful (in this
> context) fragment:
>
> # Java "source" distributions often contain precompiled things
> # we want to delete first.
> do_removebinaries() {
>   find ${WORKDIR} -name "*.jar" -exec rm {} \;
>   find ${WORKDIR} -name "*.class" -exec rm {} \;
> }
>
> addtask removebinaries after do_unpack before do_patch
>
> And, since recipe-sysroot-native is inside ${WORKDIR}, this blows away
> everything that rss carefully placed there. Doh.

good job. yeah this pre-rss assumptions, I also had another issue
where clang cross compiler was happily searching native sysroot for
headers. Not rss fault but exposed a latent problem.


      parent reply	other threads:[~2017-02-06 20:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-03 11:10 RSS difficulties Phil Blundell
2017-02-03 11:20 ` Richard Purdie
2017-02-03 12:29   ` Phil Blundell
2017-02-06 13:42     ` Phil Blundell
2017-02-06 14:27       ` Richard Purdie
2017-02-06 14:44         ` Phil Blundell
2017-02-06 16:30           ` Phil Blundell
2017-02-06 16:55           ` Phil Blundell
2017-02-06 17:05             ` Burton, Ross
2017-02-06 20:54             ` Khem Raj [this message]

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='CAMKF1sqKHdzCP3BW1AWZ+cVq+jhoL9=rTvnexKJz3bXyD59Ytw@mail.gmail.com' \
    --to=raj.khem@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=pb@pbcl.net \
    /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.