From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] Analysis of build results for 2016-08-05
Date: Mon, 8 Aug 2016 22:34:07 +0200 [thread overview]
Message-ID: <20160808223407.4f535efd@free-electrons.com> (raw)
In-Reply-To: <1470671781.31195.45.camel@synopsys.com>
Hello,
On Mon, 8 Aug 2016 15:56:21 +0000, Vlad Zakharov wrote:
> 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.
OK, thanks!
> > > 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.
Perfect, thanks!
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2016-08-08 20:34 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
2016-08-08 20:34 ` Thomas Petazzoni [this message]
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=20160808223407.4f535efd@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