From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Robert Yang <liezhi.yang@windriver.com>,
openembedded-core@lists.openembedded.org
Cc: "Bartosh, Eduard" <eduard.bartosh@intel.com>
Subject: Re: [PATCH 7/8] qemuboot.bbclass: add two vars for use by runqemu
Date: Mon, 10 Apr 2017 17:53:54 +0100 [thread overview]
Message-ID: <1491843234.783.2.camel@linuxfoundation.org> (raw)
In-Reply-To: <af3b44b2cc2be0771d70599286fa55d6ec3629bf.1491557671.git.liezhi.yang@windriver.com>
On Fri, 2017-04-07 at 02:47 -0700, Robert Yang wrote:
> From: Chen Qi <Qi.Chen@windriver.com>
>
> Add STAGING_DIR_TUNCTL_NATIVE and STAGING_DIR_QEMU_BINDIR_NATIVE so
> that
> runqemu could find 'tunctl' and 'qemu-xxx' binaries to run correctly.
>
> [YOCTO #11266]
> [YOCTO #11193]
>
> Signed-off-by: Chen Qi <Qi.Chen@windriver.com>
Hi Robert/Qi,
Unfortunately this can't work as we can't use binaries directly from
the sysroot-components directory if they link to any libraries. tunctl
is ok but qemu links against libfdt.so.1 which isn't there. If the
system has its own copy, it may happen to work by luck but if it
doesn't, or the system version is incompatible we'd see failures.
So I'm afraid we need to find a different solution.
Cheers,
Richard
> meta/classes/qemuboot.bbclass | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/meta/classes/qemuboot.bbclass
> b/meta/classes/qemuboot.bbclass
> index 2870388dfb..ac52ef295e 100644
> --- a/meta/classes/qemuboot.bbclass
> +++ b/meta/classes/qemuboot.bbclass
> @@ -70,12 +70,15 @@ QB_DRIVE_TYPE ?= "/dev/sd"
> # Create qemuboot.conf
> addtask do_write_qemuboot_conf after do_rootfs before do_image
> IMGDEPLOYDIR ?= "${WORKDIR}/deploy-${PN}-image-complete"
> +STAGING_DIR_TUNCTL_NATIVE = "${STAGING_DIR}-
> components/${BUILD_ARCH}/qemu-helper-native"
> +STAGING_DIR_QEMU_BINDIR_NATIVE = "${STAGING_DIR}-
> components/${BUILD_ARCH}/qemu-native/usr/bin"
>
> def qemuboot_vars(d):
> build_vars = ['MACHINE', 'TUNE_ARCH', 'DEPLOY_DIR_IMAGE',
> 'KERNEL_IMAGETYPE', 'IMAGE_NAME', 'IMAGE_LINK_NAME',
> 'STAGING_DIR_NATIVE', 'STAGING_BINDIR_NATIVE',
> - 'STAGING_DIR_HOST']
> + 'STAGING_DIR_HOST', 'STAGING_DIR_TUNCTL_NATIVE',
> + 'STAGING_DIR_QEMU_BINDIR_NATIVE']
> return build_vars + [k for k in d.keys() if k.startswith('QB_')]
>
> do_write_qemuboot_conf[vardeps] += "${@' '.join(qemuboot_vars(d))}"
> --
> 2.11.0.rc2.dirty
>
next prev parent reply other threads:[~2017-04-10 17:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-07 9:47 [PATCH 0/8 V2] fixes for runqemu and runqemu + rm_work Robert Yang
2017-04-07 9:47 ` [PATCH 1/8] runqemu: fix 2 typos Robert Yang
2017-04-07 9:47 ` [PATCH 2/8] runqemu: support env vars explicitly Robert Yang
2017-04-07 9:47 ` [PATCH 3/8] runqemu: use self.rootfs to replace self.nfs_dir Robert Yang
2017-04-07 9:47 ` [PATCH 4/8] runqemu: run without arguments Robert Yang
2017-04-07 9:47 ` [PATCH 5/8] runqemu: use realpath for imgdir Robert Yang
2017-04-07 9:47 ` [PATCH 6/8] runqemu: do not rely on grepping images Robert Yang
2017-04-08 14:24 ` Richard Purdie
2017-04-11 2:21 ` Robert Yang
2017-04-07 9:47 ` [PATCH 7/8] qemuboot.bbclass: add two vars for use by runqemu Robert Yang
2017-04-10 16:53 ` Richard Purdie [this message]
2017-04-11 2:29 ` ChenQi
2017-04-07 9:47 ` [PATCH 8/8] runqemu: make use of two new vars Robert Yang
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=1491843234.783.2.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=eduard.bartosh@intel.com \
--cc=liezhi.yang@windriver.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox