All of lore.kernel.org
 help / color / mirror / Atom feed
From: Sander van Grieken <sander@3v8.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Reproducible builds (Was Re: Checksums in Bitbake)
Date: Mon, 29 Mar 2010 12:42:22 +0200	[thread overview]
Message-ID: <201003291242.22230.sander@3v8.net> (raw)
In-Reply-To: <1269714709.2382.6.camel@gnutoo-desktop>

On Saturday 27 March 2010 19:31:49 GNUtoo wrote:
> On Thu, 2010-03-25 at 08:45 +0100, Frans Meulenbroeks wrote:
> > I've seen too often (also outside OE) that two engineers take the same
> > source yet still get different results, and that bugs at a customer
> > site cannot be reproduced in the lab (and yes, I do know there are
> > other ways to tackle this problem) 
> Also:
> bitbake optionaldep
> bitbake package
> And:
> bitbake package
> 
> could result in different binaries/packages due to configure picking
> optionaldep in the first case and not in the second one.

So, building any of the *-image recipes is non-deterministic, if it pulls in optional deps 
for other recipes? It then comes down to the build-queue ordering, which is probably not 
guaranteed to have a predictable order, especially with a high number of parallel bitbake 
threads.

Sounds like there's a need for something similar to Gentoo's USE flags.

grtz,
Sander



      parent reply	other threads:[~2010-03-29 10:51 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-24 13:27 Checksums in Bitbake Richard Purdie
2010-03-24 15:15 ` Frans Meulenbroeks
2010-03-24 15:51   ` Chris Larson
2010-03-24 20:17     ` Frans Meulenbroeks
2010-03-24 21:46       ` Richard Purdie
2010-03-25  7:45         ` Frans Meulenbroeks
2010-03-27 18:31           ` Reproducible builds (Was Re: Checksums in Bitbake) GNUtoo
2010-03-27 18:54             ` Tom Rini
2010-03-27 19:14               ` Koen Kooi
2010-03-29 10:42             ` Sander van Grieken [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=201003291242.22230.sander@3v8.net \
    --to=sander@3v8.net \
    --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 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.