Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Stephan Hoffmann <sho@relinux.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] toolchain/microblaze: fix up big-endian	characteristics
Date: Wed, 04 Apr 2012 19:26:43 +0200	[thread overview]
Message-ID: <4F7C8453.10305@relinux.de> (raw)
In-Reply-To: <1332186504-27410-1-git-send-email-gustavo@zacarias.com.ar>

Am 19.03.2012 20:48, schrieb Gustavo Zacarias:
> The big-endian microblaze external toolchain is missing vital
> characteristics being set, such as LARGEFILE support, IPV6 and so on.
>
> Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
Tested-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 014bfc5..ee79339 100644
> --- a/toolchain/toolchain-external/Config.in
> +++ b/toolchain/toolchain-external/Config.in
> @@ -447,6 +447,11 @@ config BR2_TOOLCHAIN_EXTERNAL_XILINX_MICROBLAZEEL_V2
>  config BR2_TOOLCHAIN_EXTERNAL_XILINX_MICROBLAZEBE_V2
>  	bool "Xilinx Big Endian Microblaze GNU Tools"
>  	depends on BR2_microblazebe
> +	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


-- 
reLinux     -    Stephan Hoffmann
Am Schmidtgrund 124    50765 K?ln
Tel. +49.221.95595-19    Fax: -64
www.reLinux.de     sho at reLinux.de

  parent reply	other threads:[~2012-04-04 17:26 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-19 19:48 [Buildroot] [PATCH] toolchain/microblaze: fix up big-endian characteristics Gustavo Zacarias
2012-03-20  2:58 ` Spenser Gilliland
2012-04-04 17:26 ` Stephan Hoffmann [this message]
2012-04-04 20:46 ` Peter Korsgaard

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=4F7C8453.10305@relinux.de \
    --to=sho@relinux.de \
    --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