From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Numerous ARC related toolchain issues
Date: Thu, 9 Jun 2016 17:50:17 +0200 [thread overview]
Message-ID: <20160609175017.0d9fae13@free-electrons.com> (raw)
Hello Alexey,
It seems like since the latest update of the ARC tools, we're seeing
quite a few build failures caused by the toolchain:
http://autobuild.buildroot.net/results/d73/d732127d136bacc6bc17b742028691437df7f5f9/build-end.log
BFD (GNU Binutils) 2.26.51.20160308 assertion fail elf32-arc.c:1566
http://autobuild.buildroot.net/results/cb8/cb8bd3a01c7a6fadb20f18c1a3cbfabc52f3a6ff/build-end.log
/tmp/ccKi33Rl.s: Assembler messages:
/tmp/ccKi33Rl.s:578: Error: @dtpoff is not a complex relocation.
/tmp/ccKi33Rl.s:578: Error: extra comma
/tmp/ccKi33Rl.s:578: Error: syntax error
/tmp/ccKi33Rl.s:588: Error: @dtpoff is not a complex relocation.
/tmp/ccKi33Rl.s:588: Error: extra comma
/tmp/ccKi33Rl.s:588: Error: syntax error
http://autobuild.buildroot.net/results/37a/37a57f29c6632fcdb18670a18328679dee925240/build-end.log
BFD (GNU Binutils) 2.26.51.20160308 assertion fail elf32-arc.c:1566
http://autobuild.buildroot.net/results/1c1/1c14a7cbda1dce8867275ba2f2c70054fdbfbbbc/build-end.log
(same, but on wireshark)
These are all with the internal toolchain backend, so we're building
with the latest ARC toolchain components.
Are these problems already known? They seem to be new, I don't think
they were appearing with the previous release of ARC tools.
Thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next reply other threads:[~2016-06-09 15:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-09 15:50 Thomas Petazzoni [this message]
2016-06-10 7:23 ` [Buildroot] Numerous ARC related toolchain issues Alexey Brodkin
2016-06-10 7:37 ` Thomas Petazzoni
2016-06-10 7:45 ` Alexey Brodkin
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=20160609175017.0d9fae13@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