From: Steffen Sledz <sledz@dresearch-fe.de>
To: openembedded-devel <openembedded-devel@lists.openembedded.org>
Subject: Re: [2011.03-maintenance] unsatisfied dependencies to libgcc
Date: Fri, 05 Aug 2011 08:05:58 +0200 [thread overview]
Message-ID: <4E3B8846.2080203@dresearch-fe.de> (raw)
In-Reply-To: <4E3A3C4B.8040208@dresearch-fe.de>
On 04.08.2011 08:29, Steffen Sledz wrote:
> In the last days we switched our local development from an older oe-dev master to 2011.03-maintenance branch and hit an annoying problem.
>
> The test builds on various developer machines were successful but the build on our continuous integration server (with exactly the same scripting) ended up with a lot of
>
> | * satisfy_dependencies_for: Cannot satisfy the following dependencies for lighttpd:
> | * libstdc++6 (>= 4.3.3) * libgcc1 (>= 4.3.3) * libgcc1 (>= 4.3.3) *
> | * opkg_install_cmd: Cannot install package lighttpd.
>
> errors.
>
> After some searching we found that there was no libgcc1_4.3.3-r24.2.6_armv5te.ipk in the deploy area.
>
> I'm not sure which package should produce this but i guess it should come from gcc-cross-4.3.3 (because its recipe version is r24.2.6 in opposite to gcc-4.3.3 r24.1.6).
>
> Looking into the log i hit the fact that the do_rootfs stage for the image was started *before* the do_package_stage of gcc-cross_4.3.3.bb was succeeded.
>
> Any ideas?
>
> PS: Bitbaking gcc-cross explicitly before bitbaking the image wors as a workaround for us at the moment.
Another collegue had a similar problem while bitbaking meta-toolchain.
| * satisfy_dependencies_for: Cannot satisfy the following dependencies for task-sdk-bare:
| * libstdc++-dev *
| * opkg_install_cmd: Cannot install package task-sdk-bare.
So it seems it is not a problem of our image recipe.
--
DResearch Fahrzeugelektronik GmbH
Otto-Schmirgal-Str. 3, 10319 Berlin, Germany
Tel: +49 30 515932-237 mailto:sledz@dresearch-fe.de
Fax: +49 30 515932-299
Geschäftsführer: Dr. Michael Weber, Werner Mögle;
Amtsgericht Berlin Charlottenburg; HRB 130120 B;
Ust.-IDNr. DE273952058
next prev parent reply other threads:[~2011-08-05 6:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-04 6:29 [2011.03-maintenance] unsatisfied dependencies to libgcc Steffen Sledz
2011-08-05 6:05 ` Steffen Sledz [this message]
2011-08-05 7:13 ` Steffen Sledz
2011-08-07 17:37 ` Steffen Sledz
2011-08-07 20:46 ` Tom Rini
2011-08-09 9:23 ` Steffen Sledz
2011-08-09 10:15 ` Steffen Sledz
2011-08-11 8:27 ` Steffen Sledz
2011-08-11 14:30 ` Khem Raj
2011-08-12 5:56 ` Steffen Sledz
2011-08-19 9:11 ` Steffen Sledz
2011-08-19 14:21 ` Khem Raj
2011-08-19 14:27 ` Steffen Sledz
2011-08-19 14:38 ` Steve Sakoman
2011-08-19 15:29 ` Khem Raj
2011-08-19 15:32 ` Steve Sakoman
2011-08-19 16:29 ` Khem Raj
2011-08-19 17:29 ` Steve Sakoman
2011-08-18 21:44 ` Steve Sakoman
2011-08-18 21:52 ` Steve Sakoman
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=4E3B8846.2080203@dresearch-fe.de \
--to=sledz@dresearch-fe.de \
--cc=openembedded-devel@lists.openembedded.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