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] Autobuilder update
Date: Fri, 11 Mar 2016 14:38:40 +0100	[thread overview]
Message-ID: <20160311143840.27274777@free-electrons.com> (raw)
In-Reply-To: <87a8m5jn94.fsf@dell.be.48ers.dk>

Peter,

On Fri, 11 Mar 2016 11:57:11 +0100, Peter Korsgaard wrote:

> It depends on how much we're otherwise testing the internal toolchain? I
> agree that using an external toolchain is more efficient, but we should
> imho do "some" builds with the internal toolchain on various archs as
> well.

Agreed. We currently have the following internal toolchain
configurations tested:

br-arc-full-internal.config
br-arm-internal-full.config
br-microblazeel-full-internal.config
br-powerpc-internal-full.config
br-xtensa-full-internal.config

I can add some more if you have some suggestions.

Best regards,

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

  reply	other threads:[~2016-03-11 13:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-10 22:47 [Buildroot] Autobuilder update Thomas Petazzoni
2016-03-11  5:27 ` Bernd Kuhls
     [not found] ` <E1aeFbm-0004jE-Q7@fli4l.lan.fli4l>
2016-03-11  8:42   ` Thomas Petazzoni
2016-03-11 10:57     ` Peter Korsgaard
2016-03-11 13:38       ` Thomas Petazzoni [this message]
2016-03-11 14:20         ` Peter Korsgaard
2016-03-11 11:08 ` Peter Korsgaard
2016-03-11 13:37   ` Thomas Petazzoni
2016-03-11 14:21     ` Peter Korsgaard
2016-03-12 22:58 ` Yann E. MORIN
2016-03-13 12:08   ` 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=20160311143840.27274777@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