From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] Numerous ARC related toolchain issues
Date: Fri, 10 Jun 2016 07:23:04 +0000 [thread overview]
Message-ID: <1465543337.2942.15.camel@synopsys.com> (raw)
In-Reply-To: <20160609175017.0d9fae13@free-electrons.com>
Hi Thomas,
Thanks for taking care and spending your time on this analysis.
We did see all these failures and already working hard to fix them.
Below some more details on particular failures.
On Thu, 2016-06-09 at 17:50 +0200, Thomas Petazzoni wrote:
> 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
This is yet another manifestation of PIE invocation on ARC.
We'll need to disable usage of PIE in linuxpam.
> 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
That one was reported to our toolchain guys and we're looking forward
to hearing back from them.
> http://autobuild.buildroot.net/results/37a/37a57f29c6632fcdb18670a18328679dee925240/build-end.log
> BFD (GNU Binutils) 2.26.51.20160308 assertion fail elf32-arc.c:1566
Given the same assertion that was triggered and that line in the log:
----------------------->8--------------------
checking whether /home/buildroot/build/instance-1/output/host/usr/bin/arc-buildroot-linux-uclibc-gcc accepts -fPIE...
yes
----------------------->8--------------------
I would assume PIE is guilty here, so we will disable PIE in bluez-utils.
> http://autobuild.buildroot.net/results/1c1/1c14a7cbda1dce8867275ba2f2c70054fdbfbbbc/build-end.log
> (same, but on wireshark)
Looks like the same is applicable to 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.
As said above we know about all of these and trying to resolve them ASAP.
Be prepared for patches with fixes next week :)
Again thanks for all your efforts in making BR a better product!
-Alexey
next prev parent reply other threads:[~2016-06-10 7:23 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-09 15:50 [Buildroot] Numerous ARC related toolchain issues Thomas Petazzoni
2016-06-10 7:23 ` Alexey Brodkin [this message]
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=1465543337.2942.15.camel@synopsys.com \
--to=alexey.brodkin@synopsys.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