This is a good point. In looking at the example it does not say what branch you should be dealing with for poky-extras.
-----Original Message----- From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com] Sent: Tuesday, June 26, 2012 9:24 AM To: jfabernathy Cc: Rifenbark, Scott M; yocto@yoctoproject.org Subject: Re: [yocto] Yocto Development Manual Appendix B question On 12-06-26 12:11 PM, jfabernathy wrote: > On 06/26/2012 12:04 PM, Bruce Ashfield wrote: >> On 12-06-26 12:00 PM, jfabernathy wrote: >>> On 06/26/2012 10:56 AM, Rifenbark, Scott M wrote: >>>> Bruce, >>>> >>>> Should the example note this? Would it be best to specifically say to >>>> uncomment that SRC_URI line? >>>> >>>> Scott >>> I think some text needs to be added. I uncommented the SRC_URI line and >>> I still fail building the image. The failure is related to kernel tools: >>> >>> ERROR: kern-tools-native: md5 data is not matching for >>> file://git/tools/kgit;beginline=5;endline=9;md5=e2bf4415f3d843f43d2e22b0d91a6fee >>> >>> >>> ERROR: kern-tools-native: The new md5 checksum is >>> d8d1d729a70cd5f52972f8884b80743d >>> ERROR: kern-tools-native: Check if the license information has >>> changed in >>> ERROR: Licensing Error: LIC_FILES_CHKSUM does not match, please fix >>> ERROR: Function failed: do_qa_configure >> >> This one is actually fixed on master, but poky-extras .. is just that >> 'extra', so this may still be alive in that repo. >> >> This wouldn't need to be documented, since it's a bug/issue, and not >> something that would persist. >> >> What release are you pairing poky extras with ? I can always create a >> branch to make sure they are consistent. >> > > I was using Denzil because the snapshot noted in the example does not > exist. So there is another doc issue. Aha. In this case, we could note that the poky-extras repo branch should match the main repository branch .. and I could ensure that meta-kernel-dev works in that configuration. That's likely the right solution, rather than forcing you to switch to master (unless you want to :) Cheers, Bruce > > I can always test on Master, but the docs need to be update to reflect > something that will work to completion without errors, IMHO. > > Jim A > >> Cheers, >> >> Bruce >> >>> >>> >>> Jim A >>> >>>> -----Original Message----- >>>> From: yocto-boun...@yoctoproject.org >>>> [mailto:yocto-boun...@yoctoproject.org] On Behalf Of Bruce Ashfield >>>> Sent: Tuesday, June 26, 2012 7:54 AM >>>> To: jfabernathy >>>> Cc: yocto@yoctoproject.org >>>> Subject: Re: [yocto] Yocto Development Manual Appendix B question >>>> >>>> On 12-06-26 10:52 AM, jfabernathy wrote: >>>>> In the example in The Developement Manual v1.2 in Appendix B Section >>>>> B.1.7, it states that you need to put in the statement: >>>>> >>>>> KSRC_linux_yocto_3_2 ?="/home/scottrif/linux-yocto-3.2.git" >>>>> >>>>> into the appropriate .bbappend file way now in the poky-extra >>>>> directory >>>>> structure. If I look at that file, |linux-yocto_3.2.bbappend| , I >>>>> seen a >>>>> SRC_URI line, immediately after our inserted KSRC statement, that is >>>>> commented out: >>>>> >>>>> # SRC_URI = >>>>> "git://${KSRC_linux_yocto_3_2};protocol=file;nocheckout=1;branch=${KBRANCH},meta;name=machine,meta" >>>>> >>>>> >>>>> >>>>> Should that line be uncommented or is the SRC_URI already defaulted >>>>> somewhere to use the newly defined KSRC_linux_yocto_3_2 variable? >>>> It should be uncommented. I commented them by default, since the extras >>>> repository is a bit of a collection ground. If they are uncommented, >>>> and >>>> combined with the AUTOREV also set in the file, you are forced to fix >>>> all files, versus just the one you want. >>>> >>>> Cheers, >>>> >>>> Bruce >>>> >>>>> Jim A >>>>> >>>>> >>>>> >>>>> >>>>> >>>>> _______________________________________________ >>>>> yocto mailing list >>>>> yocto@yoctoproject.org >>>>> https://lists.yoctoproject.org/listinfo/yocto >>>> _______________________________________________ >>>> yocto mailing list >>>> yocto@yoctoproject.org >>>> https://lists.yoctoproject.org/listinfo/yocto >>> >>> >> > > _______________________________________________ yocto mailing list yocto@yoctoproject.org https://lists.yoctoproject.org/listinfo/yocto
