From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 3/5] Microblaze: Added Xilinx toolchain options
Date: Mon, 12 Mar 2012 23:06:04 +0100 [thread overview]
Message-ID: <20120312230604.266c1254@skate> (raw)
In-Reply-To: <4F5CD794.7000804@relinux.de>
Hello,
Le Sun, 11 Mar 2012 17:49:24 +0100,
Stephan Hoffmann <sho@relinux.de> a ?crit :
> Signed-off-by: Stephan Hoffmann <sho@relinux.de
>
> ---
> toolchain/toolchain-external/Config.in | 5 +++++
> 1 files changed, 5 insertions(+), 0 deletions(-)
>
> diff --git a/toolchain/toolchain-external/Config.in b/toolchain/toolchain-external/Config.in
> index b417cb7..2093180 100644
> --- a/toolchain/toolchain-external/Config.in
> +++ b/toolchain/toolchain-external/Config.in
> @@ -433,6 +433,11 @@ config BR2_TOOLCHAIN_EXTERNAL_BLACKFIN_UCLINUX_2010RC1
> config BR2_TOOLCHAIN_EXTERNAL_XILINX_MICROBLAZEEL_V2
> bool "Xilinx Little Endian Microblaze GNU Tools"
> depends on BR2_microblazeel
> + select BR2_LARGEFILE
> + select BR2_INET_IPV6
> + select BR2_INET_RPC
> + select BR2_ENABLE_LOCALE
> + select BR2_USE_WCHAR
> help
> Toolchain for the Microblaze architecture, from
> http://wiki.xilinx.com/mb-gnu-tools
This should be squashed into PATCH 2/5, and it should also be done
similarly for the big endian MicroBlaze toolchain (unless its uClibc
configuration has none of those features).
Thomas
--
Thomas Petazzoni, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2012-03-12 22:06 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-11 16:49 [Buildroot] [PATCH 3/5] Microblaze: Added Xilinx toolchain options Stephan Hoffmann
2012-03-12 22:06 ` Thomas Petazzoni [this message]
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=20120312230604.266c1254@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