Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2014-02-04
Date: Wed, 5 Feb 2014 13:52:06 +0100	[thread overview]
Message-ID: <20140205135206.58a30106@skate> (raw)
In-Reply-To: <52F22534.6030403@imgtec.com>

Dear Vicente Olivert Riera,

On Wed, 5 Feb 2014 11:49:08 +0000, Vicente Olivert Riera wrote:
> On 02/05/2014 07:30 AM, Thomas Petazzoni wrote:
> > Classification of failures by reason
> > ====================================
> >                    bcusdk-0.0.5 | 1
> 
> > Detail of failures
> > ===================
> >      mipsel |                   bcusdk-0.0.5 | NOK | http://autobuild.buildroot.net/results/32ad17192194171a4b9b5334731d32a323e2b007/
> 
> This failure is *not* present when using the internal BR toolchain. 
> Perhaps the "br-mipsel-o32-full-2013.11-rc2.tar.bz2" toolchain should be 
> upgraded.

Seems to be related to the internal toolchain bug which lead
libstdc++.a to not be generated. I am waiting for Peter to release
2014.02-rc1, and I will rebuild all the Buildroot external toolchains
to this release, which will fix this problem.

Thanks for your investigation!

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  reply	other threads:[~2014-02-05 12:52 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-02-05  7:30 [Buildroot] [autobuild.buildroot.net] Build results for 2014-02-04 Thomas Petazzoni
2014-02-05 11:49 ` Vicente Olivert Riera
2014-02-05 12:52   ` Thomas Petazzoni [this message]
2014-02-05 13:50 ` Anton Kolesov

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=20140205135206.58a30106@skate \
    --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