All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] boost: correctly disable icu in locale if needed
Date: Mon, 8 Apr 2019 09:21:12 +0200	[thread overview]
Message-ID: <20190408092112.043f6885@windsurf> (raw)
In-Reply-To: <CAMo8Bf+a5JZcfG4JGibU6icFbMN0SdDiTfRidD9wRYk2dxf2gg@mail.gmail.com>

Hello Max,

On Sun, 7 Apr 2019 14:09:18 -0700
Max Filippov <jcmvbkbc@gmail.com> wrote:

> > I didn't see that. Will take a look at the ICE on xtensa.  
> 
> Hmmm... Does not reproduce here, the build is successful. Puzzled.

Of all the failures in:

  http://autobuild.buildroot.net/?reason=boost%&arch=xtensa

the internal compiler error happened only once. Did you try rebuilding
with that exact configuration and Git commit ?

If you indeed reproduced with the same config and Git commit, then it
can be:

 1. Influence from the environment (i.e the build machine is different)
 2. The build machine is flaky and causes random failures

If needed, we can always ask Richard Braun to try to reproduce the same
build on his machine, in order to discriminate between (1) and (2).

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

  reply	other threads:[~2019-04-08  7:21 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-13 17:42 [Buildroot] [PATCH 1/1] boost: correctly disable icu in locale if needed Fabrice Fontaine
2018-07-14 20:41 ` Thomas Petazzoni
2018-07-14 21:04   ` Fabrice Fontaine
2018-07-14 21:21     ` Thomas Petazzoni
2019-04-07 20:25 ` Thomas Petazzoni
2019-04-07 20:39   ` Fabrice Fontaine
2019-04-07 20:45   ` Max Filippov
2019-04-07 21:09     ` Max Filippov
2019-04-08  7:21       ` Thomas Petazzoni [this message]
2019-04-08 15:53         ` Max Filippov

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=20190408092112.043f6885@windsurf \
    --to=thomas.petazzoni@bootlin.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.