All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <rpurdie@rpsys.net>
To: openembedded-devel@openembedded.org
Subject: Re: [RFC] Stop on multiple providers but none explicitly	specified
Date: Thu, 15 May 2008 17:42:06 +0100	[thread overview]
Message-ID: <1210869726.7097.93.camel@localhost.localdomain> (raw)
In-Reply-To: <c384c5ea0805141436m9f5151dje832c2da95379127@mail.gmail.com>

On Wed, 2008-05-14 at 23:36 +0200, Leon Woestenberg wrote:
> Hello all,
> 
> in trying to explain a new user why his build fails, it was the
> classic situation of multiple providers available but non specified:
> 
> NOTE: multiple providers are available for virtual/libc
> (external-toolchain, uclibc);
> NOTE: consider defining PREFERRED_PROVIDER_virtual/libc
> 
> Now, as far as I know, this makes the build non-deterministic, because
> bitbake "just" chooses one.
> 
> Why do we want this behaviour? I cannot see any benefit in this situation.
> 
> We should at least prefer one over the other, or just bail out in my opinion.

Bitbake will pick one, the options in brackets are in the order bitbake
will choose them. We sort them alphabetically iirc since that is more
deterministic than depending on parsing order which was the previous
approach.

Cheers,

Richard




  reply	other threads:[~2008-05-15 16:44 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-05-14 21:36 [RFC] Stop on multiple providers but none explicitly specified Leon Woestenberg
2008-05-15 16:42 ` Richard Purdie [this message]
2008-05-15 18:38   ` Tom Rini
2008-05-15 18:51   ` Leon Woestenberg
2008-05-15 20:11     ` Tom Rini
2008-05-15 20:50       ` Leon Woestenberg
2008-05-15 22:06         ` Tom Rini
2008-05-15 22:25         ` Koen Kooi
2008-05-15 21:45     ` Richard Purdie
2008-05-16 21:44       ` Leon Woestenberg
2008-05-17 21:59         ` Richard Purdie
2008-05-18 22:48           ` Leon Woestenberg
2008-05-19  8:38             ` Richard Purdie

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=1210869726.7097.93.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.