All of 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 2016-05-16
Date: Wed, 18 May 2016 23:54:26 +0200	[thread overview]
Message-ID: <20160518235426.785ae8c1@free-electrons.com> (raw)
In-Reply-To: <8a1534c8-494c-2470-dcb3-f45b6da6f208@mind.be>

Hello,

On Wed, 18 May 2016 21:40:38 +0200, Arnout Vandecappelle wrote:

>   In my opinion, ICE issues are not really our problem. Since the user can 
> configure any kind of toolchain combination, I don't think it makes a whole lot 
> of sense even to add dependencies in the Config.in to avoid broken toolchains 
> (like we used to have for BR2_TOOLCHAIN_EXTERNAL_CODESOURCERY_NIOSII).
> 
>   So I'd just add an autobuilder exception.

I'm hesitant to do this, because it means that normal users can also
fall into the problem.

On the other hand, it's annoying to encode all those exceptions in
Buildroot itself.

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

  reply	other threads:[~2016-05-18 21:54 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-17  6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2016-05-16 Thomas Petazzoni
2016-05-17 13:36 ` [Buildroot] Analysis of build " Thomas Petazzoni
2016-05-17 13:53   ` Rodrigo Rebello
2016-05-17 15:13   ` gwenhael.goavec
2016-05-17 15:20     ` Thomas Petazzoni
2016-05-18  7:09       ` gwenhael.goavec
2016-05-18 19:40         ` Arnout Vandecappelle
2016-05-18 21:54           ` Thomas Petazzoni [this message]
2016-05-18 22:15             ` Arnout Vandecappelle
2016-05-17 16:27   ` Bernd Kuhls
2016-05-17 18:47   ` Bernd Kuhls
2016-05-17 18:56   ` Geoff Levand
2016-05-17 19:34     ` Thomas Petazzoni
2016-05-17 20:15       ` Geoff Levand
2016-05-17 21:03   ` Yegor Yefremov
2016-05-17 21:06     ` Yegor Yefremov
2016-05-18 19:33   ` Samuel Martin
2016-05-19 13:26   ` Gustavo Zacarias
2016-05-19 18:52   ` Gustavo Zacarias
2016-05-19 21:31     ` Arnout Vandecappelle
2016-05-20  7:35       ` Thomas Petazzoni
2016-05-25 14:44   ` Clayton Shotwell
2016-06-17  1:21   ` Ben Boeckel
2016-06-17  2:11     ` Ben Boeckel

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=20160518235426.785ae8c1@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 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.