All of lore.kernel.org
 help / color / mirror / Atom feed
From: jfabernathy <jfabernathy@gmail.com>
To: Bruce Ashfield <bruce.ashfield@windriver.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Yocto Development Manual Appendix B question
Date: Tue, 26 Jun 2012 12:11:39 -0400	[thread overview]
Message-ID: <4FE9DF3B.8010104@gmail.com> (raw)
In-Reply-To: <4FE9DD7F.2090402@windriver.com>

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




  reply	other threads:[~2012-06-26 16:11 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-26 14:52 Yocto Development Manual Appendix B question jfabernathy
2012-06-26 14:53 ` Bruce Ashfield
2012-06-26 14:56   ` Rifenbark, Scott M
2012-06-26 15:53     ` Bruce Ashfield
2012-06-26 16:00     ` jfabernathy
2012-06-26 16:04       ` Bruce Ashfield
2012-06-26 16:11         ` jfabernathy [this message]
2012-06-26 16:24           ` Bruce Ashfield
2012-06-26 16:26             ` Rifenbark, Scott M
2012-06-26 16:27               ` Bruce Ashfield
2012-06-26 16:30                 ` Rifenbark, Scott M
2012-06-26 17:42                   ` Bruce Ashfield
2012-06-26 17:44                     ` Rifenbark, Scott M
2012-06-26 18:07                       ` Rifenbark, Scott M
2012-06-26 19:22                         ` jfabernathy
2012-06-26 19:49                         ` jfabernathy
2012-06-26 20:21                           ` Rifenbark, Scott M
2012-06-26 20:40                             ` jfabernathy
2012-06-26 20:43                               ` Rifenbark, Scott M
2012-06-27  0:42                                 ` James Abernathy
2012-06-27 10:35                                 ` jfabernathy
2012-06-27 11:35                                   ` jfabernathy
2012-06-27 14:39                                     ` Rifenbark, Scott M
2012-06-26 20:57                               ` Bruce Ashfield
2012-06-26 21:15                                 ` Rifenbark, Scott M

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4FE9DF3B.8010104@gmail.com \
    --to=jfabernathy@gmail.com \
    --cc=bruce.ashfield@windriver.com \
    --cc=yocto@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.