From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-vb0-f48.google.com (mail-vb0-f48.google.com [209.85.212.48]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 8313EE0070C for ; Tue, 26 Jun 2012 13:40:05 -0700 (PDT) Received: by vbjk17 with SMTP id k17so308064vbj.35 for ; Tue, 26 Jun 2012 13:40:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=message-id:date:from:user-agent:mime-version:to:cc:subject :references:in-reply-to:content-type:content-transfer-encoding; bh=kkjpkqIRn29bOcCHEf5s5HCH2YVH0zTfpZG6gQTu/Xk=; b=rRod8wfBjTfFrjqf0KKSV9yLd+5mm4skb8iyJC4RZ3CnYppceViEf7keWSeNNapx1Y 1XNdyssFIqGEwsTEYBM3Ho1YupNUBadC7h7tHySVd5KLe0dIywigRCksZFHkLrep2/xi caE0LL0xAwc5djz74zu+K6QWwS5kmemL1/kZC2hWbbFHgHaV1rTXAFOZEP5r/1XVUVqJ 569HVOcvZIo7Szod638B4yyXgD81Y+MSSWUH/eK8dTwSWyf8sU33JPzypc+7qrpIwH2G RESpOKsX76aH3zaDwuPkTJCcnVtmmqZ5E1996T9E4vo8/2SQeF6zV2V2HEFcWWviUorB 6f2g== Received: by 10.220.152.138 with SMTP id g10mr12141240vcw.14.1340743204851; Tue, 26 Jun 2012 13:40:04 -0700 (PDT) Received: from [10.0.1.54] (nc-184-4-33-55.dhcp.embarqhsd.net. [184.4.33.55]) by mx.google.com with ESMTPS id i19sm56323179vdt.18.2012.06.26.13.40.03 (version=SSLv3 cipher=OTHER); Tue, 26 Jun 2012 13:40:04 -0700 (PDT) Message-ID: <4FEA1E25.9080103@gmail.com> Date: Tue, 26 Jun 2012 16:40:05 -0400 From: jfabernathy User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:13.0) Gecko/20120615 Thunderbird/13.0.1 MIME-Version: 1.0 To: "Rifenbark, Scott M" References: <4FE9CCAD.7080003@gmail.com> <4FE9CD04.60604@windriver.com> <41DEA4B02DBDEF40A0F3B6D0DDB1237946A130B2@ORSMSX101.amr.corp.intel.com> <4FE9DC9B.2090104@gmail.com> <4FE9DD7F.2090402@windriver.com> <4FE9DF3B.8010104@gmail.com> <4FE9E22E.8080305@windriver.com> <41DEA4B02DBDEF40A0F3B6D0DDB1237946A131AA@ORSMSX101.amr.corp.intel.com> <4FE9E30B.9080903@windriver.com> <41DEA4B02DBDEF40A0F3B6D0DDB1237946A131CC@ORSMSX101.amr.corp.intel.com> <4FE9F47F.80306@windriver.com> <41DEA4B02DBDEF40A0F3B6D0DDB1237946A13288@ORSMSX101.amr.corp.intel.com> <41DEA4B02DBDEF40A0F3B6D0DDB1237946A132A5@ORSMSX101.amr.corp.intel.com> <4FEA1265.1050408@gmail.com> <41DEA4B02DBDEF40A0F3B6D0DDB1237946A13317@ORSMSX101.amr.corp.intel.com> In-Reply-To: <41DEA4B02DBDEF40A0F3B6D0DDB1237946A13317@ORSMSX101.amr.corp.intel.com> Cc: "yocto@yoctoproject.org" Subject: Re: Yocto Development Manual Appendix B question X-BeenThere: yocto@yoctoproject.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: Discussion of all things Yocto List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Jun 2012 20:40:05 -0000 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 06/26/2012 04:21 PM, Rifenbark, Scott M wrote: > Jim, > > Yes - I am still running the very last part of my test. If that is the change then I will make it to the 1.2 version of the manual and publish it to the website. > > Scott While I had this working I thought I'd complete the Appendix B example for the CONFIG_SMP change. I'm finding problems with the compile step after menuconfig is run to turn off SMP. I get a mismatch that I don't understand: Value requested for CONFIG_SMP not in final ".config" Requested value: "CONFIG_SMP=y" Actual value set: "# CONFIG_SMP is not set" There must be another setting of CONFIG_SMP that is conflicting with the .config file Jim A > -----Original Message----- > From: yocto-bounces@yoctoproject.org [mailto:yocto-bounces@yoctoproject.org] On Behalf Of jfabernathy > Sent: Tuesday, June 26, 2012 12:50 PM > To: yocto@yoctoproject.org > Subject: Re: [yocto] Yocto Development Manual Appendix B question > > On 06/26/2012 02:07 PM, Rifenbark, Scott M wrote: >> When I attempted to rebuild minimal I hit the same error you did Jim regarding kern-tools-native. This would be expected as Bruce pointed out that problem is alive in denzil. I am going to set the poky-extras branch to 'denzil' and retry that part of the example. >> >> Scott >> >> -----Original Message----- >> From: yocto-bounces@yoctoproject.org [mailto:yocto-bounces@yoctoproject.org] On Behalf Of Rifenbark, Scott M >> Sent: Tuesday, June 26, 2012 10:44 AM >> To: Bruce Ashfield >> Cc: yocto@yoctoproject.org >> Subject: Re: [yocto] Yocto Development Manual Appendix B question >> >> I am on task 1507 of 1606 of a minimal build (from the example). No issues so far. > So now that Denzil has a branch in poky-extra, the only doc change is to > add the checkout -b denzil statement for the poky-extra directory. > Everything else is correct. > > Jim A > >> -----Original Message----- >> From: Bruce Ashfield [mailto:bruce.ashfield@windriver.com] >> Sent: Tuesday, June 26, 2012 10:42 AM >> To: Rifenbark, Scott M >> Cc: jfabernathy; yocto@yoctoproject.org >> Subject: Re: [yocto] Yocto Development Manual Appendix B question >> >> On 12-06-26 12:30 PM, Rifenbark, Scott M wrote: >>> I am going to run through the B.1 example verbatim from the "current" version of the manual and see what happens. >> Fixing the license check was just a matter of me locking the SRCREV >> for the tools to a value that works for denzil. I just pushed a denzil >> branch to poky-extras that built and booted the yocto kernel for >> me. >> >> Cheers, >> >> Bruce >> >>> Scott >>> >>> -----Original Message----- >>> From: Bruce Ashfield [mailto:bruce.ashfield@windriver.com] >>> Sent: Tuesday, June 26, 2012 9:28 AM >>> To: Rifenbark, Scott M >>> Cc: jfabernathy; yocto@yoctoproject.org >>> Subject: Re: [yocto] Yocto Development Manual Appendix B question >>> >>> On 12-06-26 12:26 PM, Rifenbark, Scott M wrote: >>>> This is a good point. In looking at the example it does not say what branch you should be dealing with for poky-extras. >>> And I'm configuring a test right now and will create a denzil >>> branch, once I see it works. >>> >>> Cheers, >>> >>> Bruce >>> >>>> -----Original Message----- >>>> From: Bruce Ashfield [mailto:bruce.ashfield@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-bounces@yoctoproject.org >>>>>>>> [mailto:yocto-bounces@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 >> _______________________________________________ >> yocto mailing list >> yocto@yoctoproject.org >> https://lists.yoctoproject.org/listinfo/yocto > > _______________________________________________ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto