From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: "Lu, Lianhao" <lianhao.lu@intel.com>
Cc: "poky@yoctoproject.org" <poky@yoctoproject.org>
Subject: Re: poky-image-sato-sdk failed at do_rootfs
Date: Mon, 31 Jan 2011 16:40:09 +0000 [thread overview]
Message-ID: <1296492009.13501.13668.camel@rex> (raw)
In-Reply-To: <C10D3FB0CD45994C8A51FEC1227CE22F20F8C32C7C@shsmsx502.ccr.corp.intel.com>
On Mon, 2011-01-31 at 23:24 +0800, Lu, Lianhao wrote:
> Lu, Lianhao wrote on 2011-01-30:
> > Tian, Kevin wrote on 2011-01-30:
> > Here is what I found using the master with the latest commit
> > ffd12fc476d6061ba1e019a1e789cf1a2d3c82e6.
> >
> > 1. set PACKAGE_CLASSES to "package_rpm package_ipk" and target machine
> > to "qemumips" in conf/local.conf 2. bitbake poky-image-minimal from
> > scratch, then bitbake meta-toolchain incrementally. Both got built successfully.
> > 3. set PACKAGE_CLASSES to "package_ipk package_rpm"
> > 4. bitbake poky-image-minimal incrementally, and it succeeded.
> > 5. bitbake meta-toolchain incrementally, it failed complaining about
> > unsatisfied dependencies to eglibc during opkg installation. See
> > attached file "log.do_populate_sdk" for details. This failure is then reproducible every time.
> > 6. set PACKAGE_CLASSES back to "package_rpm package_ipk"
> > 7. bitbake poky-image-minimal incrementally, it failed complaining
> > about unsatisfied dependencies to eglibc during rpm installation. See
> > attached file "log.do_rootfs" for details. This failure is then reproducible every time.
> >
>
> Just as Richard said, we've confirmed that this issue was caused by a
> race problem. We saw this issue because the libgcc's
> do_package_write_xxx task got executed before the eglibc's do_pacakge
> task finished. This problem might be there for some time, but somehow
> it was not exposed until the recent commit of adding a non stamp task
> do_populate_lic.(see the email chain named after "summary about recent
> do_populate_sdk failures" for details). We should add dependency so
> that the task package_write_xxx of libgcc and libstdc++ is dependent
> upon "virtual/libc:do_package".
>
> Is there any package other than libgcc and gcc-runtime have such race
> problem with libc? I think many packages are implicitly dependent on
> virtual/libc, how those packages do_package_write_xxx's dependency
> upon libc's do_package get assured?
debian.bbclass ensures that things don't package until all a package's
dependencies have packaged:
do_package_write_ipk[rdeptask] = "do_package"
do_package_write_deb[rdeptask] = "do_package"
do_package_write_tar[rdeptask] = "do_package"
do_package_write_rpm[rdeptask] = "do_package"
This doesn't work in the special case of libgcc and libc since the cross
compiler bootstrap process confuses the dependency issues a lot. We need
to inject some manual dependencies at that point. We could probably even
make it RDEPENDS on libc but at this point I'm going to manually create
these dependencies to be safe and make the code clearer:
http://git.pokylinux.org/cgit.cgi/poky/commit/?id=21f2dae46b481dbf34f6874ae814dcd23fc86d54
Cheers,
Richard
next prev parent reply other threads:[~2011-01-31 16:40 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 [this message]
2011-02-01 0:58 ` Zhang, Jessica
2011-02-01 11:55 ` Richard Purdie
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=1296492009.13501.13668.camel@rex \
--to=richard.purdie@linuxfoundation.org \
--cc=lianhao.lu@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 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.