Openembedded Core Discussions
 help / color / mirror / Atom feed
From: richard.purdie@linuxfoundation.org
To: Andrej Valek <andrej.valek@siemens.com>, Khem Raj <raj.khem@gmail.com>
Cc: "bluehills7@comcast.net" <bluehills7@comcast.net>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: SDK and out of tree modules
Date: Wed, 26 Sep 2018 13:27:51 +0100	[thread overview]
Message-ID: <2a024a84749d6b6a838c92efad8a2ddf7f262dbe.camel@linuxfoundation.org> (raw)
In-Reply-To: <7f369514-092a-6a76-0262-ac9a84309b10@siemens.com>

On Wed, 2018-09-26 at 14:22 +0200, Andrej Valek wrote:
> Hello Richard,
> 
> I am working on derivate of pyro branch.
> So I have setup new machine based on master (without my
> modifications),
> but the problem is still there.
> 
> What I have made:
> IMAGE_INSTALL += "kernel-devsrc"
> 
> core-image-minimal -c populate_sdk_ext
> 
> Now the manifests in directory have different names:
> $ find . -name "*kernel*"
> ./manifest-qemuarm-kernel-devsrc.populate_lic
> ./manifest-qemuarm-kernel-devsrc.package
> ./manifest-qemuarm-kernel-devsrc.packagedata
> ./manifest-qemuarm-kernel-devsrc.package_write_rpm
> ./manifest-qemuarm-kernel-devsrc.package_qa
> 
> So now allarch has been replaced by qemuarm. Seems to be, that
> something
> has been changed in PKG_ARCH.
> 
> But warnings are still the same:
> WARNING: core-image-minimal-1.0-r0 do_sdk_depends: Manifest
> build/tmp/sstate-control/manifest-x86_64_x86_64-nativesdk-kernel-
> devsrc.populate_sysroot
> not found in qemuarm armv5te armv5e armv5t armv5 armv4t armv4 arm
> allarch x86_64_x86_64-nativesdk (variant '')?
> WARNING: core-image-minimal-1.0-r0 do_populate_sdk_ext: Manifest
> build/tmp/sstate-control/manifest-x86_64_x86_64-nativesdk-kernel-
> devsrc.populate_sysroot
> not found in qemuarm armv5te armv5e armv5t armv5 armv4t armv4 arm
> allarch x86_64_x86_64-nativesdk (variant '')?
>
> But why is trying to find nativesdk manifests instead of qemuarm? 

It will search all the PACKAGE_ARCHS variants in order.

> Isn't it caused by IMAGE_INSTALL in populate task?
> Anyway, the problem is the same. Still couldn't find the
> .populate_sysroot manifest file due to mentioned [noxec].

I've given this a fair bit of thought. Could you try replacing the
[noexec] with:

deltask do_populate_sysroot
deltask do_populate_sysroot_setscene

I think thay may be the right fix. Whether it causes other issues,
we'll see...

Cheers,

Richard




  reply	other threads:[~2018-09-26 12:27 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-25 14:51 SDK and out of tree modules Andrej Valek
2018-09-25 15:22 ` richard.purdie
2018-09-26 12:22   ` Andrej Valek
2018-09-26 12:27     ` richard.purdie [this message]
2018-09-26 13:28     ` [PATCH 0/1] kernel-devsrc: fix searching for non-existing Andrej Valek
2018-09-26 13:28     ` [PATCH 1/1] kernel-devsrc: fix searching for non-existing manifest files Andrej Valek
2018-09-26 15:54       ` Khem Raj
2018-09-26 22:30       ` Richard Purdie
2018-09-26 23:12         ` Richard Purdie
2018-09-26 23:52           ` Khem Raj
2018-09-27  5:55             ` Andrej Valek

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=2a024a84749d6b6a838c92efad8a2ddf7f262dbe.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=andrej.valek@siemens.com \
    --cc=bluehills7@comcast.net \
    --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