From: Vlad Zakharov <Vladislav.Zakharov@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of build results for 2016-07-29
Date: Mon, 1 Aug 2016 15:43:55 +0000 [thread overview]
Message-ID: <1470066235.23233.62.camel@synopsys.com> (raw)
In-Reply-To: <20160730232322.4eca1a53@free-electrons.com>
Hi Thomas, all.
You can find some comments about failed packages for ARC below:
On Sat, 2016-07-30 at 23:23 +0200, Thomas Petazzoni wrote:
> >
> > ?????????arc |????????????????????dante-1.4.1 | NOK | http://autobuild.buildroot.net/results/964cb9bc434c8634db76c875b877317d77956982/
> arc-buildroot-linux-uclibc-gcc.br_real: error: 2: No such file or directory
> arc-buildroot-linux-uclibc-gcc.br_real: error: 2: No such file or directory
>
> Not sure what's going on here. Alexey? Vlad?
Note that this failure appears not only for ARC.
Tomorrow I hope a will find some time to take a look at this issue.
> >
> > ?????????arc |????????????????libcap-ng-0.7.7 | NOK | http://autobuild.buildroot.net/results/5430b902d900943a34c1888e7e410bd5df367bc2/
> /tmp/ccGvdupB.s: Assembler messages:
> /tmp/ccGvdupB.s:575: Error: @dtpoff is not a complex relocation.
> /tmp/ccGvdupB.s:575: Error: extra comma
> /tmp/ccGvdupB.s:575: Error: syntax error
> /tmp/ccGvdupB.s:585: Error: @dtpoff is not a complex relocation.
> /tmp/ccGvdupB.s:585: Error: extra comma
> /tmp/ccGvdupB.s:585: Error: syntax error
>
> Alexey, Vlad, this one is for you?
>
> ?> ? ? ? ? arc |????????????libvncserver-0.9.10 | NOK | http://autobuild.buildroot.net/results/a563b484c9d123a711f1c92513cfc14c23bbc038/
> ?Another ARC toolchain issue. Alexey, Vlad?
This packages failed due to the same assembler problem. It has already been fixed internally.
>
> >
> > ?????????arc |????????????????linux-pam-1.2.1 | NOK | http://autobuild.buildroot.net/results/2c3aa54a14dbb561d56d8a48b6b9904f4cd1be12/
> > ?????????arc |????????????????linux-pam-1.2.1 | NOK | http://autobuild.buildroot.net/results/e9510c9443619d059770f85eb9755700e864a0c9/
> BFD (GNU Binutils) 2.26.51.20160702 assertion fail elf32-arc.c:1587
>
> Alexey, Vlad?
> >
> > ?????????arc |?????????????????????mosh-1.2.5 | NOK | http://autobuild.buildroot.net/results/d81e817f45331c90ed7aa7f114628a2ebe343979/
> > ?????????arc |?????????????????????mosh-1.2.5 | NOK | http://autobuild.buildroot.net/results/8997fdf95be140123be183e860e6948a21ed038a/
> Some more ARC toolchain issues: BFD (GNU Binutils) 2.26.51.20160702 assertion fail elf32-arc.c:2267.
>
> Alexey, Vlad :)
These failures occurred because ARC toolchain hadn't PIE support. This issue has been solved too.
>
> Thanks a lot!
>
> Thomas
According to that report I can conclude that most failures above are fixed by the patch:
http://lists.busybox.net/pipermail/buildroot/2016-August/168893.html
So if you don't have any corrections or comments please consider to apply it.
Thank you for keeping us up to date of what is happening with our toolchain :)
--
Best regards,
Vlad Zakharov <vzakhar@synopsys.com>
next prev parent reply other threads:[~2016-08-01 15:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-30 6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2016-07-29 Thomas Petazzoni
2016-07-30 21:23 ` [Buildroot] Analysis of build " Thomas Petazzoni
2016-07-31 7:44 ` Peter Korsgaard
2016-07-31 8:48 ` Waldemar Brodkorb
2016-07-31 12:44 ` Bernd Kuhls
2016-08-04 8:12 ` Khem Raj
2016-07-31 18:56 ` Baruch Siach
2016-07-31 20:56 ` Thomas Petazzoni
2016-07-31 20:06 ` Romain Naour
2016-07-31 20:49 ` Romain Naour
2016-07-31 21:42 ` Waldemar Brodkorb
2016-07-31 21:25 ` Yann E. MORIN
2016-08-01 15:43 ` Vlad Zakharov [this message]
[not found] ` <CACcFhEWvcokFB0WFsVpv6PaB-5QBnDNvhgSPFGmk43=zq8D6=A@mail.gmail.com>
2016-08-02 7:19 ` Thomas Petazzoni
2016-08-03 8:27 ` Olivier Schonken
2016-08-03 20:10 ` Angelo Compagnucci
2016-08-03 20:23 ` Yann E. MORIN
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=1470066235.23233.62.camel@synopsys.com \
--to=vladislav.zakharov@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