Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] staging: fix logic of guessing dependency manifest file in extend_recipe_sysroot
Date: Tue, 24 Jan 2017 22:08:47 +0000	[thread overview]
Message-ID: <1485295727.30673.69.camel@linuxfoundation.org> (raw)
In-Reply-To: <5ac6e942-a4af-b333-b8f2-45655548915d@gmail.com>

On Tue, 2017-01-24 at 14:05 -0800, Khem Raj wrote:
> 
> On 1/24/17 5:50 AM, Maciej Borzecki wrote:
> > 
> > Recipe sysroots introduced a change where dependencies ending with
> > "-cross" also
> > count as native tools and (see setscene_depvalid() for details).
> > 
> > The same logic was missing from extend_recipe_sysroot(), hence for
> > depency named
> > `go-cross` the manifest file would default to
> > `manifest-allarch-go-cross.populate_sysroot`, while the correct
> > name is
> > `manifest-x86_64_arm-go-cross.populate_sysroot`
> > 
> > Signed-off-by: Maciej Borzecki <maciej.borzecki@rndity.com>
> > ---
> >  meta/classes/staging.bbclass | 2 +-
> >  1 file changed, 1 insertion(+), 1 deletion(-)
> > 
> > diff --git a/meta/classes/staging.bbclass
> > b/meta/classes/staging.bbclass
> > index
> > fc387eaf4bb52971e111ae7deac7d7d6fc389337..efea450e4f73661366d0929d5
> > c39e42bfe9f8e8b 100644
> > --- a/meta/classes/staging.bbclass
> > +++ b/meta/classes/staging.bbclass
> > @@ -521,7 +521,7 @@ python extend_recipe_sysroot() {
> >              native = True
> >          elif c.startswith("nativesdk-"):
> >              manifest = d2.expand("${SSTATE_MANIFESTS}/manifest-
> > ${SDK_ARCH}_${SDK_OS}-%s.populate_sysroot" % c)
> > -        elif "-cross-" in c:
> > +        elif "-cross-" in c or c.endswith("-cross"):
> Perhaps you can change the go cross recipe to use something like
> 
> PN = "go-cross-${TARGET_ARCH}"
> 
> > 
> >              manifest = d2.expand("${SSTATE_MANIFESTS}/manifest-
> > ${BUILD_ARCH}_${TARGET_ARCH}-%s.populate_sysroot" % c)
> >              native = True
> >          elif "-crosssdk" in c:
> > 

FWIW the patch as it stands is going to cause problems since for
example qemuwrapper-cross doesn't inherit cross.bbclass (nor should it)
and will fail the manifest tests if we change it to include *-cross :(

Cheers,

Richard



  reply	other threads:[~2017-01-24 22:08 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-24 13:50 [PATCH] staging: fix logic of guessing dependency manifest file in extend_recipe_sysroot Maciej Borzecki
2017-01-24 22:05 ` Khem Raj
2017-01-24 22:08   ` Richard Purdie [this message]
2017-01-24 22:14     ` Maciej Borzęcki

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=1485295727.30673.69.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=raj.khem@gmail.com \
    /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