Poky Project Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Zhang, Jessica" <jessica.zhang@intel.com>
Cc: "poky@yoctoproject.org" <poky@yoctoproject.org>
Subject: Re: poky-image-sato-sdk failed at do_rootfs
Date: Tue, 01 Feb 2011 11:55:16 +0000	[thread overview]
Message-ID: <1296561316.13501.18767.camel@rex> (raw)
In-Reply-To: <9AFCD584B0B67B48AE8D8585BE30BA9506C267B0@orsmsx504.amr.corp.intel.com>

Hi Jessica,

On Mon, 2011-01-31 at 16:58 -0800, Zhang, Jessica wrote:
> Some update with recent do_package racing condition triggered build issues.
> Today, I've cherry-picked 3 related commits: Kevin's fix for rebuild,
> Richard's fix for change PACKAGE_CLASSES and do_package_write* depends on
> libc do_package and did the following test builds:
> 1. bitbake poky-image-minimal (incremental)
> 2. bitbake poky-image-sato-sdk (incremental)
> 3. switch PACKAGE_CLASSES setting, then bitbake poky-image-minimal
> Everything behaved as desired so far.  Then I did
> 4. bitbake libgcc virtual/libc -c package -f 
> 5. bitbake poky-image-minimal and stumbled on the eglibc depencies issues
> again, then Richard suggest me to make the following change:
> http://git.pokylinux.org/cgit.cgi/poky-contrib/commit/?h=jzhang/eglibc_issue
> , which solved my build issues.

I've tried locally and I cannot reproduce this problem any more with
master. I'm wondering if there is some kind of caches state problem
within your build which is causing this?

I don't think the above patch I've proposed is correct.

Cheers,

Richard




  reply	other threads:[~2011-02-01 11:55 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-30  1:33 poky-image-sato-sdk failed at do_rootfs Zhang, Jessica
2011-01-30  2:00 ` Cui, Dexuan
2011-01-30  7:16   ` Zhang, Jessica
2011-01-30  7:46   ` Lu, Lianhao
2011-01-30  7:58     ` Zhang, Jessica
2011-01-30  8:05       ` Cui, Dexuan
2011-01-30  8:16     ` Lu, Lianhao
2011-01-30  8:26       ` Zhang, Jessica
2011-01-30 10:13 ` Richard Purdie
2011-01-30 12:20   ` Tian, Kevin
2011-01-30 14:49     ` Lu, Lianhao
2011-01-31 15:24       ` Lu, Lianhao
2011-01-31 16:40         ` Richard Purdie
2011-02-01  0:58           ` Zhang, Jessica
2011-02-01 11:55             ` Richard Purdie [this message]
2011-02-01 13:07               ` Zhang, Jessica
2011-02-01 13:32                 ` Richard Purdie
2011-02-01 19:27                   ` Wolfgang Denk
2011-02-01 20:00                     ` Mark Hatle
2011-02-01 22:08                       ` Wolfgang Denk
2011-02-01 23:29                     ` Richard Purdie
2011-02-02  7:03                       ` Wolfgang Denk
2011-02-02 11:18                         ` Richard Purdie
2011-02-02 11:33                           ` Wolfgang Denk
2011-02-02 13:56                             ` Mark Hatle
2011-02-02 14:05                               ` Wolfgang Denk
2011-02-02 14:06                               ` Richard Purdie
2011-02-02 14:56                                 ` Mark Hatle

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=1296561316.13501.18767.camel@rex \
    --to=richard.purdie@linuxfoundation.org \
    --cc=jessica.zhang@intel.com \
    --cc=poky@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox