> On Jun 1, 2015, at 7:48 AM, Joel (Xi Zhou) Zhou <joel.z...@broadcom.com> > wrote: > > Hi all, > > I need to create multiple recipes for different kernel config based on the > same kernel source. > In my experiment, I create a new recipe linux-brcm-nand based on linux-brcm, > the only different is the kernel defconfig file. > From the following error message, it looks like the idea of multi-kernel > providers. > > What is the correct way to different kernel config on the same kernel source?
look at multi-kernel options e.g. https://github.com/Angstrom-distribution/meta-ti/blob/master/recipes-kernel/linux/multi-kernel.inc <https://github.com/Angstrom-distribution/meta-ti/blob/master/recipes-kernel/linux/multi-kernel.inc> that might help here. > > Thanks, > Joel > ---------------------------------- > ERROR: The recipe linux-brcm-nand is trying to install files into a shared > area when those files already exist. Those files and their manifest location > are: > /projects/poky/build64/tmp/sysroots/brcm/pkgdata/runtime/kernel > Matched in manifest-brcm-linux-brcm.packagedata > /projects/poky/build64/tmp/sysroots/brcm/pkgdata/runtime/kernel.packaged > Matched in manifest-brcm-linux-brcm.packagedata > ... > /projects/poky/build64/tmp/sysroots/brcm/pkgdata/kernel-depmod/System.map-3.14.29 > Matched in manifest-brcm-linux-brcm.packagedata > Please verify which recipe should provide the above files. > The build has stopped as continuing in this scenario WILL break things, if > not now, possibly in the future (we've seen builds fail several months > later). If the system knew how to recover from this automatically it would > however there are several different scenarios which can result in this and we > don't know which one this is. It may be you have switched providers of > something like virtual/kernel (e.g. from linux-yocto to linux-yocto-dev), in > that case you need to execute the clean task for both recipes and it will > resolve this error. It may be you changed DISTRO_FEATURES from systemd to > udev or vice versa. Cleaning those recipes should again resolve this error > however switching DISTRO_FEATURES on an existing build directory is not > supported, you should really clean out tmp and rebuild (reusing sstate should > be safe). It could be the overlapping files detected are harmless in which > case adding them to SSTATE_DUPWHITELIST may be the correct solution. It could > also be your build is including two different conflicting versions of things > (e.g. bluez 4 and bluez 5 and the correct solution for that would be to > resolve the conflict. If in doubt, please ask on the mailing list, sharing > the error and filelist above. > ERROR: If the above message is too much, the simpler version is you're > advised to wipe out tmp and rebuild (reusing sstate is fine). That will > likely fix things in most (but not all) cases. > ERROR: Function failed: sstate_task_postfunc > ERROR: Logfile of failure stored in: /projects/poky/build64/tmp/work/brcm > -poky-linux/linux-brcm-nand/3.14.29-r6/temp/log.do_packagedata.40045 > NOTE: recipe linux-brcm-nand-3.14.29-r6: task do_packagedata: Failed > ERROR: Task 11 > (/projects/poky/build64../meta-brcm/meta/recipes-kernel/linux/linux-brcm-nand_3.14.29.bb, > do_packagedata) failed with exit code '1' > NOTE: Tasks Summary: Attempted 447 tasks of which 445 didn't need to be rerun > and 2 failed. > -- > _______________________________________________ > yocto mailing list > yocto@yoctoproject.org <mailto:yocto@yoctoproject.org> > https://lists.yoctoproject.org/listinfo/yocto > <https://lists.yoctoproject.org/listinfo/yocto>
signature.asc
Description: Message signed with OpenPGP using GPGMail
-- _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
