Yocto Development Manual Appendix B question

Yocto Development Manual Appendix B question

[jfabernathy]

[-- Attachment #1: Type: text/plain, Size: 702 bytes --]

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




[-- Attachment #2: Type: text/html, Size: 1061 bytes --]

Re: Yocto Development Manual Appendix B question

[Bruce Ashfield]

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

Re: Yocto Development Manual Appendix B question

[Rifenbark, Scott M]

Bruce, 

Should the example note this?  Would it be best to specifically say to uncomment 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 ?="/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

Re: Yocto Development Manual Appendix B question

[Bruce Ashfield]

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

Re: Yocto Development Manual Appendix B question

[jfabernathy]

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

Re: Yocto Development Manual Appendix B question

[Bruce Ashfield]

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
>
>

Re: Yocto Development Manual Appendix B question

[jfabernathy]

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
>>
>>
>

Re: Yocto Development Manual Appendix B question

[Bruce Ashfield]

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
>>>
>>>
>>
>
>

Re: Yocto Development Manual Appendix B question

[Rifenbark, Scott M]

This is a good point.  In looking at the example it does not say what branch you should be dealing with for poky-extras.

-----Original Message-----
From: Bruce Ashfield [mailto:bruce.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
>>>
>>>
>>
>
>

Re: Yocto Development Manual Appendix B question

[Bruce Ashfield]

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
>>>>
>>>>
>>>
>>
>>
>

Re: Yocto Development Manual Appendix B question

[Rifenbark, Scott M]

I am going to run through the B.1 example verbatim from the "current" version of the manual and see what happens.

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
>>>>
>>>>
>>>
>>
>>
>

Re: Yocto Development Manual Appendix B question

[Bruce Ashfield]

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
>>>>>
>>>>>
>>>>
>>>
>>>
>>
>

Re: Yocto Development Manual Appendix B question

[Rifenbark, Scott M]

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] 
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
>>>>>
>>>>>
>>>>
>>>
>>>
>>
>

Re: Yocto Development Manual Appendix B question

[Rifenbark, Scott M]

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.

-----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

Re: Yocto Development Manual Appendix B question

[jfabernathy]

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

Re: Yocto Development Manual Appendix B question

[jfabernathy]

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

Re: Yocto Development Manual Appendix B question

[Rifenbark, Scott M]

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

-----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

Re: Yocto Development Manual Appendix B question

[jfabernathy]

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

Re: Yocto Development Manual Appendix B question

[Rifenbark, Scott M]

Jim, 

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] 
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

Re: Yocto Development Manual Appendix B question

[James Abernathy]

Yes I did cleansstate. 
On Jun 26, 2012, at 4:43 PM, "Rifenbark, Scott M" <scott.m.rifenbark@intel.com> wrote:

> Jim, 
> 
> 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] 
> 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
> 
> 

Re: Yocto Development Manual Appendix B question

[jfabernathy]

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
>

Re: Yocto Development Manual Appendix B question

[jfabernathy]

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
>>
>
>

Re: Yocto Development Manual Appendix B question

[Rifenbark, Scott M]

I have added a note to the manual explaining this warning.

Thanks, 
Scott

-----Original Message-----
From: jfabernathy [mailto:jfabernathy@gmail.com] 
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 
>> 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
>>
>
>

Re: Yocto Development Manual Appendix B question

[Bruce Ashfield]

On Tue, Jun 26, 2012 at 4:40 PM, jfabernathy <jfabernathy@gmail.com> 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.  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

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 enable
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.  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
>
>
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"

Re: Yocto Development Manual Appendix B question

[Rifenbark, Scott M]

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 situation. 

Scott

-----Original Message-----
From: Bruce Ashfield [mailto:bruce.ashfield@gmail.com] 
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 <jfabernathy@gmail.com> 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.  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

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 enable
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.  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
>
>
>
> _______________________________________________
> yocto mailing list
> yocto@yoctoproject.org
> https://lists.yoctoproject.org/listinfo/yocto



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await
thee at its end"