What's your build OS On Sun, Apr 16, 2017 at 6:09 PM Paul D. DeRocco wrote: > I'm trying to migrate an Atom-based build from Fido to Morty, and also > switch from 32-bit mode to x32. On a clean build, it gets about half way > through, and then suddenly coughs up a patch error. I've put blank lines > between the log lines so that the email word wrap won't be as confusing: > > -- > > DEBUG: Executing shell function do_patch > > (1/660) ARM-LPAE-Invalidate-the-TLB-for-module-addresses-dur.patch > > [INFO]: check of > .kernel-meta//patches//arch/arm/v7-A15/ARM-LPAE-Invalidate-the-TLB-for-mod > ule-addresses-dur.patch with "git am" did not pass, trying reduced > context. > > [INFO]: Context reduced git-am of > .kernel-meta//patches//arch/arm/v7-A15/ARM-LPAE-Invalidate-the-TLB-for-mod > ule-addresses-dur.patch with "git am" did not work, trying "apply". > > error: patch failed: arch/arm/mm/fault.c:448 > > error: arch/arm/mm/fault.c: patch does not apply > > [ERROR]: Application of > .kernel-meta//patches//arch/arm/v7-A15/ARM-LPAE-Invalidate- > the-TLB-for-module-addresses-dur.patch failed. > > Patch needs to be refreshed. Sample resolution script: > > .git/rebase-apply/resolve_rejects > > WARNING: > /home/pauld/yocto-morty/build/tmp/work/chroma_bsp-poky-linux-gnux32/linux- > yocto-rt/4.8.12+gitAUTOINC+926c93ae07_3bafd55e39-r0/temp/run.do_patch.3069 > 0:1 exit 1 from 'kgit-s2q --gen -v --patches .kernel-meta/' > > ERROR: Function failed: do_patch (log file is located at > /home/pauld/yocto-morty/build/tmp/work/chroma_bsp-poky-linux-gnux32/linux- > yocto-rt/4.8.12+gitAUTOINC+926c93ae07_3bafd55e39-r0/temp/log.do_patch.3069 > 0) > > -- > > If I start bitbake again, it detects a "fence", and proceeds a little > further. I can do it over and over again, and it keeps building more and > more, but this can't be right, can it? The strange thing is that the > patches are all about ARM, PowerPC, etc., which have nothing to do with my > system. Could this be some fundamental misconfiguration having to do with > my MACHINE? At the beginning of my local.conf, I have: > > MACHINE ?= "chroma-bsp" > DEFAULTTUNE = "core2-64-x32" > baselib = "libx32" > > where chroma-bsp is defined in my own layer. My chroma-bsp.conf file > contains (among other things): > > PREFERRED_PROVIDER_virtual/kernel ?= "linux-yocto-rt" > PREFERRED_VERSION_linux-yocto-rt ?= "4.8%" > require conf/machine/include/tune-atom.inc > require conf/machine/include/x86-base.inc > > I'm not really good at this. Does anyone see anything wrong? > > -- > > Ciao, Paul D. DeRocco > Paul mailto:pderocco@ix.netcom.com > > -- > _______________________________________________ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto >