PS: I just notice now that I have meta-python duplicated at bblayers.conf, 2017-12-14 0:27 GMT-02:00 Daniel. <danielhi...@gmail.com>:
> Okay, sorry for the late reply! > > I could reproduce the same error again, I just cleanall and then build > linux-raspberrypi again. Let's go to the logs: > > The whole output: https://pastebin.com/zHLpPf5V > My config: https://pastebin.com/mKJb2tyJ > Configured layers: https://pastebin.com/7UakkhHJ > https://pastebin.com/xKRd8rDr > The layers commits: https://pastebin.com/9pJCrdh4 > > I'll let it stay in this state, so if you need any other information just > let me know and I gather it for you. Again, I'm on fedora 27, kernel > 4.14.3-300.fc27.x86_64, i3, 8GB ram. I think this is it. > > Regards! > > > 2017-12-11 9:34 GMT-02:00 Daniel. <danielhi...@gmail.com>: > >> I can anticipate some info for you. I'm on version 2.4 Rocko. Building >> rpi-hwup-image for MACHINE=rasbiberrypi3-64. Also is worth noting that I'm >> running Fedora 27 which wasn't tested... >> >> I'll try to get the full log tonight and let you know >> >> Regards >> >> On Dec 11, 2017 9:26 AM, "Daniel." <danielhi...@gmail.com> wrote: >> >>> Yeah but I got to face the error again, maybe tonight when I get home :) >>> >>> On Dec 11, 2017 9:17 AM, "Paul Barker" <pbar...@toganlabs.com> wrote: >>> >>>> On Sun, Dec 10, 2017 at 5:14 PM, Daniel. <danielhi...@gmail.com> wrote: >>>> > Hi everybody, >>>> > >>>> > I'm building a vanilla image for MACHINE=raspberrypi3-64. I'm doing >>>> the >>>> > build for the first time and faced an error at >>>> > linux-raspberrypi:do_kernel_configme. I found that >>>> .kernel-meta/configs >>>> > folder was missing, so I fired a devshell and created it. After that >>>> > everything works as expected and linux-raspberrypi build fines. >>>> > >>>> > The solution I got is palliative, what would be the real solution and >>>> what >>>> > is this .kernel-meta folder? I had never seem this folder before. >>>> >>>> I have seen this issue occasionally when the do_kernel_configme task >>>> is re-executed. A "bitbake virtual/kernel -c clean" has always >>>> resolved this for me, allowing the next build to succeed. It doesn't >>>> occur on my autobuild systems though so I figure it's an edge case I'm >>>> hitting when building locally as I'm hacking around on recipes. >>>> >>>> I've never seen this on the first build of the kernel though. >>>> >>>> Which version of Yocto are you using? Could you send us the build >>>> configuration summary and the full error messages printed by bitbake? >>>> >>>> Thanks, >>>> >>>> -- >>>> Paul Barker >>>> Togán Labs Ltd >>>> >>> > > > -- > “If you're going to try, go all the way. Otherwise, don't even start. ..." > Charles Bukowski > -- “If you're going to try, go all the way. Otherwise, don't even start. ..." Charles Bukowski
-- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto