Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Zacarias <gustavo@zacarias.com.ar>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] glibc: remove version 2.21
Date: Mon, 22 Feb 2016 09:25:05 -0300	[thread overview]
Message-ID: <56CAFE21.4030803@zacarias.com.ar> (raw)
In-Reply-To: <20160222132027.091e7c84@free-electrons.com>

On 22/02/16 09:20, Thomas Petazzoni wrote:

> Gustavo,
>
> On Mon, 22 Feb 2016 09:07:25 -0300, Gustavo Zacarias wrote:
>> Mask out glibc for sparc as well since it's no longer available.
>>
>> Signed-off-by: Gustavo Zacarias <gustavo@zacarias.com.ar>
>
> Is it SPARC entirely, or only some specific architecture variants of
> SPARC that are no longer supported ?
>
> Thomas

Quick SPARC lesson.
SPARC < V9 = 32 bits (AKA sparc arch).
SPARC >= V9 = 64 bits and 32 bits as well (similar to x86, AKA sparc64 
arch).
Now, you can use atomics for >= v9 and even on 32 bits, but normally 
even if you use 32 bit userland you want a 64 bit kernel anyway (IIRC 
solaris supports 32 bit kernel as well for old/transition versions, but 
AFAIK linux never went there).
So basically yes, sparc = no glibc, sparc64 = yes glibc, because we 
don't support multilib (in gentoo it wasn't 100% multilib in the past, 
except that binutils/gcc did support -m64/-m32, but there wasn't libc 
support, hence not really multilib).
If/when said support is in place someone can update it.
Regards.

  reply	other threads:[~2016-02-22 12:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-02-22 12:07 [Buildroot] [PATCH v2] glibc: remove version 2.21 Gustavo Zacarias
2016-02-22 12:07 ` [Buildroot] [PATCH] " Gustavo Zacarias
2016-02-22 12:20   ` Thomas Petazzoni
2016-02-22 12:25     ` Gustavo Zacarias [this message]
2016-02-22 12:33       ` Thomas Petazzoni
2016-02-22 12:40         ` Gustavo Zacarias
2016-02-29 21:57   ` Thomas Petazzoni
  -- strict thread matches above, loose matches on Subject: below --
2016-02-22 11:15 Gustavo Zacarias

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=56CAFE21.4030803@zacarias.com.ar \
    --to=gustavo@zacarias.com.ar \
    --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