All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tom Zanussi <tom.zanussi@intel.com>
To: James Abernathy <jfabernathy@gmail.com>
Cc: "yocto@yoctoproject.org" <yocto@yoctoproject.org>
Subject: Re: Build error while following Appendix A. Yocto Project Development manual
Date: Tue, 01 Nov 2011 14:55:41 -0500	[thread overview]
Message-ID: <1320177341.2400.65.camel@elmorro> (raw)
In-Reply-To: <CANFv2Emacwk4+Z+bYNs3MXZL-uxHmPUiB5tFXNM7Kx+NgFOnig@mail.gmail.com>

On Tue, 2011-11-01 at 12:48 -0700, James Abernathy wrote:
> Just to clear up the basics, Prior to following Appendix A verbatim, I
> did the following
> 1. install prerequisites from GS guide
> 2. git clone git://git.yoctoproject.org/poky
> 3. cd poky
> 4. git clone git://git.yoctoproject.org/meta-intel.git
>  
> I did not install the poky-extras. I assumed it only had to be
> installed if you installed the kernel source for modification like in
> Appendix b
>  

Yeah, normally, assuming you're using an existing kernel branch.  But
you didn't get a build error for the kernel, so I'm assuming that's the
case.

Tom

> Jim a
> 
> 
> 
>  
> On Tue, Nov 1, 2011 at 3:40 PM, Tom Zanussi <tom.zanussi@intel.com>
> wrote:
>         Hi,
>         
>         On Tue, 2011-11-01 at 11:37 -0700, James Abernathy wrote:
>         > I tried to duplicate the Yocto Project Decelopment Manual
>         Appendix A
>         > build of a Crownbay NOEMGD image,  no changes just dulicate
>         the
>         > instructions.  This is using the latest Yocto 1.1.  I did
>         get a long
>         > way down the line, but had a fatal error in the last 2
>         steps.
>         >
>         > The only change I had to make was related to A.5.2.4.  The
>         commit
>         > string for the SRCREV_meta_pn was different on the
>         > git.yoctoproject.org/cgit/cgi for the Meta commit so I used
>         what I
>         > found online.  The first section of 126 task completed
>         without error.
>         > The next section of 4394 tasks failed on 4393.  Not sure if
>         the error
>         > is obvious, but I wanted to run it by someone. Console error
>         log
>         > below:
>         >
>         
>         
>         Hmm, not sure what's going on here - I'm sure this example was
>         verified
>         several times, but just to make sure, what you're doing is
>         going through
>         'Appendix A. BSP Development Example' verbatim and getting
>         this?
>         
>         The SRCREVs in either case look ok for this, so that shouldn't
>         be the
>         problem...
>         
>         But let me go over the steps myself and see what I come up
>         with - will
>         let you know either way...
>         
>         Tom
>         
>         
>         >  NOTE: package core-image-sato-1.0-r0: task do_bootimg:
>         Started
>         > ERROR: Function 'build_boot_bin' failed
>         >
>         (see /home/jim/poky/yocto-build/tmp/work/mymachine-poky-linux/core-image-sato-1.0-r0/temp/log.do_bootimg.31418 for further information)
>         > ERROR: Logfile of failure stored
>         >
>         in: /home/jim/poky/yocto-build/tmp/work/mymachine-poky-linux/core-image-sato-1.0-r0/temp/log.do_bootimg.31418
>         > Log data follows:
>         > | install: cannot stat
>         >
>         `/home/jim/poky/yocto-build/tmp/sysroots/mymachine/kernel/bzImage': No
>         > such file or directory
>         > | ERROR: Function 'build_boot_bin' failed
>         >
>         (see /home/jim/poky/yocto-build/tmp/work/mymachine-poky-linux/core-image-sato-1.0-r0/temp/log.do_bootimg.31418 for further information)
>         > NOTE: package core-image-sato-1.0-r0: task do_bootimg:
>         Failed
>         > ERROR: Task 9
>         > (/home/jim/poky/meta/recipes-sato/images/core-image-sato.bb,
>         > do_bootimg) failed with exit code '1'
>         > ERROR:
>         '/home/jim/poky/meta/recipes-sato/images/core-image-sato.bb'
>         > failed
>         > jim@jim-ubuntu-10:~/poky/yocto-build$
>         >
>         
>         
>         
> 




  reply	other threads:[~2011-11-01 19:55 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 [this message]
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
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=1320177341.2400.65.camel@elmorro \
    --to=tom.zanussi@intel.com \
    --cc=jfabernathy@gmail.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.