From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Analysis of build results
Date: Mon, 17 Aug 2020 14:52:49 +0200 [thread overview]
Message-ID: <20200817145249.4d02374c@windsurf.home> (raw)
In-Reply-To: <CALFsTFX6QETkRT5zui2YzmZat3qg-L4HbX_ebMx_GD6Z4xD-jQ@mail.gmail.com>
Hello Asaf,
On Mon, 17 Aug 2020 15:18:41 +0300
Asaf Kahlon <asafka7@gmail.com> wrote:
> > > or1k | zeromq-4.3.2 | NOK | http://autobuild.buildroot.net/results/538474abda90082eec91ca9017e91b4427e4f54b |
> >
> > Broken binutils:
> >
> > /home/test/autobuild/run/instance-0/output-1/host/opt/ext-toolchain/bin/../lib/gcc/or1k-buildroot-linux-uclibc/9.3.0/../../../../or1k-buildroot-linux-uclibc/bin/ld: BFD (GNU Binutils) 2.32 assertion fail elf32-or1k.c:2331
> >
> > Would be useful to test with newer binutils.
> I tried both with binutils 2.33.1 and binutils 2.34.
> Both failed with the same error...
Thanks for the additional research! I guess the next steps are:
- Report the bug to binutils upstream
- Identify if there is a work-around. But while for gcc issues we
often work-around by disabling optimizations, for binutils it is not
always possible to find a simple work-around.
If there's no workaround, then we can add a
BR2_TOOLCHAIN_HAS_BINUTILS_BUG_xyz Config.in bool and add the
appropriate dependencies.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
next prev parent reply other threads:[~2020-08-17 12:52 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-15 8:01 [Buildroot] [autobuild.buildroot.net] Daily results for 2020-08-14 Thomas Petazzoni
2020-08-15 22:09 ` [Buildroot] [autobuild.buildroot.net] Analysis of build results Thomas Petazzoni
2020-08-15 22:14 ` Thomas Petazzoni
2020-08-17 9:19 ` Gwenhael Goavec-Merou
2020-08-17 9:40 ` Thomas Petazzoni
2020-08-17 9:51 ` Gwenhael Goavec-Merou
2020-08-17 12:18 ` Asaf Kahlon
2020-08-17 12:52 ` Thomas Petazzoni [this message]
2020-08-17 20:54 ` Peter Seiderer
2020-08-17 21:30 ` Thomas Petazzoni
2020-08-17 21:57 ` Peter Seiderer
2020-08-17 21:15 ` Peter Seiderer
2020-08-17 21:43 ` Romain Naour
2020-08-19 11:47 ` Fabrice Fontaine
2020-08-19 20:31 ` [Buildroot] [arc-buildroot] " Alexey Brodkin
2020-08-19 21:33 ` Alexey Brodkin
2020-09-11 8:39 ` Thomas Petazzoni
2020-10-02 15:16 ` Alexey Brodkin
2020-10-06 18:57 ` Arnout Vandecappelle
2020-08-20 9:22 ` [Buildroot] " Frank Vanbever
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=20200817145249.4d02374c@windsurf.home \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox