Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of build results for 2015-08-18
Date: Fri, 21 Aug 2015 10:46:22 +0200	[thread overview]
Message-ID: <20150821104622.3abb16d1@free-electrons.com> (raw)
In-Reply-To: <CA+BsyQ7iPgOxOOY+vi09shjAJMhkaFQBcfe6EEJxmX_kVPh21A@mail.gmail.com>

Dear Brendan Heading,

On Wed, 19 Aug 2015 22:56:44 +0100, Brendan Heading wrote:

> > Peter, what do you suggest we do about these issues for the release?
> > Long-term, libtirpc will be changed to not use atomic builtins. But
> > what do we do now? Mark libtirpc as not available on SPARCv8, and
> > propagate the reverse dependency?
> 
> Can I suggest that you just leave it broken ?

Leaving things broken in the autobuilders is annoying. For two reasons:

 1/ Due to this Busybox failure on SPARC, many SPARC builds abort at
    this point, and we don't see other SPARC failures.

 2/ It leaves some "noise" in the build results, and due to this it's
    hard to distinguish the build failures that should be investigated
    from the ones that are already analyzed.

> I suspect it's been
> broken for a little while. The problem in libtirpc was a commit in
> 2011, which would have first been seen in stable release 0.2.3 in
> 2013. We jumped from 0.2.2 to 0.2.4 on 26 Jun 2014 (f2ac23454) so each
> release since then will have had this problem. A simple workaround in
> the short term is simply to turn off libtirpc on SPARC manually.

Testing SPARC in the autobuilders is fairly recent, that's why we're
only tackling this problem now.

> It will take another week or so to sort this out as we're waiting for
> the person who committed the change in the first place (in 2011) to
> return from vacation so he can comment on it. The fix should be ready
> by the end of the month assuming no objections are raised.

I doubt we can get this merged for 2015.08, though. It will probably be
2015.11 material.

In any case, thanks a lot for working on this libtirpc topic, it has
been around for a while, so it's good to have someone looking into this!

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  parent reply	other threads:[~2015-08-21  8:46 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-08-19  6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2015-08-18 Thomas Petazzoni
2015-08-19  8:10 ` Vicente Olivert Riera
2015-08-19 20:41 ` [Buildroot] Analysis of build " Thomas Petazzoni
2015-08-19 21:56   ` Brendan Heading
2015-08-20  6:18     ` Peter Korsgaard
2015-08-20 11:31       ` Brendan Heading
2015-08-21  8:46     ` Thomas Petazzoni [this message]
2015-08-21 11:38       ` Brendan Heading
2015-08-31 14:42         ` Thomas Petazzoni
2015-08-19 22:55   ` Yann E. MORIN

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=20150821104622.3abb16d1@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=buildroot@busybox.net \
    /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