From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: "Bodke, Kishore K" <kishore.k.bodke@intel.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>,
"Hart, Darren" <darren.hart@intel.com>
Subject: Re: Linux RT build fail
Date: Mon, 16 Jan 2012 13:44:22 -0500 [thread overview]
Message-ID: <4F147006.1070401@windriver.com> (raw)
In-Reply-To: <D956029D25CF204F948EA0FB515E1EE2030A3D@ORSMSX105.amr.corp.intel.com>
On 12-01-16 01:40 PM, Bodke, Kishore K wrote:
> Hi,
>
> I get build failure for the rt.
>
> ERROR: Function 'do_patch' failed (see
> /usr/local/src/jan13/poky/build-rt/tmp/work/cedartrail-poky-linux/linux-yocto-rt-3.0.14+git1+6ae3d992cf546184010e87a0349810198f1d167c_1+bcf4107c7f22d10952618a2ad146e6149d240cd2-r1/temp/log.do_patch.32459
> for further information)
>
> ERROR: Logfile of failure stored in:
> /usr/local/src/jan13/poky/build-rt/tmp/work/cedartrail-poky-linux/linux-yocto-rt-3.0.14+git1+6ae3d992cf546184010e87a0349810198f1d167c_1+bcf4107c7f22d10952618a2ad146e6149d240cd2-r1/temp/log.do_patch.32459
>
> Log data follows:
>
> | ERROR: Function 'do_patch' failed (see
> /usr/local/src/jan13/poky/build-rt/tmp/work/cedartrail-poky-linux/linux-yocto-rt-3.0.14+git1+6ae3d992cf546184010e87a0349810198f1d167c_1+bcf4107c7f22d10952618a2ad146e6149d240cd2-r1/temp/log.do_patch.32459
> for further information)
>
> | Deleted branch meta-temp (was 620917d).
>
> |
>
> | ERROR: patch
> /usr/local/src/jan13/poky/build-rt/tmp/work/cedartrail-poky-linux/linux-yocto-rt-3.0.14+git1+6ae3d992cf546184010e87a0349810198f1d167c_1+bcf4107c7f22d10952618a2ad146e6149d240cd2-r1/linux/meta/cfg/kernel-cache/features/rt/rt-apply-patch-3.0.10-rt27.patch.patch
> is not available
This is the problem. But I could have sworn that I fixed this, and
send a merge request. When I just checked now, it still looks broken.
That being said, we should have seen this before now. Are any -rt
kernels being build regularly on master ?
It is partially due to meta-kernel-dev picking up new kernel tools that
do strict checking on patches by default (hence my question about
anyone else building this on master).
I'm pushing a fix out now to the meta branch and will send it along
with my next consolidated pull request.
Cheers,
Bruce
>
> |
>
> | ERROR. Could not find an excutable target for
> yocto/standard/preempt-rt/base
>
> | ERROR. Could not locate meta series for preempt-rt-standard
>
> | ERROR. Could not modify yocto/standard/preempt-rt/base
>
> NOTE: package
> linux-yocto-rt-3.0.14+git1+6ae3d992cf546184010e87a0349810198f1d167c_1+bcf4107c7f22d10952618a2ad146e6149d240cd2-r1:
> task do_patch: Failed
>
> NOTE: package bzip2-1.0.6-r4: task do_compile: Succeeded
>
> ERROR: Task 3
> (/usr/local/src/jan13/poky/meta/recipes-kernel/linux/linux-yocto-rt_3.0.bb,
> do_patch) failed with exit code '1'
>
> Is this anything to do with meta-kernel-dev I am using or something else?
>
> Thanks
>
> Kishore.
>
next prev parent reply other threads:[~2012-01-16 18:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-16 18:40 Linux RT build fail Bodke, Kishore K
2012-01-16 18:44 ` Bruce Ashfield [this message]
2012-01-16 19:13 ` Darren Hart
2012-01-16 23:35 ` Bodke, Kishore K
2012-01-23 17:51 ` Bodke, Kishore K
2012-01-23 18:06 ` Bruce Ashfield
2012-01-24 1:17 ` Bodke, Kishore K
2012-01-24 6:22 ` Bruce Ashfield
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=4F147006.1070401@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=darren.hart@intel.com \
--cc=kishore.k.bodke@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.