Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bernd Kuhls <bernd.kuhls@t-online.de>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2 10/11] package/glibc: bump to 2.26
Date: Tue, 19 Sep 2017 09:50:24 +0200	[thread overview]
Message-ID: <0ru69ex7qp.ln2@ID-313208.user.individual.net> (raw)
In-Reply-To: 20170902205423.21288-11-romain.naour@gmail.com

Am Sat, 02 Sep 2017 22:54:22 +0200 schrieb Romain Naour:

> --- a/package/glibc/glibc.mk
> +++ b/package/glibc/glibc.mk
> @@ -4,7 +4,7 @@
>  #
>  
################################################################################
>  
> -GLIBC_VERSION = 2.25
> +GLIBC_VERSION = 2.26
>  GLIBC_SITE = $(BR2_GNU_MIRROR)/libc
>  GLIBC_SOURCE = glibc-$(GLIBC_VERSION).tar.xz
>  GLIBC_SRC_SUBDIR = .

Tested-by: Bernd Kuhls <bernd.kuhls@t-online.de>
[build-tested using this defconfig:
BR2_x86_64=y
BR2_TOOLCHAIN_BUILDROOT_GLIBC=y
BR2_TOOLCHAIN_BUILDROOT_CXX=y
BR2_PACKAGE_KODI=y
BR2_PACKAGE_MESA3D=y
BR2_PACKAGE_MESA3D_DRI_DRIVER_I965=y
BR2_PACKAGE_MESA3D_OPENGL_EGL=y
BR2_PACKAGE_XORG7=y
BR2_PACKAGE_PYTHON=y
BR2_PACKAGE_PYTHON_PY_ONLY=y]

  reply	other threads:[~2017-09-19  7:50 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-02 20:54 [Buildroot] [PATCH v2 00/11] glibc: bump to 2.26 Romain Naour
2017-09-02 20:54 ` [Buildroot] [PATCH v2 01/11] package/gcc: fix build issue with glibc 2.26 Romain Naour
2017-09-17 16:08   ` Yann E. MORIN
2017-09-17 16:13     ` Yann E. MORIN
2017-09-02 20:54 ` [Buildroot] [PATCH v2 02/11] " Romain Naour
2017-09-17 16:17   ` Yann E. MORIN
2017-09-02 20:54 ` [Buildroot] [PATCH v2 03/11] package/mesa3d: fix build issue with glibc >= 2.26 Romain Naour
2017-09-19  7:54   ` Bernd Kuhls
2017-09-02 20:54 ` [Buildroot] [PATCH v2 04/11] package/jsoncpp: fix build " Romain Naour
2017-09-02 20:54 ` [Buildroot] [PATCH v2 05/11] package/glibc: needs kernel headers >= 3.10 on powerpc64le Romain Naour
2017-09-10 10:30   ` Yann E. MORIN
2017-09-11 23:05     ` Arnout Vandecappelle
2017-09-11 23:37       ` Thomas Petazzoni
2017-09-12  6:04         ` Yann E. MORIN
2017-09-12  7:47           ` Arnout Vandecappelle
2017-09-02 20:54 ` [Buildroot] [PATCH v2 06/11] package/gcc: enable float128 on powerpc64le with glibc >= 2.26 toolchains Romain Naour
2017-09-02 20:54 ` [Buildroot] [PATCH v2 07/11] package/flex: disable reallocarray Romain Naour
2017-09-02 21:12   ` Thomas Petazzoni
2017-09-02 22:23     ` Romain Naour
2017-09-03  7:14       ` Thomas Petazzoni
2017-09-07 21:32         ` Romain Naour
2017-09-13 18:53           ` Jörg Krause
2017-09-13 19:54             ` Romain Naour
2017-09-14  8:25               ` Adrian Perez de Castro
2017-09-14 10:51                 ` Jörg Krause
2017-09-02 20:54 ` [Buildroot] [PATCH v2 08/11] package/diffutils: fix build with glibc 2.26 Romain Naour
2017-09-02 20:54 ` [Buildroot] [PATCH v2 09/11] package/kodi: " Romain Naour
2017-09-19  7:51   ` Bernd Kuhls
2017-09-02 20:54 ` [Buildroot] [PATCH v2 10/11] package/glibc: bump to 2.26 Romain Naour
2017-09-19  7:50   ` Bernd Kuhls [this message]
2017-09-19 10:43     ` Romain Naour
2017-09-02 20:54 ` [Buildroot] [PATCH v2 11/11] package/glibc: backport fixes for glibc bug 21930 Romain Naour
2017-09-21 10:45 ` [Buildroot] [PATCH v2 00/11] glibc: bump to 2.26 Arnout Vandecappelle
2017-09-21 20:54   ` Romain Naour

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=0ru69ex7qp.ln2@ID-313208.user.individual.net \
    --to=bernd.kuhls@t-online.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