Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@free-electrons.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] glibc: add version 2.24
Date: Fri, 5 Aug 2016 18:53:48 +0200	[thread overview]
Message-ID: <20160805185348.4c0ff1fd@free-electrons.com> (raw)
In-Reply-To: <1470387567-64171-1-git-send-email-Vincent.Riera@imgtec.com>

Hello,

On Fri, 5 Aug 2016 09:59:27 +0100, Vicente Olivert Riera wrote:
> Signed-off-by: Vicente Olivert Riera <Vincent.Riera@imgtec.com>
> ---
>  package/glibc/Config.in  | 6 ++++++
>  package/glibc/glibc.hash | 1 +
>  2 files changed, 7 insertions(+)
> 
> diff --git a/package/glibc/Config.in b/package/glibc/Config.in
> index f86822d..a9a6cc7 100644
> --- a/package/glibc/Config.in
> +++ b/package/glibc/Config.in
> @@ -22,6 +22,11 @@ config BR2_GLIBC_VERSION_2_23
>  	# No support for pthread barriers on < v9 ISA
>  	depends on !BR2_sparc
>  
> +config BR2_GLIBC_VERSION_2_24
> +	bool "2.24"
> +	# No support for pthread barriers on < v9 ISA
> +	depends on !BR2_sparc

One thing important I notice in the release announcement of 2.24 is:

* The minimum Linux kernel version that this version of the GNU C Library
  can be used with is 3.2, except on i[4567]86 and x86_64, where Linux
  kernel version 2.6.32 or later suffices (on architectures that already
  required kernel versions more recent than 3.2, those requirements remain
  unchanged).  Linux 3.2 or later kernel headers are required on all
  architectures.

It is not written completely clearly: they first say that on
x86/x86-64, 2.6.32 is sufficient, but they conclude that 3.2 is the
minimum version on all architectures. It would be good to clarify this
aspect.

Regardless of this detail, this means we will have to encode this
dependency somehow. Indeed, we still have people using kernels older
than 3.2 I believe on various platforms.

Best regards,

Thomas
-- 
Thomas Petazzoni, CTO, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com

  parent reply	other threads:[~2016-08-05 16:53 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-05  8:59 [Buildroot] [PATCH] glibc: add version 2.24 Vicente Olivert Riera
2016-08-05 14:33 ` Khem Raj
2016-08-05 16:54   ` Thomas Petazzoni
2016-08-08  8:46     ` Vicente Olivert Riera
2016-08-05 16:53 ` Thomas Petazzoni [this message]
2016-08-05 20:58   ` Khem Raj
2016-08-05 21:17     ` Thomas Petazzoni
2016-08-05 21:25       ` Khem Raj
2016-08-05 21:30         ` Thomas Petazzoni
2016-08-08 16:42   ` Yann E. MORIN
2016-08-09  8:49     ` Thomas Petazzoni
2016-08-09 19:33       ` Yann E. MORIN
2016-08-09 19:42         ` Khem Raj
2016-08-09 19:56           ` Yann E. MORIN

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=20160805185348.4c0ff1fd@free-electrons.com \
    --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