From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Darren Hart <dvhart@linux.intel.com>
Cc: Yocto Project <yocto@yoctoproject.org>
Subject: Re: [PATCH][meta-kernel-dev] kern-tools: Include do_install() in bbappend
Date: Fri, 16 Dec 2011 21:55:31 -0500 [thread overview]
Message-ID: <4EEC04A3.4040305@windriver.com> (raw)
In-Reply-To: <ce764bbeb15baa4a42cd983807ea2fec6f8ac91e.1324085495.git.dvhart@linux.intel.com>
On 11-12-16 8:31 PM, Darren Hart wrote:
> do_install() has changed over versions of kern-tools, ensure this matches
> the latest sources as referenced by ${AUTOREV}. Without this, using
> this bbappend against older kern-tools recipes will fail in very strange
> and unexplainable ways. The edison recipe for example has:
>
> do_install() {
> install -d ${D}${bindir}
> for s in ${kern_tools_LIST}; do
> install -m 0755 ${S}/git/tools/$s ${D}${bindir}
> done
> }
We don't need this. As I mentioned in other email, meta-kernel-dev
works with master, not any particular branch.
Removing this bbappend is the right solution if you aren't on master.
Having this in the bbappend, simply means that when I change the install
next time .. this breaks again.
Bruce
>
> This resulted in do_kernel_configme failures:
>
> | mv: cannot stat `/usr/local/src/yocto_1_1/poky/build/tmp/work/crystalforest-poky-linux/linux-yocto-rt-3.0.4+git1+d05450e4aef02c1b7137398ab3a9f8f96da74f52_1+0936e13cc65d816f1759e2322c5e3fc82a5037f3-r1/linux-crystalforest-preempt-rt-build/.tmp.config*': No such file or directory
>
> Signed-off-by: Darren Hart<dvhart@linux.intel.com>
> CC: Kishore Bodke<kishore.k.bodke@intel.com>
> ---
> .../kern-tools-native_git.bbappend | 7 +++++++
> 1 files changed, 7 insertions(+), 0 deletions(-)
>
> diff --git a/meta-kernel-dev/recipes-kernel/kern-tools-native/kern-tools-native_git.bbappend b/meta-kernel-dev/recipes-kernel/kern-tools-native/kern-tools-native_git.bbappend
> index 201ec7f..445b385 100644
> --- a/meta-kernel-dev/recipes-kernel/kern-tools-native/kern-tools-native_git.bbappend
> +++ b/meta-kernel-dev/recipes-kernel/kern-tools-native/kern-tools-native_git.bbappend
> @@ -5,3 +5,10 @@ LOCALCOUNT = "0"
> # For local kern-tools work, fill in KERN_TOOLS_SRC and uncomment the SRC_URI
> # KERN_TOOLS_SRC ?= /path/to/local/kern-tools-clone
> # SRC_URI = "git://${KERN_TOOLS_SRC}"
> +
> +# This step has changed over versions of kern-tools, ensure this matches
> +# the latest sources as referenced by ${AUTOREV}
> +do_install() {
> + cd ${S}/git
> + make DESTDIR=${D}${bindir} install
> +}
prev parent reply other threads:[~2011-12-17 2:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-17 1:31 [PATCH][meta-kernel-dev] kern-tools: Include do_install() in bbappend Darren Hart
2011-12-17 2:55 ` Bruce Ashfield [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=4EEC04A3.4040305@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=dvhart@linux.intel.com \
--cc=yocto@yoctoproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.