From: Jianxun Zhang <jianxun.zhang@linux.intel.com>
To: Saul Wold <sgw@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] qemu: fix: cp command cannot find tests/Makeflie
Date: Thu, 8 Sep 2016 15:40:34 -0700 [thread overview]
Message-ID: <1D92F6AA-3031-4AF8-BD6B-15DC2B28543D@linux.intel.com> (raw)
In-Reply-To: <1473362414-29683-1-git-send-email-sgw@linux.intel.com>
Note the patch is based on 958c05b on master-next branch in poky.
Thanks
> On Sep 8, 2016, at 12:20 PM, Saul Wold <sgw@linux.intel.com> wrote:
>
> From: Jianxun Zhang <jianxun.zhang@linux.intel.com>
>
> bitbake qemu
>
> This error shows up:
>
> ERROR: qemu-2.7.0-r1 do_install_ptest_base: Function failed:
> do_install_ptest_base
> ...
> cp: cannot stat '...tmp/work/core2-64-poky-linux/qemu/2.7.0-r1
> /qemu-2.7.0/tests/Makefile: No such file or directory
> ...
>
> Commit 46e7b70699d8bf4db08c8bb5111974318dd5416d in qemu project
> renamed tests/Makefile to tests/Makefile.include, we apply the
> same change in recipe accordingly to fix this issue.
>
> Fixes [YOCTO #10245]
> ---
> meta/recipes-devtools/qemu/qemu.inc | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/meta/recipes-devtools/qemu/qemu.inc b/meta/recipes-devtools/qemu/qemu.inc
> index d724aa4..b46e7f7 100644
> --- a/meta/recipes-devtools/qemu/qemu.inc
> +++ b/meta/recipes-devtools/qemu/qemu.inc
> @@ -76,7 +76,7 @@ do_install_ptest() {
> cp -rL ${B}/tests ${D}${PTEST_PATH}
> find ${D}${PTEST_PATH}/tests -type f -name "*.[Sshcod]" | xargs -i rm -rf {}
>
> - cp ${S}/tests/Makefile ${D}${PTEST_PATH}/tests
> + cp ${S}/tests/Makefile.include ${D}${PTEST_PATH}/tests
> }
>
> do_install () {
> --
> 2.7.4
>
prev parent reply other threads:[~2016-09-08 22:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-08 19:20 [PATCH] qemu: fix: cp command cannot find tests/Makeflie Saul Wold
2016-09-08 22:40 ` Jianxun Zhang [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=1D92F6AA-3031-4AF8-BD6B-15DC2B28543D@linux.intel.com \
--to=jianxun.zhang@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=sgw@linux.intel.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