From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [autobuild.buildroot.net] Build results for 2017-02-20
Date: Tue, 21 Feb 2017 23:12:42 +0100 [thread overview]
Message-ID: <20170221231242.108c3ac4@free-electrons.com> (raw)
In-Reply-To: <20170221230119.5750f9cd@gmx.net>
Hello,
On Tue, 21 Feb 2017 23:01:19 +0100, Peter Seiderer wrote:
> > But indeed, for the release, disabling unsupported architectures is
> > probably best. Can you send a patch?
>
> Can do..., depending on BR2_xtensa or (BR2_xtensa && BR2_TOOLCHAIN_USES_UCLIBC)?
Is it C library specific? I don't think it is.
Also, it's not only xtensa, but also arc and nios2 (at least).
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux and Kernel engineering
http://free-electrons.com
next prev parent reply other threads:[~2017-02-21 22:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-21 7:29 [Buildroot] [autobuild.buildroot.net] Build results for 2017-02-20 Thomas Petazzoni
2017-02-21 21:42 ` Peter Seiderer
2017-02-21 21:48 ` Thomas Petazzoni
2017-02-21 21:51 ` Romain Naour
2017-02-21 22:01 ` Peter Seiderer
2017-02-21 22:12 ` Thomas Petazzoni [this message]
2017-02-22 20:39 ` Peter Seiderer
2017-02-23 8:17 ` Thomas Petazzoni
2017-02-23 16:57 ` Peter Seiderer
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=20170221231242.108c3ac4@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