From: Vlad Zakharov <Vladislav.Zakharov@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of build results for 2016-08-05
Date: Mon, 8 Aug 2016 15:56:21 +0000 [thread overview]
Message-ID: <1470671781.31195.45.camel@synopsys.com> (raw)
In-Reply-To: <20160807112654.7b520594@free-electrons.com>
Hi Thomas, all,
On Sun, 2016-08-07 at 11:26 +0200, Thomas Petazzoni wrote:
> Hello,
>
> Here is the usual analysis of build failures. Waldemar, Alexey, Vlad,
> Gustavo, Frank, Gwenhael, Angelo, Fran?ois, Romain, Bernd, can you have
> a look below? Thanks!
>
> On Sat,??6 Aug 2016 08:30:28 +0200 (CEST), Thomas Petazzoni wrote:
> >
> > ?????????arc |????????????????bootutils-1.0.0 | NOK | http://autobuild.buildroot.net/results/4059a5afe3e471d4b25db493d4c5eec646a8b0e1/
> cannot find crtbeginT.o: No such file or directory
>
> Alexey, Vlad ?
> >
> > ?????????arc | host-gcc-final-arc-2016.09-... | NOK | http://autobuild.buildroot.net/results/3afc00e64274e89de2cf81e1dda8854327b89291/
> configure: error: Link tests are not allowed after GCC_NO_EXECUTABLES.
>
> Alexey, Vlad ?
>
The failures listed above occurred due to the same issue - crtbeginT.o file was missing as the corresponding dependency wasn't added.
The issue has already been solved internally and will be included in our next engineering build. We hope that new build happen tomorrow or
the day after tomorrow. Anyway we will send patch patch with bumping to new arc toolchain as soon as it will come up.
> ?????????arc |???????????????????stella-4.7.2 | NOK | http://autobuild.buildroot.net/results/1752ca6a393b43750022db3faee85cfc9d360bc4/
> > x86_64-linux-gnu-g++: error: unrecognized command line option '-matomic'
> > x86_64-linux-gnu-g++: error: unrecognized command line option '-matomic'
> >?
> > Why is the heck a x86_64-linux-gnu compiler used on an ARC
> > configuration? There are some configure scripts issues as well:
> >?
> > Looking for C++ compiler... ./configure: line 110: eval: -g: invalid option
> > eval: usage: eval [arg ...]
> > ./configure: line 110: eval: -c: invalid option
> > eval: usage: eval [arg ...]
>
I am looking at this issue now. I will report about it ASAP.
> >
> Thomas
Thank you for your reports.
--
Best regards,
Vlad Zakharov <vzakhar@synopsys.com>
next prev parent reply other threads:[~2016-08-08 15:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-06 6:30 [Buildroot] [autobuild.buildroot.net] Build results for 2016-08-05 Thomas Petazzoni
2016-08-07 9:26 ` [Buildroot] Analysis of build " Thomas Petazzoni
2016-08-07 11:46 ` Waldemar Brodkorb
2016-08-09 10:03 ` Thomas Petazzoni
2016-08-07 14:33 ` Frank Hunleth
2016-08-07 15:48 ` Samuel Martin
2016-08-09 14:15 ` Ben Boeckel
2016-08-17 21:18 ` Samuel Martin
2016-08-08 15:56 ` Vlad Zakharov [this message]
2016-08-08 20:34 ` Thomas Petazzoni
2016-08-11 10:43 ` Vlad Zakharov
2016-08-09 13:27 ` gwenhael.goavec
2016-08-09 13:41 ` Thomas Petazzoni
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=1470671781.31195.45.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