All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Zanussi <tom.zanussi@intel.com>
To: "Robert P. J. Day" <rpjday@crashcourse.ca>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Build error while following Appendix A. Yocto Project Development manual
Date: Tue, 01 Nov 2011 18:16:36 -0500	[thread overview]
Message-ID: <1320189396.26655.6.camel@elmorro> (raw)
In-Reply-To: <alpine.DEB.2.02.1111011835470.5888@localhost6.localdomain6>

On Tue, 2011-11-01 at 15:47 -0700, Robert P. J. Day wrote:
> some questions/observations as i'm getting close to the end of this
> appendix (some of which you've already seen and addressed), all done
> on my 64-bit ubuntu 11.10 system:
> 
>   * section A.3: rather than force the reader to follow a link or go
> to an earlier section, why not just supply the command to check out
> meta-intel/?
> 
>   $ git clone http://git.yoctoproject.org/cgit/cgit.cgi/meta-intel
> 

Makes sense to me.  Also, the same comment would apply to the main poky
repo as well.

>   * section A.5.1: is it actually *necessary* to delete the
> crownbay.conf file, and to change the comments in the mymachine.conf
> file?  admittedly, it's nice to keep things consistent, but if the
> text claims that something is "needed", then it really should be
> required.

No, not strictly necessary, but assuming you're using these instructions
to create a new BSP, definitely desirable.

> 
>   * section A.5.2.1: as we've noted, that first command can be tossed.
> in addition, should one remove the "crownbay" directory from that
> location?  since "crownbay" content is being removed from other
> locations, it would be nice to be consistent.
> 
>   * section A.5.2.2: delete first command
> 

I think that's right.

>   * section A.5.2.4: the "SRCREV_meta" values listed in the appendix
> don't match what's in the actual file.  so what are the correct
> values?
> 

Well, this example seems to assume you want to base it on the atom-pc
branch, so I guess we should use the value for that branch in meta-yocto
(meta-yocto/recipes-kernel/linux/linux-yocto_3.0.bbappend).  The meta
branch SRCREV should be inherited from the main recipe
(meta/recipes-kernel/linux/linux-yocto_3.0.bb) which looks like it
matches the current value and doesn't need to be changed.

Or at least that's what I'm building now.  I'll post the full transcript
assuming I get a good build out of it...

Tom

>   ... back to work ...
> 
> rday
> 




  reply	other threads:[~2011-11-01 23:16 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-01 18:37 Build error while following Appendix A. Yocto Project Development manual James Abernathy
2011-11-01 19:40 ` Tom Zanussi
2011-11-01 19:48   ` James Abernathy
2011-11-01 19:55     ` Tom Zanussi
2011-11-01 20:04       ` James Abernathy
2011-11-02  0:45     ` Tom Zanussi
2011-11-02 12:19       ` Robert P. J. Day
2011-11-02 14:18         ` Tom Zanussi
2011-11-02 14:35           ` Robert P. J. Day
2011-11-02 14:24       ` Jim Abernathy
2011-11-02 14:41         ` Tom Zanussi
2011-11-02 15:07           ` Jim Abernathy
2011-11-02 15:34             ` Tom Zanussi
2011-11-02 19:18               ` Jim Abernathy
2011-11-02 19:36                 ` Tom Zanussi
2011-11-02 20:07                   ` Jim Abernathy
2011-11-02 20:18                     ` Tom Zanussi
2011-11-02 22:05                       ` Jim Abernathy
2011-11-03 19:32       ` James Abernathy
2011-11-01 21:37   ` Robert P. J. Day
2011-11-01 21:46     ` Tom Zanussi
2011-11-01 21:54       ` Tom Zanussi
2011-11-01 22:47         ` Robert P. J. Day
2011-11-01 23:16           ` Tom Zanussi [this message]
2011-11-01 23:27             ` Robert P. J. Day
2011-11-01 21:56       ` Robert P. J. Day

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=1320189396.26655.6.camel@elmorro \
    --to=tom.zanussi@intel.com \
    --cc=rpjday@crashcourse.ca \
    --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.