From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v3 6/7] toolchain: uclibc does not support microblze
Date: Wed, 13 Nov 2013 22:58:19 +0100 [thread overview]
Message-ID: <20131113225819.56b10ada@skate> (raw)
In-Reply-To: <1384378130-8599-7-git-send-email-spenser@gillilanding.com>
Dear Spenser Gilliland,
On Wed, 13 Nov 2013 15:28:49 -0600, Spenser Gilliland wrote:
>
> Signed-off-by: Spenser Gilliland <spenser@gillilanding.com>
> ---
> toolchain/toolchain-buildroot/Config.in | 1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/toolchain/toolchain-buildroot/Config.in b/toolchain/toolchain-buildroot/Config.in
> index 1529004..57bbc3d 100644
> --- a/toolchain/toolchain-buildroot/Config.in
> +++ b/toolchain/toolchain-buildroot/Config.in
> @@ -9,6 +9,7 @@ choice
> config BR2_TOOLCHAIN_BUILDROOT_UCLIBC
> bool "uClibc"
> select BR2_TOOLCHAIN_USES_UCLIBC
> + depends on !BR2_microblaze
Hum, I see a libc/sysdeps/linux/microblaze in my uClibc tree. And also,
since there are some no-MMU variant of Microblaze processors, which C
library other than uClibc could they use?
That being said, I don't *require* you to add the support for uClibc.
Having glibc/eglibc support is already good. We can add uClibc support
later on.
Best regards,
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
next prev parent reply other threads:[~2013-11-13 21:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-13 21:28 [Buildroot] [PATCH v3 0/7] Add Microblaze internal toolchain Spenser Gilliland
2013-11-13 21:28 ` [Buildroot] [PATCH v3 1/7] binutils: add microblaze " Spenser Gilliland
2013-11-13 21:28 ` [Buildroot] [PATCH v3 2/7] gcc: " Spenser Gilliland
2013-11-13 21:28 ` [Buildroot] [PATCH v3 3/7] glibc: " Spenser Gilliland
2013-11-13 21:28 ` [Buildroot] [PATCH v3 4/7] gdb: " Spenser Gilliland
2013-11-13 21:28 ` [Buildroot] [PATCH v3 5/7] toolchain: enable microblaze toolchain Spenser Gilliland
2013-11-13 21:28 ` [Buildroot] [PATCH v3 6/7] toolchain: uclibc does not support microblze Spenser Gilliland
2013-11-13 21:58 ` Thomas Petazzoni [this message]
2013-11-13 22:35 ` Spenser Gilliland
2013-11-13 23:20 ` Thomas Petazzoni
2013-11-13 23:42 ` Spenser Gilliland
2013-11-13 21:28 ` [Buildroot] [PATCH v3 7/7] defconfigs: update microblaze defconfigs to use new toolchain Spenser Gilliland
2013-11-13 22:11 ` [Buildroot] [PATCH v3 0/7] Add Microblaze internal toolchain Mischa Jonker
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=20131113225819.56b10ada@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.