Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Phil Blundell <pb@pbcl.net>
To: Richard Purdie <richard.purdie@linuxfoundation.org>,
	 openembedded-core@lists.openembedded.org
Subject: Re: RSS difficulties
Date: Mon, 06 Feb 2017 14:44:41 +0000	[thread overview]
Message-ID: <1486392281.22715.7.camel@pbcl.net> (raw)
In-Reply-To: <1486391230.14144.82.camel@linuxfoundation.org>

[-- Attachment #1: Type: text/plain, Size: 826 bytes --]

On Mon, 2017-02-06 at 14:27 +0000, Richard Purdie wrote:
> What happens if you set DEPENDS?

With DEPENDS I do at least get some entries for ecj-bootstrap-native in
task-depends.dot.  The relevant ones seem to be:

"gnujaf-native.do_prepare_recipe_sysroot" -> "ecj-bootstrap-
native.do_populate_sysroot"
"ecj-bootstrap-native.do_prepare_recipe_sysroot" -> "libecj-bootstrap-
native.do_populate_sysroot"

which looks fairly encouraging.  And in log.do_prepare_recipe_sysroot I
see:

Considering setscene task: ['libecj-bootstrap-native',
'do_populate_sysroot']
  considering dependency: ['ecj-bootstrap-native',
'do_populate_sysroot']
Adding dependency on libecj-bootstrap-native

But sadly the contents of libecj-bootstrap-native doesn't actually show
up in gnujaf-native's recipe-sysroot-native.

p.

[-- Attachment #2: Type: text/html, Size: 1106 bytes --]

  reply	other threads:[~2017-02-06 14:44 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 [this message]
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

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=1486392281.22715.7.camel@pbcl.net \
    --to=pb@pbcl.net \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.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