Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Autobuilder site back online
Date: Sun, 17 Nov 2013 18:58:45 +0100	[thread overview]
Message-ID: <87k3g6ykoa.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <20131117172917.GB4425@free.fr> (Yann E. MORIN's message of "Sun,  17 Nov 2013 18:29:17 +0100")

>>>>> "Yann" == Yann E MORIN <yann.morin.1998@free.fr> writes:

Hi,

 > Here are a few analysis of some of the build failures:

 > http://autobuild.humanoidz.org/results/a60/a60a63163288af14f701adfdfa9f62229c983984/
 -> unable to download the toolchain from mentor.com
 -> I was able to download the toolchain OK from here
 -> temporary glitch in network or on the server?

It also works here, so I guess so.

 > http://autobuild.humanoidz.org/results/6aa/6aa47858a511e89b0bd6a3a472276baab65afb1c/
 -> Cannot execute cross-compiler '/path/to/toolchain/usr/bin/nios2-linux-gcc'

 > For the last three failures above, can it be that the .config file is
 > improperly tweaked by the test framework?

It seems like it. This /path/to/toolchain/usr is the default path when a
custom external toolchain is used.

-- 
Bye, Peter Korsgaard

  parent reply	other threads:[~2013-11-17 17:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-16 21:36 [Buildroot] Autobuilder site back online Thomas Petazzoni
2013-11-17  8:03 ` Thomas De Schampheleire
2013-11-17 17:29 ` Yann E. MORIN
2013-11-17 17:50   ` Yann E. MORIN
2013-11-17 22:44     ` Thomas Petazzoni
2013-11-18 23:15     ` Arnout Vandecappelle
2013-11-18 23:30       ` Thomas Petazzoni
2013-11-20 11:45         ` Fatih Aşıcı
2013-11-20 12:30           ` Thomas Petazzoni
2013-11-17 17:58   ` Peter Korsgaard [this message]
2013-11-17 22:38   ` Thomas Petazzoni
2013-11-18 12:55     ` Arnout Vandecappelle
2013-11-18 12:59       ` 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=87k3g6ykoa.fsf@dell.be.48ers.dk \
    --to=jacmet@uclibc.org \
    --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