From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@openembedded.org
Subject: Re: Bitbake Request for Testing of bitbake 1.8
Date: Fri, 09 Mar 2007 11:09:09 +0000 [thread overview]
Message-ID: <1173438550.5864.57.camel@localhost.localdomain> (raw)
In-Reply-To: <200703091033.41288.christopher.lang@plus.cablesurf.de>
On Fri, 2007-03-09 at 10:33 +0100, Christopher Lang wrote:
> This is the output without -v without the 'GLIBC_ADDONS = "nptl"'. The "triple
> glibc" note does not show.
>
> http://pastebin.ca/387372
>
>
> This one is the original output (without the 'GLIBC_ADDONS = "nptl"') but with
> -v. Only there you can see the line:
> NOTE: multiple preferred providers are available for runtime libsegfault
> (glibc, glibc, glibc);
>
> http://pastebin.ca/387374
>
> I thought that multiple identical PREFERRED_PROVIDERS might indicate an issue.
That just looks like the new logic in bitbake working as expected (it
examined all possible libc providers of which there were probably 3,
each one gave a messge). Yes, the output could be more friendly/readable
but that is an on going problem to be revisited during the UI overhaul.
Bitbake 1.6 would do something similar if it had tried to build all 3
glibc providers.
Cheers,
Richard
prev parent reply other threads:[~2007-03-09 11:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-05 21:55 Bitbake Request for Testing of bitbake 1.8 Richard Purdie
2007-03-06 4:15 ` Mark Gross
2007-03-07 9:20 ` Richard Purdie
2007-03-07 14:05 ` Henning Heinold
2007-03-07 11:17 ` Christopher Lang
2007-03-07 14:26 ` Richard Purdie
2007-03-08 19:46 ` Christopher Lang
2007-03-08 20:26 ` Christopher Lang
2007-03-08 22:31 ` Richard Purdie
2007-03-09 9:33 ` Christopher Lang
2007-03-09 11:09 ` Richard Purdie [this message]
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=1173438550.5864.57.camel@localhost.localdomain \
--to=rpurdie@rpsys.net \
--cc=openembedded-devel@lists.openembedded.org \
--cc=openembedded-devel@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 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.