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:40:58 -0300	[thread overview]
Message-ID: <56CB01DA.1060601@zacarias.com.ar> (raw)
In-Reply-To: <20160222133337.743dba7f@free-electrons.com>

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

> I don't really see why you're talking specifically about atomics here,
> but OK with the rest.

Because newer glibc versions need them for thread barriers, see glibc 
source in sysdeps/sparc/sparc32/atomic-machine.h

>> 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).
>
> I don't follow the relation with multilib support. Care to expand on
> this?

Since you can't build a 32-bit linux kernel for v9+ then you need a gcc 
capable of -m64 for v9, even if your userland is 32-bit.
There's no separation in cpu mode for SPARC 32/64 bits like there is for 
x86, so you can use the new instructions even in 32-bit "mode".
Regards.

  reply	other threads:[~2016-02-22 12:40 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
2016-02-22 12:33       ` Thomas Petazzoni
2016-02-22 12:40         ` Gustavo Zacarias [this message]
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=56CB01DA.1060601@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