All of lore.kernel.org
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Andreas Schultz <aschultz@tpip.net>
Cc: poky@yoctoproject.org
Subject: Re: how to detect unstable builds
Date: Wed, 30 Jul 2014 15:20:33 +0100	[thread overview]
Message-ID: <1406730033.13346.146.camel@ted> (raw)
In-Reply-To: <551317585.6654.1406729428858.JavaMail.zimbra@tpip.net>

On Wed, 2014-07-30 at 14:10 +0000, Andreas Schultz wrote:
> Hi,
> 
> Unstable might be not the right term, but I couldn't think of another.
> 
> The issue is that two builds on exactly the same build host, produce
> packages that have different runtime dependencies and also different
> behaviors.
> 
> I encountered this problem with readline, but other package might have
> it as well.
> 
> I try to build an image that contains systemd and (an modified) bind. The
> declared dependencies of systemd contain readline, those of my version of
> bind do not. With multiple parallel task, build order is not guaranteed
> and bind might be build before or after readline.
> 
> bind's autoconf does check for readline and will link bind to it if
> it finds it.
> 
> The outcome is that some builds contain a bind linked against readline,
> while other contain a bind that is not linked against readline.
> 
> ** QA hell breaks loose **
> 
> Is there a way to detect and/or prevent situations like this?

If linkage to a library that is not in DEPENDS happens, there is new
code which should detect this:

http://git.yoctoproject.org/cgit.cgi/poky/commit/?id=a202f8a66383787c899246c5fa14c862e5d7647d

Its not perfect but it should be better than we've ever had before and
is a start...

Cheers,

Richard



  reply	other threads:[~2014-07-30 14:20 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1733425688.6639.1406728610529.JavaMail.zimbra@tpip.net>
2014-07-30 14:10 ` how to detect unstable builds Andreas Schultz
2014-07-30 14:20   ` Richard Purdie [this message]
2014-07-30 14:31   ` 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=1406730033.13346.146.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=aschultz@tpip.net \
    --cc=poky@yoctoproject.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.