From: Neuer User <auslands-kv@gmx.de>
To: yocto@yoctoproject.org
Subject: Re: Kernel config fragments are not applied
Date: Thu, 01 May 2014 08:32:22 +0200 [thread overview]
Message-ID: <5361EA76.1080604@gmx.de> (raw)
In-Reply-To: <5361CDAE.8050206@windriver.com>
Hi Bruce
Here is the error messega, I get after a "bitbake linux-cubox-i -c
cleansstate; bitbake linux-cubox-i" using the recipe you posted:
ERROR: Function failed: do_patch (log file is located at
/home/ubuntu/yocto/build/tmp/work/cubox_i-poky-linux-gnueabi/linux-cubox-i/3.0.35-r0/temp/log.do_patch.5660)
ERROR: Logfile of failure stored in:
/home/ubuntu/yocto/build/tmp/work/cubox_i-poky-linux-gnueabi/linux-cubox-i/3.0.35-r0/temp/log.do_patch.5660
Log data follows:
| DEBUG: Executing shell function do_patch
| WARNING: no meta data branch found ...
| ls: cannot access .meta*: No such file or directory
| Already on 'imx_3.0.35_4.1.0'
| [INFO] validating against known patches (cubox-i-standard-meta)
error: patch failed: arch/arm/lib/memset.S:19#############] (/)(110 %)
| error: arch/arm/lib/memset.S: patch does not apply
| ERROR. could not update git tree
| ERROR. Could not apply patches for cubox-i.
| Patch failures can be resolved in the devshell (bitbake -c
devshell linux-cubox-i)
| WARNING: exit code 1 from a shell command.
| ERROR: Function failed: do_patch (log file is located at
/home/ubuntu/yocto/build/tmp/work/cubox_i-poky-linux-gnueabi/linux-cubox-i/3.0.35-r0/temp/log.do_patch.5660)
ERROR: Task 3
(/home/ubuntu/yocto/sources/meta-fsl-arm-extra/recipes-kernel/linux/linux-cubox-i_3.0.35.bb,
do_patch) failed with exit code '1'
Hope, it helps!
Michael
Am 01.05.2014 06:29, schrieb Bruce Ashfield:
> I'm glad that I looked again, I though there was an error without my
> clean up series .. but what I was seeing was a legitimate double
> application of the patch.
>
> What error where you seeing when you tried a bbappend like so:
>
> ------------
> FILESEXTRAPATHS_prepend := "${THISDIR}/${PN}-${PV}:"
>
> inherit kernel
> require recipes-kernel/linux/linux-yocto.inc
>
> COMPATIBLE_MACHINE_cubox-i = "(cubox-i)"
>
> SRC_URI += "file://videoin.cfg"
> --------------
>
> Your error message will set me straight .. and tell me if it is just
> the late night hacking fooling my eyes .. or not!
>
>
> Bruce
next prev parent reply other threads:[~2014-05-01 6:32 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-28 8:03 Kernel config fragments are not applied Neuer User
2014-04-28 13:03 ` Bruce Ashfield
2014-04-28 13:14 ` Neuer User
2014-04-28 13:16 ` Bruce Ashfield
2014-04-28 13:35 ` Neuer User
2014-04-28 13:37 ` Bruce Ashfield
2014-04-28 13:54 ` Neuer User
2014-04-30 18:44 ` Bruce Ashfield
2014-04-30 19:16 ` Neuer User
2014-04-30 19:21 ` Bruce Ashfield
2014-04-30 19:23 ` Neuer User
2014-04-30 21:08 ` Bruce Ashfield
2014-05-01 4:29 ` Bruce Ashfield
2014-05-01 6:32 ` Neuer User [this message]
2014-05-01 17:12 ` Bruce Ashfield
2014-05-02 17:24 ` Bruce Ashfield
2014-05-03 8:43 ` Neuer User
2014-04-30 10:24 ` Neuer User
2014-04-30 12:28 ` 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=5361EA76.1080604@gmx.de \
--to=auslands-kv@gmx.de \
--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.