From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of build results for 2015-08-18
Date: Mon, 31 Aug 2015 16:42:45 +0200 [thread overview]
Message-ID: <20150831164245.1a25a5a9@free-electrons.com> (raw)
In-Reply-To: <CA+BsyQ6a=2Lt5Q8XGmT4EegWFnj1b6FeV_EU3KNRGUTXx5PCtg@mail.gmail.com>
Dear Brendan Heading,
On Fri, 21 Aug 2015 12:38:33 +0100, Brendan Heading wrote:
> > 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.
>
> Understood. Would you like me to put together a "disable libtirpc on
> SPARC" patch then ?
I think we'll just ship 2015.08 with the SPARCv8 breakage on libtirpc.
I must admit I'm not sure what to do with SPARCv8. Should we simply
deprecate it, and if someone complain, ask that someone to help
maintaining the platform?
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2015-08-31 14:42 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
2015-08-21 11:38 ` Brendan Heading
2015-08-31 14:42 ` Thomas Petazzoni [this message]
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=20150831164245.1a25a5a9@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