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 3B201E0070C for ; Tue, 26 Jun 2012 07:52:30 -0700 (PDT) Received: by vbjk17 with SMTP id k17so3479006vbj.35 for ; Tue, 26 Jun 2012 07:52:29 -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:subject :content-type; bh=AVKF+FUbrhlrOTGrBAsw8UYPZWlFSiWBrrYEmUhWKMQ=; b=nveSWKbbDXLkGviF9IL+E4zw48Xj5v7bARJaMHhEwGGUvvsXw9+CgKRSmtKCQ5jLXQ ry/At48V56UKwNIefipZ5B1Y9X9K7ixff2I4sWzlg6/Qtb1IXYcpwYuwA9+rdr4jRP0w GSEz58nECA0aMnek8QD/Zuo9xroJmQQrc53qbZW34a9TQ5WF+KE7TylnV3t5auc5B2mt 5qOdExN8bQiSegUcivbCgXNmGR/EL6d6Hrk3cwdH6TgACm7kp+yCQZAak9J9Rw6TM80Z iLFORepQJRb63igww0CLhfJP2oJKQL+XpPCbAKhGLjRrQ8sjpu3Ymrb4ATiMnekxhzuD 62nw== Received: by 10.52.27.244 with SMTP id w20mr9268047vdg.67.1340722349205; Tue, 26 Jun 2012 07:52:29 -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 s10sm55205570vdg.10.2012.06.26.07.52.28 (version=SSLv3 cipher=OTHER); Tue, 26 Jun 2012 07:52:28 -0700 (PDT) Message-ID: <4FE9CCAD.7080003@gmail.com> Date: Tue, 26 Jun 2012 10:52:29 -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: "yocto@yoctoproject.org" Subject: 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 14:52:30 -0000 Content-Type: multipart/alternative; boundary="------------050309030903070605010005" --------------050309030903070605010005 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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? Jim A --------------050309030903070605010005 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 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?

Jim A



--------------050309030903070605010005-- From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail1.windriver.com (mail1.windriver.com [147.11.146.13]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id D60FAE0070C for ; Tue, 26 Jun 2012 07:54:14 -0700 (PDT) Received: from ALA-HCA.corp.ad.wrs.com (ala-hca [147.11.189.40]) by mail1.windriver.com (8.14.3/8.14.3) with ESMTP id q5QEsBbL026733 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 26 Jun 2012 07:54:11 -0700 (PDT) Received: from [128.224.146.67] (128.224.146.67) by ALA-HCA.corp.ad.wrs.com (147.11.189.50) with Microsoft SMTP Server id 14.1.255.0; Tue, 26 Jun 2012 07:54:10 -0700 Message-ID: <4FE9CD04.60604@windriver.com> Date: Tue, 26 Jun 2012 10:53:56 -0400 From: Bruce Ashfield User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1 MIME-Version: 1.0 To: jfabernathy References: <4FE9CCAD.7080003@gmail.com> In-Reply-To: <4FE9CCAD.7080003@gmail.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 14:54:15 -0000 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit 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 From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 91494E006D9 for ; Tue, 26 Jun 2012 07:56:24 -0700 (PDT) Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga102.jf.intel.com with ESMTP; 26 Jun 2012 07:56:24 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.67,352,1309762800"; d="scan'208";a="158386645" Received: from orsmsx606.amr.corp.intel.com ([10.22.226.128]) by orsmga001.jf.intel.com with ESMTP; 26 Jun 2012 07:56:24 -0700 Received: from orsmsx152.amr.corp.intel.com (10.22.226.39) by orsmsx606.amr.corp.intel.com (10.22.226.128) with Microsoft SMTP Server (TLS) id 8.2.255.0; Tue, 26 Jun 2012 07:56:24 -0700 Received: from orsmsx101.amr.corp.intel.com ([169.254.8.59]) by ORSMSX152.amr.corp.intel.com ([169.254.8.235]) with mapi id 14.01.0355.002; Tue, 26 Jun 2012 07:56:23 -0700 From: "Rifenbark, Scott M" To: Bruce Ashfield , jfabernathy Thread-Topic: [yocto] Yocto Development Manual Appendix B question Thread-Index: AQHNU6tX5HKMCOJfWU226Ph+u+uRAJcNJQcA//+LH1A= Date: Tue, 26 Jun 2012 14:56:23 +0000 Message-ID: <41DEA4B02DBDEF40A0F3B6D0DDB1237946A130B2@ORSMSX101.amr.corp.intel.com> References: <4FE9CCAD.7080003@gmail.com> <4FE9CD04.60604@windriver.com> In-Reply-To: <4FE9CD04.60604@windriver.com> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.22.254.140] MIME-Version: 1.0 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 14:56:24 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Bruce,=20 Should the example note this? Would it be best to specifically say to unco= mment that SRC_URI line? Scott -----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 ?=3D"/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 =3D > "git://${KSRC_linux_yocto_3_2};protocol=3Dfile;nocheckout=3D1;branch=3D${= KBRANCH},meta;name=3Dmachine,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 From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail1.windriver.com (mail1.windriver.com [147.11.146.13]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 81319E006D9 for ; Tue, 26 Jun 2012 08:53:49 -0700 (PDT) Received: from ALA-HCA.corp.ad.wrs.com (ala-hca [147.11.189.40]) by mail1.windriver.com (8.14.3/8.14.3) with ESMTP id q5QFrllr027776 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 26 Jun 2012 08:53:47 -0700 (PDT) Received: from [128.224.146.67] (128.224.146.67) by ALA-HCA.corp.ad.wrs.com (147.11.189.50) with Microsoft SMTP Server id 14.1.255.0; Tue, 26 Jun 2012 08:53:47 -0700 Message-ID: <4FE9DAFD.6000600@windriver.com> Date: Tue, 26 Jun 2012 11:53:33 -0400 From: Bruce Ashfield User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.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> In-Reply-To: <41DEA4B02DBDEF40A0F3B6D0DDB1237946A130B2@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 15:53:49 -0000 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit On 12-06-26 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? It's worth noting, and I can make sure that the comments in the recipes reflect this as well. My comments within the individual bbappends may not be noticed, or may be less obvious when you look at the recipes-kernel as a whole. Cheers, Bruce > > Scott > > -----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 From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-vc0-f176.google.com (mail-vc0-f176.google.com [209.85.220.176]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 7BDFBE0070C for ; Tue, 26 Jun 2012 09:00:28 -0700 (PDT) Received: by vcbfo14 with SMTP id fo14so64383vcb.35 for ; Tue, 26 Jun 2012 09:00:27 -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=/GSPsPNpBzC57v8KEa2TYjQpmNbOckBEYSWU1jTONWo=; b=f9v2l9Ku8ZmRvs9WGRlvN5WEaJrO4xzBi+I2sKaWR6IdAPGdZshIdniayrvu5X5mWK yy22s3cEKACZjTTbc++vyA6uXf+bpj9R6yBOlpBuKaDnPCSZsP0tKkNxb8X3fkSrDXUP 3Z5KMI7iqlQfx9rx4SUlIwtWWklJm9JI1hwioBcIbAjVjTMuutsLdp6RFYDzpS64wkh6 KwRlZLfGli/5DRWUx4FfYCBLgPXfXNAed1Vsnlg3KFQZzZaqWrJ6GRMZ18vD/pxnUkKO IUw2uiaN4IF0pvRw2V7UshVEqxGutIse9jXCAH9Q8qIH52BFfo/CZIatAKfOkK/Bv8rY Rrjg== Received: by 10.52.98.8 with SMTP id ee8mr9463812vdb.58.1340726427862; Tue, 26 Jun 2012 09:00:27 -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 ek5sm55432530vdb.5.2012.06.26.09.00.26 (version=SSLv3 cipher=OTHER); Tue, 26 Jun 2012 09:00:26 -0700 (PDT) Message-ID: <4FE9DC9B.2090104@gmail.com> Date: Tue, 26 Jun 2012 12:00:27 -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> In-Reply-To: <41DEA4B02DBDEF40A0F3B6D0DDB1237946A130B2@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 16:00:28 -0000 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 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 From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail1.windriver.com (mail1.windriver.com [147.11.146.13]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 2654AE0070C for ; Tue, 26 Jun 2012 09:04:31 -0700 (PDT) Received: from ALA-HCA.corp.ad.wrs.com (ala-hca [147.11.189.40]) by mail1.windriver.com (8.14.3/8.14.3) with ESMTP id q5QG4TPx027968 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 26 Jun 2012 09:04:29 -0700 (PDT) Received: from [128.224.146.67] (128.224.146.67) by ALA-HCA.corp.ad.wrs.com (147.11.189.50) with Microsoft SMTP Server id 14.1.255.0; Tue, 26 Jun 2012 09:04:29 -0700 Message-ID: <4FE9DD7F.2090402@windriver.com> Date: Tue, 26 Jun 2012 12:04:15 -0400 From: Bruce Ashfield User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1 MIME-Version: 1.0 To: jfabernathy References: <4FE9CCAD.7080003@gmail.com> <4FE9CD04.60604@windriver.com> <41DEA4B02DBDEF40A0F3B6D0DDB1237946A130B2@ORSMSX101.amr.corp.intel.com> <4FE9DC9B.2090104@gmail.com> In-Reply-To: <4FE9DC9B.2090104@gmail.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 16:04:31 -0000 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit 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. 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 > > From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qc0-f182.google.com (mail-qc0-f182.google.com [209.85.216.182]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id AAC3EE0070C for ; Tue, 26 Jun 2012 09:11:39 -0700 (PDT) Received: by qcsg15 with SMTP id g15so60306qcs.13 for ; Tue, 26 Jun 2012 09:11:39 -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=3MALnDQB8HLyDyA9R8ssNf2OwuM7X2bR+Eq3q+Wgxck=; b=f2q3/2FWISTb0PdwdGgdP7RSZBp3LspmeaNCdRd/8VGpCnYluhtByG7cizOy11aMxm VRSsS9BciTqPXkj/cIXb9Ha6up1+Z8xB3AAs4W82omgOptTF5d3dQSpkuF4Ql3r6AKul MtFUde2uLE/Y19f0ki90pms75au4Nq7SCRP2pVwmrm+ItBOEM37MAZg3rhMVU6ZwuFZQ JL5NxUnAq6gh4pMGF4L7uTRST3b0MFpYepzDDGA0CGl8Z4IqeNBql4Wx+HGYTbupeNey NitSJXNWZAZ84ATGw2yo+zPFTJis59b8xTgMbCPF0B8erQsBr8yyX5t6nOC0iRoHkzhM qi4w== Received: by 10.229.135.132 with SMTP id n4mr7148674qct.95.1340727098883; Tue, 26 Jun 2012 09:11:38 -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 9sm18564477qac.9.2012.06.26.09.11.37 (version=SSLv3 cipher=OTHER); Tue, 26 Jun 2012 09:11:38 -0700 (PDT) Message-ID: <4FE9DF3B.8010104@gmail.com> Date: Tue, 26 Jun 2012 12:11:39 -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: Bruce Ashfield References: <4FE9CCAD.7080003@gmail.com> <4FE9CD04.60604@windriver.com> <41DEA4B02DBDEF40A0F3B6D0DDB1237946A130B2@ORSMSX101.amr.corp.intel.com> <4FE9DC9B.2090104@gmail.com> <4FE9DD7F.2090402@windriver.com> In-Reply-To: <4FE9DD7F.2090402@windriver.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 16:11:39 -0000 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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. 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 >> >> > From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.windriver.com (mail.windriver.com [147.11.1.11]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 7D899E006D9 for ; Tue, 26 Jun 2012 09:24:31 -0700 (PDT) Received: from ALA-HCA.corp.ad.wrs.com (ala-hca [147.11.189.40]) by mail.windriver.com (8.14.3/8.14.3) with ESMTP id q5QGOSim021468 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 26 Jun 2012 09:24:28 -0700 (PDT) Received: from [128.224.146.67] (128.224.146.67) by ALA-HCA.corp.ad.wrs.com (147.11.189.50) with Microsoft SMTP Server id 14.1.255.0; Tue, 26 Jun 2012 09:24:28 -0700 Message-ID: <4FE9E22E.8080305@windriver.com> Date: Tue, 26 Jun 2012 12:24:14 -0400 From: Bruce Ashfield User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.0.1 MIME-Version: 1.0 To: jfabernathy 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> In-Reply-To: <4FE9DF3B.8010104@gmail.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 16:24:31 -0000 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit 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 >>> >>> >> > > From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 38521E0070C for ; Tue, 26 Jun 2012 09:26:58 -0700 (PDT) Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga101.fm.intel.com with ESMTP; 26 Jun 2012 09:26:57 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.71,315,1320652800"; d="scan'208";a="170245392" Received: from orsmsx604.amr.corp.intel.com ([10.22.226.87]) by fmsmga001.fm.intel.com with ESMTP; 26 Jun 2012 09:26:57 -0700 Received: from orsmsx104.amr.corp.intel.com (10.22.225.131) by orsmsx604.amr.corp.intel.com (10.22.226.87) with Microsoft SMTP Server (TLS) id 8.2.255.0; Tue, 26 Jun 2012 09:26:57 -0700 Received: from orsmsx101.amr.corp.intel.com ([169.254.8.59]) by ORSMSX104.amr.corp.intel.com ([169.254.3.217]) with mapi id 14.01.0355.002; Tue, 26 Jun 2012 09:26:56 -0700 From: "Rifenbark, Scott M" To: Bruce Ashfield , jfabernathy Thread-Topic: [yocto] Yocto Development Manual Appendix B question Thread-Index: AQHNU6tX5HKMCOJfWU226Ph+u+uRAJcNJQcA//+LH1CAAId2gIAAARCAgAACEoCAAAOEAP//i0Ow Date: Tue, 26 Jun 2012 16:26:56 +0000 Message-ID: <41DEA4B02DBDEF40A0F3B6D0DDB1237946A131AA@ORSMSX101.amr.corp.intel.com> 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> In-Reply-To: <4FE9E22E.8080305@windriver.com> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.22.254.140] MIME-Version: 1.0 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 16:26:58 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable This is a good point. In looking at the example it does not say what branc= h you should be dealing with for poky-extras. -----Original Message----- From: Bruce Ashfield [mailto:bruce.ashfield@windriver.com]=20 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=3D5;endline=3D9;md5=3De2bf4415f3d843f43= d2e22b0d91a6fee >>> >>> >>> 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 ?=3D"/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 =3D >>>>> "git://${KSRC_linux_yocto_3_2};protocol=3Dfile;nocheckout=3D1;branch= =3D${KBRANCH},meta;name=3Dmachine,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 extra= s >>>> 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 >>> >>> >> > > From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail1.windriver.com (mail1.windriver.com [147.11.146.13]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 42E81E0070C for ; Tue, 26 Jun 2012 09:28:11 -0700 (PDT) Received: from ALA-HCA.corp.ad.wrs.com (ala-hca [147.11.189.40]) by mail1.windriver.com (8.14.3/8.14.3) with ESMTP id q5QGS9UC028332 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 26 Jun 2012 09:28:09 -0700 (PDT) Received: from [128.224.146.67] (128.224.146.67) by ALA-HCA.corp.ad.wrs.com (147.11.189.50) with Microsoft SMTP Server id 14.1.255.0; Tue, 26 Jun 2012 09:28:09 -0700 Message-ID: <4FE9E30B.9080903@windriver.com> Date: Tue, 26 Jun 2012 12:27:55 -0400 From: Bruce Ashfield User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.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> In-Reply-To: <41DEA4B02DBDEF40A0F3B6D0DDB1237946A131AA@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 16:28:11 -0000 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit 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 >>>> >>>> >>> >> >> > From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 3CE89E0070C for ; Tue, 26 Jun 2012 09:31:16 -0700 (PDT) Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga101.jf.intel.com with ESMTP; 26 Jun 2012 09:30:55 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.67,351,1309762800"; d="scan'208";a="162942142" Received: from orsmsx604.amr.corp.intel.com ([10.22.226.87]) by orsmga002.jf.intel.com with ESMTP; 26 Jun 2012 09:30:55 -0700 Received: from orsmsx153.amr.corp.intel.com (10.22.226.247) by orsmsx604.amr.corp.intel.com (10.22.226.87) with Microsoft SMTP Server (TLS) id 8.2.255.0; Tue, 26 Jun 2012 09:30:55 -0700 Received: from orsmsx101.amr.corp.intel.com ([169.254.8.59]) by ORSMSX153.amr.corp.intel.com ([169.254.13.115]) with mapi id 14.01.0355.002; Tue, 26 Jun 2012 09:30:54 -0700 From: "Rifenbark, Scott M" To: Bruce Ashfield Thread-Topic: [yocto] Yocto Development Manual Appendix B question Thread-Index: AQHNU6tX5HKMCOJfWU226Ph+u+uRAJcNJQcA//+LH1CAAId2gIAAARCAgAACEoCAAAOEAP//i0OwgAB1xID//4tbcA== Date: Tue, 26 Jun 2012 16:30:53 +0000 Message-ID: <41DEA4B02DBDEF40A0F3B6D0DDB1237946A131CC@ORSMSX101.amr.corp.intel.com> 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> In-Reply-To: <4FE9E30B.9080903@windriver.com> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.22.254.140] MIME-Version: 1.0 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 16:31:16 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I am going to run through the B.1 example verbatim from the "current" versi= on of the manual and see what happens. Scott -----Original Message----- From: Bruce Ashfield [mailto:bruce.ashfield@windriver.com]=20 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 bra= nch 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 an= d >>>> I still fail building the image. The failure is related to kernel tool= s: >>>> >>>> ERROR: kern-tools-native: md5 data is not matching for >>>> file://git/tools/kgit;beginline=3D5;endline=3D9;md5=3De2bf4415f3d843f4= 3d2e22b0d91a6fee >>>> >>>> >>>> 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-d= ev > 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 ?=3D"/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 =3D >>>>>> "git://${KSRC_linux_yocto_3_2};protocol=3Dfile;nocheckout=3D1;branch= =3D${KBRANCH},meta;name=3Dmachine,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 extr= as >>>>> 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 >>>> >>>> >>> >> >> > From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail.windriver.com (mail.windriver.com [147.11.1.11]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 1AC31E006D9 for ; Tue, 26 Jun 2012 10:42:40 -0700 (PDT) Received: from ALA-HCA.corp.ad.wrs.com (ala-hca [147.11.189.40]) by mail.windriver.com (8.14.3/8.14.3) with ESMTP id q5QHgbOh003344 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL); Tue, 26 Jun 2012 10:42:37 -0700 (PDT) Received: from [128.224.146.67] (128.224.146.67) by ALA-HCA.corp.ad.wrs.com (147.11.189.50) with Microsoft SMTP Server id 14.1.255.0; Tue, 26 Jun 2012 10:42:37 -0700 Message-ID: <4FE9F47F.80306@windriver.com> Date: Tue, 26 Jun 2012 13:42:23 -0400 From: Bruce Ashfield User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:12.0) Gecko/20120430 Thunderbird/12.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> In-Reply-To: <41DEA4B02DBDEF40A0F3B6D0DDB1237946A131CC@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 17:42:40 -0000 Content-Type: text/plain; charset="ISO-8859-1"; format=flowed Content-Transfer-Encoding: 7bit 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 >>>>> >>>>> >>>> >>> >>> >> > From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 74A5CE0070C for ; Tue, 26 Jun 2012 10:44:20 -0700 (PDT) Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga102.jf.intel.com with ESMTP; 26 Jun 2012 10:44:20 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.67,351,1309762800"; d="scan'208";a="162978190" Received: from orsmsx606.amr.corp.intel.com ([10.22.226.128]) by orsmga002.jf.intel.com with ESMTP; 26 Jun 2012 10:44:20 -0700 Received: from orsmsx102.amr.corp.intel.com (10.22.225.129) by orsmsx606.amr.corp.intel.com (10.22.226.128) with Microsoft SMTP Server (TLS) id 8.2.255.0; Tue, 26 Jun 2012 10:44:20 -0700 Received: from orsmsx101.amr.corp.intel.com ([169.254.8.59]) by ORSMSX102.amr.corp.intel.com ([169.254.1.237]) with mapi id 14.01.0355.002; Tue, 26 Jun 2012 10:44:19 -0700 From: "Rifenbark, Scott M" To: Bruce Ashfield Thread-Topic: [yocto] Yocto Development Manual Appendix B question Thread-Index: AQHNU6tX5HKMCOJfWU226Ph+u+uRAJcNJQcA//+LH1CAAId2gIAAARCAgAACEoCAAAOEAP//i0OwgAB1xID//4tbcAARLnqAAA6hmFA= Date: Tue, 26 Jun 2012 17:44:18 +0000 Message-ID: <41DEA4B02DBDEF40A0F3B6D0DDB1237946A13288@ORSMSX101.amr.corp.intel.com> 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> In-Reply-To: <4FE9F47F.80306@windriver.com> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.22.254.140] MIME-Version: 1.0 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 17:44:20 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I am on task 1507 of 1606 of a minimal build (from the example). No issues= so far. -----Original Message----- From: Bruce Ashfield [mailto:bruce.ashfield@windriver.com]=20 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" ver= sion 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 br= anch 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 t= o >>>>>> uncomment that SRC_URI line? >>>>>> >>>>>> Scott >>>>> I think some text needs to be added. I uncommented the SRC_URI line a= nd >>>>> I still fail building the image. The failure is related to kernel too= ls: >>>>> >>>>> ERROR: kern-tools-native: md5 data is not matching for >>>>> file://git/tools/kgit;beginline=3D5;endline=3D9;md5=3De2bf4415f3d843f= 43d2e22b0d91a6fee >>>>> >>>>> >>>>> 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 Sectio= n >>>>>>> B.1.7, it states that you need to put in the statement: >>>>>>> >>>>>>> KSRC_linux_yocto_3_2 ?=3D"/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 i= s >>>>>>> commented out: >>>>>>> >>>>>>> # SRC_URI =3D >>>>>>> "git://${KSRC_linux_yocto_3_2};protocol=3Dfile;nocheckout=3D1;branc= h=3D${KBRANCH},meta;name=3Dmachine,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 ext= ras >>>>>> 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 fi= x >>>>>> 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 >>>>> >>>>> >>>> >>> >>> >> > From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 58E51E006D9 for ; Tue, 26 Jun 2012 11:07:43 -0700 (PDT) Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga102.fm.intel.com with ESMTP; 26 Jun 2012 11:07:43 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.71,315,1320652800"; d="scan'208";a="170289954" Received: from orsmsx606.amr.corp.intel.com ([10.22.226.128]) by fmsmga001.fm.intel.com with ESMTP; 26 Jun 2012 11:07:42 -0700 Received: from orsmsx151.amr.corp.intel.com (10.22.226.38) by orsmsx606.amr.corp.intel.com (10.22.226.128) with Microsoft SMTP Server (TLS) id 8.2.255.0; Tue, 26 Jun 2012 11:07:42 -0700 Received: from orsmsx101.amr.corp.intel.com ([169.254.8.59]) by ORSMSX151.amr.corp.intel.com ([169.254.7.154]) with mapi id 14.01.0355.002; Tue, 26 Jun 2012 11:07:42 -0700 From: "Rifenbark, Scott M" To: "Rifenbark, Scott M" , Bruce Ashfield Thread-Topic: [yocto] Yocto Development Manual Appendix B question Thread-Index: AQHNU6tX5HKMCOJfWU226Ph+u+uRAJcNJQcA//+LH1CAAId2gIAAARCAgAACEoCAAAOEAP//i0OwgAB1xID//4tbcAARLnqAAA6hmFAAHHb4UA== Date: Tue, 26 Jun 2012 18:07:41 +0000 Message-ID: <41DEA4B02DBDEF40A0F3B6D0DDB1237946A132A5@ORSMSX101.amr.corp.intel.com> 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> In-Reply-To: <41DEA4B02DBDEF40A0F3B6D0DDB1237946A13288@ORSMSX101.amr.corp.intel.com> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.22.254.140] MIME-Version: 1.0 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 18:07:43 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable When I attempted to rebuild minimal I hit the same error you did Jim regard= ing kern-tools-native. This would be expected as Bruce pointed out that pr= oblem is alive in denzil. I am going to set the poky-extras branch to 'den= zil' 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. -----Original Message----- From: Bruce Ashfield [mailto:bruce.ashfield@windriver.com]=20 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" ver= sion 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 br= anch 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 t= o >>>>>> uncomment that SRC_URI line? >>>>>> >>>>>> Scott >>>>> I think some text needs to be added. I uncommented the SRC_URI line a= nd >>>>> I still fail building the image. The failure is related to kernel too= ls: >>>>> >>>>> ERROR: kern-tools-native: md5 data is not matching for >>>>> file://git/tools/kgit;beginline=3D5;endline=3D9;md5=3De2bf4415f3d843f= 43d2e22b0d91a6fee >>>>> >>>>> >>>>> 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 Sectio= n >>>>>>> B.1.7, it states that you need to put in the statement: >>>>>>> >>>>>>> KSRC_linux_yocto_3_2 ?=3D"/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 i= s >>>>>>> commented out: >>>>>>> >>>>>>> # SRC_URI =3D >>>>>>> "git://${KSRC_linux_yocto_3_2};protocol=3Dfile;nocheckout=3D1;branc= h=3D${KBRANCH},meta;name=3Dmachine,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 ext= ras >>>>>> 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 fi= x >>>>>> 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 From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-vc0-f176.google.com (mail-vc0-f176.google.com [209.85.220.176]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 67CDFE006D9 for ; Tue, 26 Jun 2012 12:22:53 -0700 (PDT) Received: by vcbfo14 with SMTP id fo14so247811vcb.35 for ; Tue, 26 Jun 2012 12:22:52 -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:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=5k20kJ2eF+OXoIsHRf0oNdVX6SEN/cAHub1VmUoKrq4=; b=omO+ZxvDrpLx7snfVFBHWm0B/IvbdvefGVwM0mhdDEUGscYwPUE01dWqAgzhkvOPte leJzIko5eShamBKRiTpJfa741gl9PtyND3rYm6qpMKyr/ptFLCS3MXnROyrPIHL0dG/4 ZKrWqA+RXnCsGUCbQzJtHSR0wQ+jvhfdRxf/oYN3ADbVXu5SlEAa5vpXwwN/tKsYaJFq 42mV47qq72oI3WuqLTnlcfoTu0eaPN7MTkEZVwg1LHR97NzOWvjfGuKXVT82BDrdhjyW osj7muSAOac0bVrlq6a+ddpSSiNK0qdEKZ9ouX9ufCWcNDFv+w+xf5NCdSfpmP+Ut3jL d3PA== Received: by 10.52.24.179 with SMTP id v19mr10146986vdf.127.1340738572656; Tue, 26 Jun 2012 12:22:52 -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 by2sm56067544vdb.22.2012.06.26.12.22.51 (version=SSLv3 cipher=OTHER); Tue, 26 Jun 2012 12:22:52 -0700 (PDT) Message-ID: <4FEA0C0D.5030809@gmail.com> Date: Tue, 26 Jun 2012 15:22:53 -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: yocto@yoctoproject.org 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> In-Reply-To: <41DEA4B02DBDEF40A0F3B6D0DDB1237946A132A5@ORSMSX101.amr.corp.intel.com> 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 19:22:53 -0000 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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. I just finished testing with Denzil branch on poky and poky-extra. I made the Hello printk mods and used the new bbappend that Bruce setup in poky-extra for denzil. I think he had already uncommented the SRC_URI and all I had to do was put in the statement from the Appendix B about KSRC. and mod the bblayer.conf to include poky-extra. Everything compiled and worked as expected. 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 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 5B52AE006D9 for ; Tue, 26 Jun 2012 12:49:59 -0700 (PDT) Received: by vbjk17 with SMTP id k17so264296vbj.35 for ; Tue, 26 Jun 2012 12:49:58 -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:subject:references :in-reply-to:content-type:content-transfer-encoding; bh=gHdygIlvjEFzNtektnyYG6i/lwwzvT5hm4oyvASoyEw=; b=bzGYLHhHcQoyfhhl/7h9eU9xt4GlXw4nw5guN18HXY0h/hsL09YlLEAbx/U7w/fqBk yyWK1XcEWiyNbxPulDNC6xQJpIARXEDFcbpNRd3xXC2sC/G7tAyYOOo4UXzo7dcc1+8j 5ic6gp6m9VYI9/qhnyhZffAD6ab/PaMjudnPy3fOt9vcS8OP38m1BI6glkVxF5yicbp6 66sr1b4up4m1g/1wMJ0Lqtx+GDYtRAYIQSSAnLg2b846DjxAwoRWpEVSacQ/7dCnkbaY tA1CA+D0zdScQkIO80197xtS0Gw8d1lbNu6gjCCmt3+5xIOBprPnjxqNtycapTN6aPPZ S/kw== Received: by 10.52.174.37 with SMTP id bp5mr9902206vdc.114.1340740198705; Tue, 26 Jun 2012 12:49:58 -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 bn5sm47906847vdb.19.2012.06.26.12.49.56 (version=SSLv3 cipher=OTHER); Tue, 26 Jun 2012 12:49:56 -0700 (PDT) Message-ID: <4FEA1265.1050408@gmail.com> Date: Tue, 26 Jun 2012 15:49:57 -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: yocto@yoctoproject.org 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> In-Reply-To: <41DEA4B02DBDEF40A0F3B6D0DDB1237946A132A5@ORSMSX101.amr.corp.intel.com> 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 19:49:59 -0000 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit 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 From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 57373E0070C for ; Tue, 26 Jun 2012 13:21:25 -0700 (PDT) Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga101.jf.intel.com with ESMTP; 26 Jun 2012 13:21:06 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.67,352,1309762800"; d="scan'208";a="158499330" Received: from orsmsx604.amr.corp.intel.com ([10.22.226.87]) by orsmga001.jf.intel.com with ESMTP; 26 Jun 2012 13:21:06 -0700 Received: from orsmsx103.amr.corp.intel.com (10.22.225.130) by orsmsx604.amr.corp.intel.com (10.22.226.87) with Microsoft SMTP Server (TLS) id 8.2.255.0; Tue, 26 Jun 2012 13:21:06 -0700 Received: from orsmsx101.amr.corp.intel.com ([169.254.8.59]) by ORSMSX103.amr.corp.intel.com ([169.254.2.73]) with mapi id 14.01.0355.002; Tue, 26 Jun 2012 13:21:05 -0700 From: "Rifenbark, Scott M" To: jfabernathy , "yocto@yoctoproject.org" Thread-Topic: [yocto] Yocto Development Manual Appendix B question Thread-Index: AQHNU6tX5HKMCOJfWU226Ph+u+uRAJcNJQcA//+LH1CAAId2gIAAARCAgAACEoCAAAOEAP//i0OwgAB1xID//4tbcAARLnqAAA6hmFAAHHb4UP/+yt+AgABs2/A= Date: Tue, 26 Jun 2012 20:21:04 +0000 Message-ID: <41DEA4B02DBDEF40A0F3B6D0DDB1237946A13317@ORSMSX101.amr.corp.intel.com> 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> In-Reply-To: <4FEA1265.1050408@gmail.com> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.22.254.140] MIME-Version: 1.0 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:21:25 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Jim,=20 Yes - I am still running the very last part of my test. If that is the cha= nge then I will make it to the 1.2 version of the manual and publish it to = the website. =20 Scott -----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 rega= rding 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 'd= enzil' and retry that part of the example. > > Scott > > -----Original Message----- > From: yocto-bounces@yoctoproject.org [mailto:yocto-bounces@yoctoproject.o= rg] 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 issu= es so far. So now that Denzil has a branch in poky-extra, the only doc change is to=20 add the checkout -b denzil statement for the poky-extra directory.=20 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" ve= rsion 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 b= ranch 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 to= ols: >>>>>> >>>>>> ERROR: kern-tools-native: md5 data is not matching for >>>>>> file://git/tools/kgit;beginline=3D5;endline=3D9;md5=3De2bf4415f3d843= f43d2e22b0d91a6fee >>>>>> >>>>>> >>>>>> 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 shoul= d >>> 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 Secti= on >>>>>>>> B.1.7, it states that you need to put in the statement: >>>>>>>> >>>>>>>> KSRC_linux_yocto_3_2 ?=3D"/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 =3D >>>>>>>> "git://${KSRC_linux_yocto_3_2};protocol=3Dfile;nocheckout=3D1;bran= ch=3D${KBRANCH},meta;name=3Dmachine,meta" >>>>>>>> >>>>>>>> >>>>>>>> >>>>>>>> Should that line be uncommented or is the SRC_URI already defaulte= d >>>>>>>> somewhere to use the newly defined KSRC_linux_yocto_3_2 variable? >>>>>>> It should be uncommented. I commented them by default, since the ex= tras >>>>>>> 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 f= ix >>>>>>> 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 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 From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 85EB2E006D9 for ; Tue, 26 Jun 2012 13:43:31 -0700 (PDT) Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga101.fm.intel.com with ESMTP; 26 Jun 2012 13:43:27 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.71,315,1320652800"; d="scan'208";a="185310132" Received: from orsmsx604.amr.corp.intel.com ([10.22.226.87]) by fmsmga002.fm.intel.com with ESMTP; 26 Jun 2012 13:43:27 -0700 Received: from orsmsx152.amr.corp.intel.com (10.22.226.39) by orsmsx604.amr.corp.intel.com (10.22.226.87) with Microsoft SMTP Server (TLS) id 8.2.255.0; Tue, 26 Jun 2012 13:43:26 -0700 Received: from orsmsx101.amr.corp.intel.com ([169.254.8.59]) by ORSMSX152.amr.corp.intel.com ([169.254.8.235]) with mapi id 14.01.0355.002; Tue, 26 Jun 2012 13:43:26 -0700 From: "Rifenbark, Scott M" To: jfabernathy Thread-Topic: [yocto] Yocto Development Manual Appendix B question Thread-Index: AQHNU6tX5HKMCOJfWU226Ph+u+uRAJcNJQcA//+LH1CAAId2gIAAARCAgAACEoCAAAOEAP//i0OwgAB1xID//4tbcAARLnqAAA6hmFAAHHb4UP/+yt+AgABs2/D//6EngIAAdK4Q Date: Tue, 26 Jun 2012 20:43:26 +0000 Message-ID: <41DEA4B02DBDEF40A0F3B6D0DDB1237946A13340@ORSMSX101.amr.corp.intel.com> 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> <4FEA1E25.9080103@gmail.com> In-Reply-To: <4FEA1E25.9080103@gmail.com> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.22.254.140] MIME-Version: 1.0 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:43:31 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Jim,=20 Did you cleansstate before building and using menuconfig? There is a bug (= 2256) that prevents configurations made using menuconfig from sticking. Scott -----Original Message----- From: jfabernathy [mailto:jfabernathy@gmail.com]=20 Sent: Tuesday, June 26, 2012 1:40 PM To: Rifenbark, Scott M Cc: yocto@yoctoproject.org Subject: Re: [yocto] Yocto Development Manual Appendix B question 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 c= hange then I will make it to the 1.2 version of the manual and publish it t= o the website. > > Scott While I had this working I thought I'd complete the Appendix B example=20 for the CONFIG_SMP change. I'm finding problems with the compile step=20 after menuconfig is run to turn off SMP. I get a mismatch that I don't=20 understand: Value requested for CONFIG_SMP not in final ".config" Requested value: "CONFIG_SMP=3Dy" Actual value set: "# CONFIG_SMP is not set" There must be another setting of CONFIG_SMP that is conflicting with the=20 .config file Jim A > -----Original Message----- > From: yocto-bounces@yoctoproject.org [mailto:yocto-bounces@yoctoproject.o= rg] 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 reg= arding 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 iss= ues 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" v= ersion 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 t= ools: >>>>>>> >>>>>>> ERROR: kern-tools-native: md5 data is not matching for >>>>>>> file://git/tools/kgit;beginline=3D5;endline=3D9;md5=3De2bf4415f3d84= 3f43d2e22b0d91a6fee >>>>>>> >>>>>>> >>>>>>> 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 tha= t >>>>>> '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 shou= ld >>>> match the main repository branch .. and I could ensure that meta-kerne= l-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 reflec= t >>>>> 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 Ashfiel= d >>>>>>>> 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 Sect= ion >>>>>>>>> B.1.7, it states that you need to put in the statement: >>>>>>>>> >>>>>>>>> KSRC_linux_yocto_3_2 ?=3D"/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 =3D >>>>>>>>> "git://${KSRC_linux_yocto_3_2};protocol=3Dfile;nocheckout=3D1;bra= nch=3D${KBRANCH},meta;name=3Dmachine,meta" >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> Should that line be uncommented or is the SRC_URI already default= ed >>>>>>>>> somewhere to use the newly defined KSRC_linux_yocto_3_2 variable? >>>>>>>> It should be uncommented. I commented them by default, since the e= xtras >>>>>>>> repository is a bit of a collection ground. If they are uncommente= d, >>>>>>>> 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 From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-qc0-f182.google.com (mail-qc0-f182.google.com [209.85.216.182]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 68739E006D9 for ; Tue, 26 Jun 2012 13:57:26 -0700 (PDT) Received: by qcsg15 with SMTP id g15so223994qcs.13 for ; Tue, 26 Jun 2012 13:57:26 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; bh=sZT93mVom0i/K/MxXtgHu86pFSj6l5+eXDgaYKBDVuI=; b=P9GloNxhxtP+CWwYQSbigwoEBMEZAPU+FiCOhC5PB16/lM7eWBfjC1CLJjJdPJIgL7 8ckrldI7DLnTbfaMbBCBud6ukcah+wQwuYv5fIARlm7kureAIwkX7d9dX2sqlA8UsvCZ At3xdsa911UNDR9Z1yfzzqkePZByWYx0qlmzXd0/edUOgFzbjum88lCjYPyJb0iz+gpX 9RkpGeremgEIAVj98QMChEuMMx0DlZnzkgtOxayWU7zCOi9NA+pbi9aGIn0pTb0dk8os gE98+/gVDBSp35BLYAOfS/RxDt34d3IGl2pa+pKpV//rgLKtXyFvi3HmIvE34BcU/Hwm 9PYA== MIME-Version: 1.0 Received: by 10.224.18.146 with SMTP id w18mr26864792qaa.96.1340744245778; Tue, 26 Jun 2012 13:57:25 -0700 (PDT) Received: by 10.229.41.5 with HTTP; Tue, 26 Jun 2012 13:57:25 -0700 (PDT) In-Reply-To: <4FEA1E25.9080103@gmail.com> 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> <4FEA1E25.9080103@gmail.com> Date: Tue, 26 Jun 2012 16:57:25 -0400 Message-ID: From: Bruce Ashfield To: jfabernathy 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:57:26 -0000 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable On Tue, Jun 26, 2012 at 4:40 PM, jfabernathy wrote: > On 06/26/2012 04:21 PM, Rifenbark, Scott M wrote: >> >> Jim, >> >> Yes - I am still running the very last part of my test. =A0If that is th= e >> 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 fo= r > the CONFIG_SMP change. =A0I'm finding problems with the compile step afte= r > menuconfig is run to turn off SMP. =A0I get a mismatch that I don't > understand: > > Value requested for CONFIG_SMP not in final ".config" > Requested value: "CONFIG_SMP=3Dy" > Actual value set: "# CONFIG_SMP is not set" > > There must be another setting of CONFIG_SMP that is conflicting with the > .config file If I'm reading this correctly, it's just another tweak needed to the docs. When we first wrote those sections, there were issues with the kernel configuration audit information being masked. In this case the kernel configuration audit knows that your BSP wants to en= able SMP, but yet it didn't appear in the final .config, so it warns you. But since you manually turned it off .. this is expected. I can't decide if we should increase complexity and detect this to inhibit the warning, or document it. For now, I'm in the document it camp. Cheers, Bruce > > > 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. =A0This would be expected as Bruce pointed= out >>> that problem is alive in denzil. =A0I am going to set the poky-extras b= ranch >>> 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). =A0No >>> 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. =A0In looking at the example it does not say wh= at >>>>> 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 sa= y >>>>>>>>> to >>>>>>>>> uncomment that SRC_URI line? >>>>>>>>> >>>>>>>>> Scott >>>>>>>> >>>>>>>> I think some text needs to be added. I uncommented the SRC_URI lin= e >>>>>>>> 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=3D5;endline=3D9;md5=3De2bf4415f3d8= 43f43d2e22b0d91a6fee >>>>>>>> >>>>>>>> >>>>>>>> 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 fi= x >>>>>>>> ERROR: Function failed: do_qa_configure >>>>>>> >>>>>>> This one is actually fixed on master, but poky-extras .. is just th= at >>>>>>> 'extra', so this may still be alive in that repo. >>>>>>> >>>>>>> This wouldn't need to be documented, since it's a bug/issue, and no= t >>>>>>> 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 no= t >>>>>> 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 t= o >>>>> master (unless you want to :) >>>>> >>>>> Cheers, >>>>> >>>>> Bruce >>>>> >>>>>> I can always test on Master, but the docs need to be update to refle= ct >>>>>> 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 Ashfie= ld >>>>>>>>> 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 ?=3D"/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, tha= t >>>>>>>>>> is >>>>>>>>>> commented out: >>>>>>>>>> >>>>>>>>>> # SRC_URI =3D >>>>>>>>>> >>>>>>>>>> "git://${KSRC_linux_yocto_3_2};protocol=3Dfile;nocheckout=3D1;br= anch=3D${KBRANCH},meta;name=3Dmachine,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 > > > > _______________________________________________ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto --=20 "Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end" From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 71C8EE006D9 for ; Tue, 26 Jun 2012 14:15:28 -0700 (PDT) Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga102.fm.intel.com with ESMTP; 26 Jun 2012 14:15:28 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.71,315,1320652800"; d="scan'208";a="170352525" Received: from orsmsx603.amr.corp.intel.com ([10.22.226.49]) by fmsmga001.fm.intel.com with ESMTP; 26 Jun 2012 14:15:28 -0700 Received: from orsmsx103.amr.corp.intel.com (10.22.225.130) by orsmsx603.amr.corp.intel.com (10.22.226.49) with Microsoft SMTP Server (TLS) id 8.2.255.0; Tue, 26 Jun 2012 14:15:25 -0700 Received: from orsmsx101.amr.corp.intel.com ([169.254.8.59]) by ORSMSX103.amr.corp.intel.com ([169.254.2.73]) with mapi id 14.01.0355.002; Tue, 26 Jun 2012 14:15:24 -0700 From: "Rifenbark, Scott M" To: Bruce Ashfield , jfabernathy Thread-Topic: [yocto] Yocto Development Manual Appendix B question Thread-Index: AQHNU6tX5HKMCOJfWU226Ph+u+uRAJcNJQcA//+LH1CAAId2gIAAARCAgAACEoCAAAOEAP//i0OwgAB1xID//4tbcAARLnqAAA6hmFAAHHb4UP/+yt+AgABs2/D//6EngIAABNiAgABwgaA= Date: Tue, 26 Jun 2012 21:15:24 +0000 Message-ID: <41DEA4B02DBDEF40A0F3B6D0DDB1237946A13361@ORSMSX101.amr.corp.intel.com> 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> <4FEA1E25.9080103@gmail.com> In-Reply-To: Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.22.254.140] MIME-Version: 1.0 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 21:15:28 -0000 Content-Language: en-US Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Yes - looking more closely this is not the bug issue but standard warnings.= I got these also. I can put a note in the example explaining the situati= on.=20 Scott -----Original Message----- From: Bruce Ashfield [mailto:bruce.ashfield@gmail.com]=20 Sent: Tuesday, June 26, 2012 1:57 PM To: jfabernathy Cc: Rifenbark, Scott M; yocto@yoctoproject.org Subject: Re: [yocto] Yocto Development Manual Appendix B question On Tue, Jun 26, 2012 at 4:40 PM, jfabernathy wrote: > On 06/26/2012 04:21 PM, Rifenbark, Scott M wrote: >> >> Jim, >> >> Yes - I am still running the very last part of my test. =A0If that is th= e >> 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 fo= r > the CONFIG_SMP change. =A0I'm finding problems with the compile step afte= r > menuconfig is run to turn off SMP. =A0I get a mismatch that I don't > understand: > > Value requested for CONFIG_SMP not in final ".config" > Requested value: "CONFIG_SMP=3Dy" > Actual value set: "# CONFIG_SMP is not set" > > There must be another setting of CONFIG_SMP that is conflicting with the > .config file If I'm reading this correctly, it's just another tweak needed to the docs. When we first wrote those sections, there were issues with the kernel configuration audit information being masked. In this case the kernel configuration audit knows that your BSP wants to en= able SMP, but yet it didn't appear in the final .config, so it warns you. But since you manually turned it off .. this is expected. I can't decide if we should increase complexity and detect this to inhibit the warning, or document it. For now, I'm in the document it camp. Cheers, Bruce > > > 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. =A0This would be expected as Bruce pointed= out >>> that problem is alive in denzil. =A0I am going to set the poky-extras b= ranch >>> 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). =A0No >>> 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. =A0In looking at the example it does not say wh= at >>>>> 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 sa= y >>>>>>>>> to >>>>>>>>> uncomment that SRC_URI line? >>>>>>>>> >>>>>>>>> Scott >>>>>>>> >>>>>>>> I think some text needs to be added. I uncommented the SRC_URI lin= e >>>>>>>> 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=3D5;endline=3D9;md5=3De2bf4415f3d8= 43f43d2e22b0d91a6fee >>>>>>>> >>>>>>>> >>>>>>>> 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 fi= x >>>>>>>> ERROR: Function failed: do_qa_configure >>>>>>> >>>>>>> This one is actually fixed on master, but poky-extras .. is just th= at >>>>>>> 'extra', so this may still be alive in that repo. >>>>>>> >>>>>>> This wouldn't need to be documented, since it's a bug/issue, and no= t >>>>>>> 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 no= t >>>>>> 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 t= o >>>>> master (unless you want to :) >>>>> >>>>> Cheers, >>>>> >>>>> Bruce >>>>> >>>>>> I can always test on Master, but the docs need to be update to refle= ct >>>>>> 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 Ashfie= ld >>>>>>>>> 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 ?=3D"/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, tha= t >>>>>>>>>> is >>>>>>>>>> commented out: >>>>>>>>>> >>>>>>>>>> # SRC_URI =3D >>>>>>>>>> >>>>>>>>>> "git://${KSRC_linux_yocto_3_2};protocol=3Dfile;nocheckout=3D1;br= anch=3D${KBRANCH},meta;name=3Dmachine,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 > > > > _______________________________________________ > yocto mailing list > yocto@yoctoproject.org > https://lists.yoctoproject.org/listinfo/yocto --=20 "Thou shalt not follow the NULL pointer, for chaos and madness await thee at its end" From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-gg0-f176.google.com (mail-gg0-f176.google.com [209.85.161.176]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 17905E006D9 for ; Tue, 26 Jun 2012 17:42:48 -0700 (PDT) Received: by ggnk4 with SMTP id k4so607906ggn.35 for ; Tue, 26 Jun 2012 17:42:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=references:in-reply-to:mime-version:content-transfer-encoding :content-type:message-id:cc:x-mailer:from:subject:date:to; bh=wnFPJMkzoRgYOj9YQb/+d/7koPvFZPowAMvLTTixCIk=; b=wWmqW6ZBc2eELn7FP4sMK5R+HJgjK/XWUDTzm2rhnJZNlZ5chZ0wlNfPbls8/cYh8Y 1zTFyxOmp1zpAF19mGFFnSEPX4sKvE1pzPcxfclVQhkpaZ+5bgDXl3pyTjXr28YTUOqJ 6CZOfUrjhZbiR9E5gOtcOVjg+jo3paNEnzNv1zDCbiCeEIMgczLkct9WlzQZExah+MjS zuqA5/1mptmdUN0wSSYLbrMA9FK4Z55JdbCpfy7Hp5uH/pG97gD3Nz3Q64AbsNScBRHy rfGqRQzJTFryP+7JPsjPFEOlLDJ35lZqWivxC+OxoxiJUoqddISHYZqQk9Z59QZlOPBk l7/g== Received: by 10.236.161.2 with SMTP id v2mr20104516yhk.26.1340757767258; Tue, 26 Jun 2012 17:42:47 -0700 (PDT) Received: from [10.68.121.217] (mobile-166-147-115-050.mycingular.net. [166.147.115.50]) by mx.google.com with ESMTPS id c28sm107231785yhk.2.2012.06.26.17.42.45 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 26 Jun 2012 17:42:46 -0700 (PDT) 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> <4FEA1E25.9080103@gmail.com> <41DEA4B02DBDEF40A0F3B6D0DDB1237946A13340@ORSMSX101.amr.corp.intel.com> In-Reply-To: <41DEA4B02DBDEF40A0F3B6D0DDB1237946A13340@ORSMSX101.amr.corp.intel.com> Mime-Version: 1.0 (1.0) Message-Id: <0826D141-960A-4B14-900A-3ECCBED18F9D@gmail.com> X-Mailer: iPhone Mail (9B206) From: James Abernathy Date: Tue, 26 Jun 2012 20:42:38 -0400 To: "Rifenbark, Scott M" 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: Wed, 27 Jun 2012 00:42:48 -0000 Content-Transfer-Encoding: quoted-printable Content-Type: text/plain; charset=us-ascii Yes I did cleansstate.=20 On Jun 26, 2012, at 4:43 PM, "Rifenbark, Scott M" wrote: > Jim,=20 >=20 > Did you cleansstate before building and using menuconfig? There is a bu= g (2256) that prevents configurations made using menuconfig from sticking. >=20 > Scott >=20 > -----Original Message----- > From: jfabernathy [mailto:jfabernathy@gmail.com]=20 > Sent: Tuesday, June 26, 2012 1:40 PM > To: Rifenbark, Scott M > Cc: yocto@yoctoproject.org > Subject: Re: [yocto] Yocto Development Manual Appendix B question >=20 > On 06/26/2012 04:21 PM, Rifenbark, Scott M wrote: >> Jim, >>=20 >> 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. >>=20 >> Scott >=20 > While I had this working I thought I'd complete the Appendix B example= =20 > for the CONFIG_SMP change. I'm finding problems with the compile step= =20 > after menuconfig is run to turn off SMP. I get a mismatch that I don't= =20 > understand: >=20 > Value requested for CONFIG_SMP not in final ".config" > Requested value: "CONFIG_SMP=3Dy" > Actual value set: "# CONFIG_SMP is not set" >=20 > There must be another setting of CONFIG_SMP that is conflicting with the= = =20 > .config file >=20 > Jim A >=20 >> -----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 >>=20 >> 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 r= egarding kern-tools-native. This would be expected as Bruce pointed out th= at problem is alive in denzil. I am going to set the poky-extras branch to= 'denzil' and retry that part of the example. >>>=20 >>> Scott >>>=20 >>> -----Original Message----- >>> From: yocto-bounces@yoctoproject.org [mailto:yocto-bounces@yoctoprojec= t.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 >>>=20 >>> I am on task 1507 of 1606 of a minimal build (from the example). No i= ssues so far. >> So now that Denzil has a branch in poky-extra, the only doc change is t= o >> add the checkout -b denzil statement for the poky-extra directory. >> Everything else is correct. >>=20 >> Jim A >>=20 >>> -----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 >>>=20 >>> 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. >>>=20 >>> Cheers, >>>=20 >>> Bruce >>>=20 >>>> Scott >>>>=20 >>>> -----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 >>>>=20 >>>> 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 wha= t 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. >>>>=20 >>>> Cheers, >>>>=20 >>>> Bruce >>>>=20 >>>>> -----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 >>>>>=20 >>>>> 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, >>>>>>>>>=20 >>>>>>>>> Should the example note this? Would it be best to specifically s= ay to >>>>>>>>> uncomment that SRC_URI line? >>>>>>>>>=20 >>>>>>>>> Scott >>>>>>>> I think some text needs to be added. I uncommented the SRC_URI li= ne and >>>>>>>> I still fail building the image. The failure is related to kernel= tools: >>>>>>>>=20 >>>>>>>> ERROR: kern-tools-native: md5 data is not matching for >>>>>>>> file://git/tools/kgit;beginline=3D5;endline=3D9;md5=3De2bf4415f3d= 843f43d2e22b0d91a6fee >>>>>>>>=20 >>>>>>>>=20 >>>>>>>> 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 f= ix >>>>>>>> ERROR: Function failed: do_qa_configure >>>>>>> This one is actually fixed on master, but poky-extras .. is just t= hat >>>>>>> 'extra', so this may still be alive in that repo. >>>>>>>=20 >>>>>>> This wouldn't need to be documented, since it's a bug/issue, and n= ot >>>>>>> something that would persist. >>>>>>>=20 >>>>>>> What release are you pairing poky extras with ? I can always creat= e a >>>>>>> branch to make sure they are consistent. >>>>>>>=20 >>>>>> I was using Denzil because the snapshot noted in the example does n= ot >>>>>> exist. So there is another doc issue. >>>>> Aha. In this case, we could note that the poky-extras repo branch sh= ould >>>>> match the main repository branch .. and I could ensure that meta-ker= nel-dev >>>>> works in that configuration. >>>>>=20 >>>>> That's likely the right solution, rather than forcing you to switch = to >>>>> master (unless you want to :) >>>>>=20 >>>>> Cheers, >>>>>=20 >>>>> Bruce >>>>>=20 >>>>>> I can always test on Master, but the docs need to be update to refl= ect >>>>>> something that will work to completion without errors, IMHO. >>>>>>=20 >>>>>> Jim A >>>>>>=20 >>>>>>> Cheers, >>>>>>>=20 >>>>>>> Bruce >>>>>>>=20 >>>>>>>> Jim A >>>>>>>>=20 >>>>>>>>> -----Original Message----- >>>>>>>>> From: yocto-bounces@yoctoproject.org >>>>>>>>> [mailto:yocto-bounces@yoctoproject.org] On Behalf Of Bruce Ashfi= eld >>>>>>>>> Sent: Tuesday, June 26, 2012 7:54 AM >>>>>>>>> To: jfabernathy >>>>>>>>> Cc: yocto@yoctoproject.org >>>>>>>>> Subject: Re: [yocto] Yocto Development Manual Appendix B questio= n >>>>>>>>>=20 >>>>>>>>> On 12-06-26 10:52 AM, jfabernathy wrote: >>>>>>>>>> In the example in The Developement Manual v1.2 in Appendix B Se= ction >>>>>>>>>> B.1.7, it states that you need to put in the statement: >>>>>>>>>>=20 >>>>>>>>>> KSRC_linux_yocto_3_2 ?=3D"/home/scottrif/linux-yocto-3.2.git" >>>>>>>>>>=20 >>>>>>>>>> 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, th= at is >>>>>>>>>> commented out: >>>>>>>>>>=20 >>>>>>>>>> # SRC_URI =3D >>>>>>>>>> "git://${KSRC_linux_yocto_3_2};protocol=3Dfile;nocheckout=3D1;b= ranch=3D${KBRANCH},meta;name=3Dmachine,meta" >>>>>>>>>>=20 >>>>>>>>>>=20 >>>>>>>>>>=20 >>>>>>>>>> Should that line be uncommented or is the SRC_URI already defau= lted >>>>>>>>>> somewhere to use the newly defined KSRC_linux_yocto_3_2 variabl= e? >>>>>>>>> It should be uncommented. I commented them by default, since the= extras >>>>>>>>> repository is a bit of a collection ground. If they are uncommen= ted, >>>>>>>>> and >>>>>>>>> combined with the AUTOREV also set in the file, you are forced t= o fix >>>>>>>>> all files, versus just the one you want. >>>>>>>>>=20 >>>>>>>>> Cheers, >>>>>>>>>=20 >>>>>>>>> Bruce >>>>>>>>>=20 >>>>>>>>>> Jim A >>>>>>>>>>=20 >>>>>>>>>>=20 >>>>>>>>>>=20 >>>>>>>>>>=20 >>>>>>>>>>=20 >>>>>>>>>> _______________________________________________ >>>>>>>>>> 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 >>=20 >> _______________________________________________ >> yocto mailing list >> yocto@yoctoproject.org >> https://lists.yoctoproject.org/listinfo/yocto >=20 >=20 From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-yw0-f53.google.com (mail-yw0-f53.google.com [209.85.213.53]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 316C7E00739 for ; Wed, 27 Jun 2012 03:35:46 -0700 (PDT) Received: by yhp26 with SMTP id 26so1033244yhp.12 for ; Wed, 27 Jun 2012 03:35:45 -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=JDxvMfv86UULs+0HFxTrmhxBZDSjBzcVXy36AJK5nZ4=; b=F2YJBRntI/IyC3HK1WYyp6NM4syPdGoSoj5cVfC8f+NkSOysOITszSw+nTLsE8DOjj 8uxDL/q2aGaabpP3T6k/Rzo5xnImj3puNKj86FwJsz/acvgmW4yxaAqY75Nw0FGQ0I7F 4csIPVqOX7RFd3gRSdLIUKr24/133xYppco8uEWyCjCYWajugyoXoOiJ4eq/hZefm9Rl WVWgmuzi+kv2npjra0C4qKDdhuGrLfMMvdnZg/ORZvYDW0f3J9cB4/gWH7qCcwdOaj4p KnpflqmLzQn1XiTd97gIRNJ2e2OU/gqSQXXDwfzzwqniUSo3owhY23Ni5o6wAtEg4Bkb s0vg== Received: by 10.236.109.196 with SMTP id s44mr21809511yhg.35.1340793345274; Wed, 27 Jun 2012 03:35:45 -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 c28sm109835697yhk.2.2012.06.27.03.35.44 (version=SSLv3 cipher=OTHER); Wed, 27 Jun 2012 03:35:44 -0700 (PDT) Message-ID: <4FEAE1FF.6070006@gmail.com> Date: Wed, 27 Jun 2012 06:35:43 -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> <4FEA1E25.9080103@gmail.com> <41DEA4B02DBDEF40A0F3B6D0DDB1237946A13340@ORSMSX101.amr.corp.intel.com> In-Reply-To: <41DEA4B02DBDEF40A0F3B6D0DDB1237946A13340@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: Wed, 27 Jun 2012 10:35:46 -0000 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 06/26/2012 04:43 PM, Rifenbark, Scott M wrote: > Jim, > > Did you cleansstate before building and using menuconfig? There is a bug (2256) that prevents configurations made using menuconfig from sticking. As I said from my iPhone last night, yes I did do cleansstate as stated in the manual. I will reset and run a test of Apendix B.2 taking the path of not having done B.1 first. Maybe the stuff related to setting up you local kernel and modifying the source had some impact. More later. JIm A > Scott > > -----Original Message----- > From: jfabernathy [mailto:jfabernathy@gmail.com] > Sent: Tuesday, June 26, 2012 1:40 PM > To: Rifenbark, Scott M > Cc: yocto@yoctoproject.org > Subject: Re: [yocto] Yocto Development Manual Appendix B question > > 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 > From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-yw0-f53.google.com (mail-yw0-f53.google.com [209.85.213.53]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id 978CEE00739 for ; Wed, 27 Jun 2012 04:35:35 -0700 (PDT) Received: by yhp26 with SMTP id 26so1076843yhp.12 for ; Wed, 27 Jun 2012 04:35:35 -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=O4u6eEPOfKtIIcwkEyuF/ZJTYF9AF87UxhZCRR2bvIQ=; b=wjs0CO6Jt/boND5ncm+1PbwB14Kb3HnnvGdo9rqI/ICqPaeldI/AOpC/x0nP1arCJy 1dqgLg/Z0x73VCX95joPdxDQW0oGA4nGRif8Jnaqhj8NDi+M2tvl27ON/6JCGMYQOOjn zwbyOo57kBfOaN/o70hfWbExH3bZ0RvKhx85wBb1aEov7yJevFyyRaLMhma38J63kzT1 jxfT2EyWfeJ2eHYHSs5DYV4vpz9ykwOcpuSMfoLFXxTN8JiUkO0xCiGQlqDfTTJeiS0u 0OJISq9VOR6zR3eGNxcY88Ot7leZD7H4XBFjQkBDnvVdiu8qqAJ8dlnQsS5PqXUlq72y 4ajw== Received: by 10.236.182.161 with SMTP id o21mr22310631yhm.43.1340796934955; Wed, 27 Jun 2012 04:35:34 -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 r8sm63041721ani.9.2012.06.27.04.35.33 (version=SSLv3 cipher=OTHER); Wed, 27 Jun 2012 04:35:34 -0700 (PDT) Message-ID: <4FEAF005.5050606@gmail.com> Date: Wed, 27 Jun 2012 07:35:33 -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> <4FEA1E25.9080103@gmail.com> <41DEA4B02DBDEF40A0F3B6D0DDB1237946A13340@ORSMSX101.amr.corp.intel.com> <4FEAE1FF.6070006@gmail.com> In-Reply-To: <4FEAE1FF.6070006@gmail.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: Wed, 27 Jun 2012 11:35:35 -0000 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit On 06/27/2012 06:35 AM, jfabernathy wrote: > On 06/26/2012 04:43 PM, Rifenbark, Scott M wrote: >> Jim, >> >> Did you cleansstate before building and using menuconfig? There is a >> bug (2256) that prevents configurations made using menuconfig from >> sticking. > As I said from my iPhone last night, yes I did do cleansstate as > stated in the manual. I will reset and run a test of Apendix B.2 > taking the path of not having done B.1 first. Maybe the stuff related > to setting up you local kernel and modifying the source had some > impact. More later. > > JIm A > Okay I did the example B.2 in the developer manual without having done B.1 first. Summary is it works as documented. However, the WARNING below scared me into thinking I had an issue. If I ignore it, everything works. I was surprised that after recompiling linux-yocto and building it, I didn't have to rebuild the image. I would have thought that a step of bitbake core-image-minimal was needed to add the newly compiled and built kernel to the boot image. Anyway, here's the warning and the contents of the mismatch.cfg file: WARNING: There were 1 hardware options requested that do not have a corresponding value present in the final ".config" file. This probably means you aren't getting the config you wanted. The full list can be found in your workspace at: /build/qemux86/tmp/work/qemux86-poky-linux/linux-yocto-3.2.18+git1+49f931bc294d5b6be60502bbd448cff5aa766235_1+c228cadee60f0ada73d11a36f6932f50a1c52d48-r1/linux/meta/cfg/standard/default/common-pc/mismatch.cfg Waiting a second to make sure you get a chance to see this... ------------------------------------------------------------- The file mismatch.cfg contains: Value requested for CONFIG_SMP not in final ".config" Requested value: "CONFIG_SMP=y" Actual value set: "# CONFIG_SMP is not set" Jim A >> Scott >> >> -----Original Message----- >> From: jfabernathy [mailto:jfabernathy@gmail.com] >> Sent: Tuesday, June 26, 2012 1:40 PM >> To: Rifenbark, Scott M >> Cc: yocto@yoctoproject.org >> Subject: Re: [yocto] Yocto Development Manual Appendix B question >> >> 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 >> > > From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by yocto-www.yoctoproject.org (Postfix) with ESMTP id D5959E0073F for ; Wed, 27 Jun 2012 07:39:13 -0700 (PDT) Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga102.jf.intel.com with ESMTP; 27 Jun 2012 07:39:13 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.67,351,1309762800"; d="scan'208";a="163454399" Received: from orsmsx604.amr.corp.intel.com ([10.22.226.87]) by orsmga002.jf.intel.com with ESMTP; 27 Jun 2012 07:39:13 -0700 Received: from orsmsx103.amr.corp.intel.com (10.22.225.130) by orsmsx604.amr.corp.intel.com (10.22.226.87) with Microsoft SMTP Server (TLS) id 8.2.255.0; Wed, 27 Jun 2012 07:39:13 -0700 Received: from orsmsx101.amr.corp.intel.com ([169.254.8.59]) by ORSMSX103.amr.corp.intel.com ([169.254.2.73]) with mapi id 14.01.0355.002; Wed, 27 Jun 2012 07:39:12 -0700 From: "Rifenbark, Scott M" To: jfabernathy Thread-Topic: [yocto] Yocto Development Manual Appendix B question Thread-Index: AQHNU6tX5HKMCOJfWU226Ph+u+uRAJcNJQcA//+LH1CAAId2gIAAARCAgAACEoCAAAOEAP//i0OwgAB1xID//4tbcAARLnqAAA6hmFAAHHb4UP/+yt+AgABs2/D//6EngIAAdK4QgAB0y4CAABC4gIAAQiKA Date: Wed, 27 Jun 2012 14:39:12 +0000 Message-ID: <41DEA4B02DBDEF40A0F3B6D0DDB1237946A136E1@ORSMSX101.amr.corp.intel.com> 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> <4FEA1E25.9080103@gmail.com> <41DEA4B02DBDEF40A0F3B6D0DDB1237946A13340@ORSMSX101.amr.corp.intel.com> <4FEAE1FF.6070006@gmail.com> <4FEAF005.5050606@gmail.com> In-Reply-To: <4FEAF005.5050606@gmail.com> Accept-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.22.254.138] MIME-Version: 1.0 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: Wed, 27 Jun 2012 14:39:14 -0000 Content-Language: en-US Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable I have added a note to the manual explaining this warning. Thanks,=20 Scott -----Original Message----- From: jfabernathy [mailto:jfabernathy@gmail.com]=20 Sent: Wednesday, June 27, 2012 4:36 AM To: Rifenbark, Scott M Cc: yocto@yoctoproject.org Subject: Re: [yocto] Yocto Development Manual Appendix B question On 06/27/2012 06:35 AM, jfabernathy wrote: > On 06/26/2012 04:43 PM, Rifenbark, Scott M wrote: >> Jim, >> >> Did you cleansstate before building and using menuconfig? There is a=20 >> bug (2256) that prevents configurations made using menuconfig from=20 >> sticking. > As I said from my iPhone last night, yes I did do cleansstate as=20 > stated in the manual. I will reset and run a test of Apendix B.2=20 > taking the path of not having done B.1 first. Maybe the stuff related=20 > to setting up you local kernel and modifying the source had some=20 > impact. More later. > > JIm A > Okay I did the example B.2 in the developer manual without having done=20 B.1 first. Summary is it works as documented. However, the WARNING=20 below scared me into thinking I had an issue. If I ignore it,=20 everything works. I was surprised that after recompiling linux-yocto=20 and building it, I didn't have to rebuild the image. I would have=20 thought that a step of bitbake core-image-minimal was needed to add the=20 newly compiled and built kernel to the boot image. Anyway, here's the=20 warning and the contents of the mismatch.cfg file: WARNING: There were 1 hardware options requested that do not have a corresponding value present in the final ".config" file. This probably means you aren't getting the config you wanted. The full list can be found in your workspace at: /build/qemux86/tmp/work/qemux86-poky-linux/linux-yocto-3.2.18+git1+49f931bc= 294d5b6be60502bbd448cff5aa766235_1+c228cadee60f0ada73d11a36f6932f50a1c52d48= -r1/linux/meta/cfg/standard/default/common-pc/mismatch.cfg Waiting a second to make sure you get a chance to see this... ------------------------------------------------------------- The file mismatch.cfg contains: Value requested for CONFIG_SMP not in final ".config" Requested value: "CONFIG_SMP=3Dy" Actual value set: "# CONFIG_SMP is not set" Jim A >> Scott >> >> -----Original Message----- >> From: jfabernathy [mailto:jfabernathy@gmail.com] >> Sent: Tuesday, June 26, 2012 1:40 PM >> To: Rifenbark, Scott M >> Cc: yocto@yoctoproject.org >> Subject: Re: [yocto] Yocto Development Manual Appendix B question >> >> 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=20 >>> the change then I will make it to the 1.2 version of the manual and=20 >>> 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=3Dy" >> 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=20 >>> [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=20 >>>> Jim regarding kern-tools-native. This would be expected as Bruce=20 >>>> pointed out that problem is alive in denzil. I am going to set the=20 >>>> poky-extras branch to 'denzil' and retry that part of the example. >>>> >>>> Scott >>>> >>>> -----Original Message----- >>>> From: yocto-bounces@yoctoproject.org=20 >>>> [mailto:yocto-bounces@yoctoproject.org] On Behalf Of Rifenbark,=20 >>>> 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). =20 >>>> No issues so far. >>> So now that Denzil has a branch in poky-extra, the only doc change=20 >>> 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=20 >>>>> "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=20 >>>>>> 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=20 >>>>>>>>>> specifically say to >>>>>>>>>> uncomment that SRC_URI line? >>>>>>>>>> >>>>>>>>>> Scott >>>>>>>>> I think some text needs to be added. I uncommented the SRC_URI=20 >>>>>>>>> line and >>>>>>>>> I still fail building the image. The failure is related to=20 >>>>>>>>> kernel tools: >>>>>>>>> >>>>>>>>> ERROR: kern-tools-native: md5 data is not matching for >>>>>>>>> file://git/tools/kgit;beginline=3D5;endline=3D9;md5=3De2bf4415f3d= 843f43d2e22b0d91a6fee=20 >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> 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,=20 >>>>>>>>> please fix >>>>>>>>> ERROR: Function failed: do_qa_configure >>>>>>>> This one is actually fixed on master, but poky-extras .. is=20 >>>>>>>> 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,=20 >>>>>>>> and not >>>>>>>> something that would persist. >>>>>>>> >>>>>>>> What release are you pairing poky extras with ? I can always=20 >>>>>>>> create a >>>>>>>> branch to make sure they are consistent. >>>>>>>> >>>>>>> I was using Denzil because the snapshot noted in the example=20 >>>>>>> does not >>>>>>> exist. So there is another doc issue. >>>>>> Aha. In this case, we could note that the poky-extras repo branch=20 >>>>>> should >>>>>> match the main repository branch .. and I could ensure that=20 >>>>>> meta-kernel-dev >>>>>> works in that configuration. >>>>>> >>>>>> That's likely the right solution, rather than forcing you to=20 >>>>>> switch to >>>>>> master (unless you want to :) >>>>>> >>>>>> Cheers, >>>>>> >>>>>> Bruce >>>>>> >>>>>>> I can always test on Master, but the docs need to be update to=20 >>>>>>> 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=20 >>>>>>>>>> Ashfield >>>>>>>>>> Sent: Tuesday, June 26, 2012 7:54 AM >>>>>>>>>> To: jfabernathy >>>>>>>>>> Cc: yocto@yoctoproject.org >>>>>>>>>> Subject: Re: [yocto] Yocto Development Manual Appendix B=20 >>>>>>>>>> question >>>>>>>>>> >>>>>>>>>> On 12-06-26 10:52 AM, jfabernathy wrote: >>>>>>>>>>> In the example in The Developement Manual v1.2 in Appendix B=20 >>>>>>>>>>> Section >>>>>>>>>>> B.1.7, it states that you need to put in the statement: >>>>>>>>>>> >>>>>>>>>>> KSRC_linux_yocto_3_2 ?=3D"/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,=20 >>>>>>>>>>> |linux-yocto_3.2.bbappend| , I >>>>>>>>>>> seen a >>>>>>>>>>> SRC_URI line, immediately after our inserted KSRC statement,=20 >>>>>>>>>>> that is >>>>>>>>>>> commented out: >>>>>>>>>>> >>>>>>>>>>> # SRC_URI =3D >>>>>>>>>>> "git://${KSRC_linux_yocto_3_2};protocol=3Dfile;nocheckout=3D1;b= ranch=3D${KBRANCH},meta;name=3Dmachine,meta"=20 >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> Should that line be uncommented or is the SRC_URI already=20 >>>>>>>>>>> defaulted >>>>>>>>>>> somewhere to use the newly defined KSRC_linux_yocto_3_2=20 >>>>>>>>>>> variable? >>>>>>>>>> It should be uncommented. I commented them by default, since=20 >>>>>>>>>> the extras >>>>>>>>>> repository is a bit of a collection ground. If they are=20 >>>>>>>>>> uncommented, >>>>>>>>>> and >>>>>>>>>> combined with the AUTOREV also set in the file, you are=20 >>>>>>>>>> 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 >> > >