From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2016-11-05
Date: Mon, 7 Nov 2016 21:53:50 +0100 [thread overview]
Message-ID: <20161107215350.1bd07849@free-electrons.com> (raw)
In-Reply-To: <20161107182531.GB27313@waldemar-brodkorb.de>
Hello,
On Mon, 7 Nov 2016 19:25:31 +0100, Waldemar Brodkorb wrote:
> > Waldemar, this is a compiler segfault, on mainline gcc for Blackfin.
> > Anything we can do?
>
> Last time I checked I suggested to disable it for bfin.
> But now I found a simple patch which avoids the segfault. I try to
> find a simple test case to report the issue upstream.
> Do you want me to sent a patch fixing the build issue without a bug
> report?
Yes, please. This will allow to get rid of one more autobuilder failure.
> > > m68k | xmlstarlet-1.6.1 | NOK | http://autobuild.buildroot.net/results/02f9fc5884d3a7d460b96937183362d6c3fc6fde
> >
> > Link issue. Waldemar?
>
> Patch sent.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
prev parent reply other threads:[~2016-11-07 20:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-06 7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2016-11-05 Thomas Petazzoni
2016-11-06 13:39 ` Yegor Yefremov
2016-11-06 14:08 ` Thomas Petazzoni
2016-11-06 14:06 ` Thomas Petazzoni
2016-11-06 15:42 ` [Buildroot] -mcpu=native [was: Re: [autobuild.buildroot.net] Build results for 2016-11-05] Arnout Vandecappelle
2016-11-06 19:33 ` [Buildroot] [autobuild.buildroot.net] Build results for 2016-11-05 Waldemar Brodkorb
2016-11-06 21:22 ` Thomas Petazzoni
2016-11-06 22:48 ` Sam Bobroff
2016-11-11 20:41 ` Thomas Petazzoni
2016-11-07 4:12 ` Sam Bobroff
2016-11-07 8:28 ` Thomas Petazzoni
2016-11-07 18:25 ` Waldemar Brodkorb
2016-11-07 20:53 ` Thomas Petazzoni [this message]
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=20161107215350.1bd07849@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