From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: Does support for external toolchains working in current OE?
Date: Fri, 05 Apr 2013 10:54:18 +0100 [thread overview]
Message-ID: <1365155658.6526.136.camel@ted> (raw)
In-Reply-To: <515E976C.8060302@linaro.org>
On Fri, 2013-04-05 at 11:20 +0200, Marcin Juszkiewicz wrote:
> For last few months I am working on fixing Linaro binary cross
> toolchains and their support in OpenEmbedded. Got to point when they
> work (both AArch64 and ARMv7a ones) for single packages but problem
> starts when I want to create image...
>
> 11:14 hrw@puchatek:build$ bitbake core-image-minimal -g
> Parsing of 1302 .bb files complete (1294 cached, 8 parsed). 1670 targets, 45 skipped, 0 masked, 0 errors.
> NOTE: Resolving any missing task queue dependencies
> NOTE: multiple providers are available for virtual/gettext (proxy-libintl, gettext)
> NOTE: consider defining a PREFERRED_PROVIDER entry to match virtual/gettext
> NOTE: Preparing runqueue
> ERROR: Multiple .bb files are due to be built which each provide virtual/libc (/home/hrw/HDD/devel/canonical/aarch64/openembedded/repos/openembedded-core/meta/recipes-core/eglibc/eglibc_2.17.bb /home/hrw/HDD/devel/canonical/aarch64/openembedded/repos/meta-linaro/meta-linaro-toolchain/recipes-devtools/external-linaro-toolchain/external-linaro-toolchain.bb).
> This usually means one provides something the other doesn't and should.
> ERROR: Multiple .bb files are due to be built which each provide virtual/arm-linux-gnueabihf-libc-for-gcc (/home/hrw/HDD/devel/canonical/aarch64/openembedded/repos/openembedded-core/meta/recipes-core/eglibc/eglibc_2.17.bb /home/hrw/HDD/devel/canonical/aarch64/openembedded/repos/meta-linaro/meta-linaro-toolchain/recipes-devtools/external-linaro-toolchain/external-linaro-toolchain.bb).
> This usually means one provides something the other doesn't and should.
> ERROR: Multiple .bb files are due to be built which each provide virtual/libiconv (/home/hrw/HDD/devel/canonical/aarch64/openembedded/repos/openembedded-core/meta/recipes-core/eglibc/eglibc_2.17.bb /home/hrw/HDD/devel/canonical/aarch64/openembedded/repos/meta-linaro/meta-linaro-toolchain/recipes-devtools/external-linaro-toolchain/external-linaro-toolchain.bb).
> This usually means one provides something the other doesn't and should.
> NOTE: PN build list saved to 'pn-buildlist'
> NOTE: PN dependencies saved to 'pn-depends.dot'
> NOTE: Package dependencies saved to 'package-depends.dot'
> NOTE: Task dependencies saved to 'task-depends.dot'
>
> Summary: There were 3 ERROR messages shown, returning a non-zero exit code.
>
> All three virtual/ are provided by external-linaro-toolchain recipe...
>
> Is there any external toolchain which allows to create image with current
> OpenEmbedded layers?
>
> TCMODE="external-sourcery" gives exactly same problem.
This means that virtual/libc is providing something which the external
toolchain recipes are not. Can you share the "bitbake -DDDv" output for
the above command somewhere (I know there will be a lot of it). Buried
somewhere in there will be the answer as it does tell you what is going
on if you search for the right things.
Cheers,
Richard
next prev parent reply other threads:[~2013-04-05 10:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-05 9:20 Does support for external toolchains working in current OE? Marcin Juszkiewicz
2013-04-05 9:26 ` Marcin Juszkiewicz
2013-04-05 9:54 ` Richard Purdie [this message]
2013-04-05 9:56 ` Marcin Juszkiewicz
2013-04-05 10:11 ` Richard Purdie
2013-04-05 11:48 ` Marcin Juszkiewicz
2013-04-05 12:21 ` Marcin Juszkiewicz
2013-04-05 12:26 ` Marcin Juszkiewicz
2013-04-05 12:31 ` Richard Purdie
2013-04-05 21:20 ` Martin Jansa
2013-04-05 22:08 ` Chris Larson
2013-04-05 22:10 ` Martin Jansa
2013-04-06 12:43 ` Martin Jansa
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=1365155658.6526.136.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=marcin.juszkiewicz@linaro.org \
--cc=openembedded-core@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