[OE-core] linux-yocto-custom. error in patch step

Bruce Ashfield bruce.ashfield at gmail.com
Mon Apr 15 19:19:37 UTC 2013


On Mon, Apr 15, 2013 at 2:55 PM, Anders Darander <anders at chargestorm.se> wrote:
> I
>
> Bruce Ashfield <bruce.ashfield at gmail.com> wrote:
>
>>On Mon, Apr 15, 2013 at 2:15 PM, Bruce Ashfield
>><bruce.ashfield at gmail.com> wrote:
>>> On Mon, Apr 15, 2013 at 2:07 PM, Anders Darander
>><anders at chargestorm.se> wrote:
>
>>/home/anders/poky/build/tmp/work/qemuarm-poky-linux-gnueabi/linux-yocto-custom/3.8+gitAUTOINC+19f949f52599ba7c3f67a5897ac6be14bfcb1200-r1/temp/log.do_patch.8972
>>>> Log data follows:
>>>> | DEBUG: Executing shell function do_patch
>>>> | WARNING: no meta data branch found ...
>>>> | Already on 'master'
>>>> | Your branch is behind 'origin/master' by 12742 commits, and can be
>>>> fast-forwarded.
>>>> | ERROR. input file "meta/cfg/scratch/obj/qemuarm-standard.scc" does
>>not
>>>> exist
>>>> | ERROR. A meta series could not be created for
>>>> meta/cfg/scratch/obj/qemuarm-standard.scc
>>>> | ERROR. Could not locate meta series for qemuarm
>>>> | ERROR. Could not apply patches for qemuarm.
>>>> |        Patch failures can be resolved in the devshell (bitbake -c
>>>> devshell linux-yocto-custom)
>>>> | ERROR: Function failed: do_patch (see
>>>>
>>/home/anders/poky/build/tmp/work/qemuarm-poky-linux-gnueabi/linux-yocto-custom/3.8+gitAUTOINC+19f949f52599ba7c3f67a5897ac6be14bfcb1200-r1/temp/log.do_patch.8972
>>>> for further information)
>>>> ERROR: Task 3
>>>>
>>(/home/anders/poky/meta-skeleton/recipes-kernel/linux/linux-yocto-custom.bb,
>>>> do_patch) failed with exit code '1'
>>>>
>>>>
>>>> Using my own machine, I got a similar error, that
>>>> ${MACHINE}-standard.scc didn't exist.
>>>>
>>>> The plan is to use a defconfig as the main configuration, and
>>possibly
>>>> later on add config fragments for certain featuers.
>>>>
>>>> However, I'm missing one step, as I'm not able to build without the
>>>> meta/cfg/scratch/obj/qemuarm-standard.scc file.
>>>>
>>>> Any hints on what step I've currently overlooked would be nice...
>>>
>>> Let me have a look at this, there were some changes to the tools for
>>> 1.4, so the
>>> examples may need some tweaking.
>>>
>>> We did run all the yocto-bsp tools against 1.4 and they worked, and
>>they are
>>> users of the same interface.
>>>
>>> Anyway, if there's a bug, I'll follow up with a patch shortly.
>>
>>Indeed, something managed to happen here. I'm investigating and will
>>follow
>>up once I know what broke.
>
> Thanks!
> Good that the issue was found prior to the release. Looking forward to see what it was all about.
>
> I was slightly worried for a while, when I couldn't find the best problem in my recipe, as something similar had been working on the 1.3 release.

This is fixed here. One line fix (smaller than that actually) .. isn't
that always the
way.

I'll be sending RP a fix for it shortly. Thanks for the report!

Bruce

>
> Cheers,
> Anders
> --
> Anders Darander
> ChargeStorm AB          Tel: +46 702 44 84 36
> Laxholmstorget 3        Email: anders at chargestorm.se
> 602 21 Norrköping       Web: www.chargestorm.se
>
> Sent from my Android phone with K-9 Mail. Please excuse my brevity.



--
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"




More information about the Openembedded-core mailing list