From: Martin Jansa <martin.jansa@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Execution of Build Output Failing (Testing)
Date: Fri, 27 Aug 2010 23:42:40 +0200 [thread overview]
Message-ID: <20100827214240.GI17268@jama> (raw)
In-Reply-To: <1282944796856928500@rkmorris.us>
On Fri, Aug 27, 2010 at 04:33:16PM -0500, openembedded@rkmorris.us wrote:
> Hi,
>
>
>
> I am running a build with Angstrom, and I receive the following error messages - is this expected (and is there a fix for this?)?
>
>
>
> NOTE: Handling BitBake files: \ (0754/7160) [10 %]NOTE: Angstrom DOES NOT support bluez-libs because bluez-libs 3.x has been replaced by bluez4
> NOTE: Handling BitBake files: \ (0960/7160) [13 %]NOTE: Angstrom DOES NOT support bluez-utils because bluez-utils 3.x has been replaced by bluez4
> NOTE: Handling BitBake files: \ (0970/7160) [13 %]NOTE: Angstrom DOES NOT support ipkg because ipkg has been superseded by opkg
> NOTE: Handling BitBake files: | (1191/7160) [16 %]NOTE: Angstrom DOES NOT support libiconv because the glibc builtin iconv replacement is used
> NOTE: Handling BitBake files: \ (1404/7160) [19 %]NOTE: Angstrom DOES NOT support libiconv because the glibc builtin iconv replacement is used
> NOTE: Handling BitBake files: | (4881/7160) [68 %]NOTE: Angstrom DOES NOT support bluez-utils because bluez-utils 3.x has been replaced by bluez4
> NOTE: Handling BitBake files: | (5731/7160) [80 %]NOTE: Angstrom DOES NOT support bluez-libs because bluez-libs 3.x has been replaced by bluez4
> NOTE: Handling BitBake files: \ (5964/7160) [83 %]NOTE: Angstrom DOES NOT support libiconv because the glibc builtin iconv replacement is used
> NOTE: Handling BitBake files: - (6038/7160) [84 %]NOTE: Angstrom DOES NOT support fso-apm because regular apmd is good enough
> NOTE: Handling BitBake files: - (6508/7160) [90 %]NOTE: Angstrom DOES NOT support bluez-libs because bluez-libs 3.x has been replaced by bluez4
> NOTE: Handling BitBake files: \ (7160/7160) [100 %]
Those are not error messages, just note that some packages are
blacklisted, see ie:
ANGSTROM_BLACKLIST_pn-bluez-libs = "bluez-libs 3.x has been replaced by bluez4"
etc in distro configs like conf/distro/angstrom-2010.x.conf
So it's expected.
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
next prev parent reply other threads:[~2010-08-27 21:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-27 20:26 Execution of Build Output Failing (Testing) openembedded
2010-08-27 21:27 ` openembedded
[not found] ` <1282944796856928500@rkmorris.us>
2010-08-27 21:42 ` Martin Jansa [this message]
2010-08-28 13:42 ` openembedded
2010-08-29 13:34 ` openembedded
-- strict thread matches above, loose matches on Subject: below --
2010-08-27 12:15 [RFC] review process Frans Meulenbroeks
2010-08-27 13:46 ` Execution of Build Output Failing (Testing) openembedded
2010-08-27 17:41 ` Khem Raj
2010-08-27 19:37 ` openembedded
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=20100827214240.GI17268@jama \
--to=martin.jansa@gmail.com \
--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