Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Khem Raj <raj.khem@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 0/2] Upgrade glibc 2.27
Date: Thu,  1 Feb 2018 14:40:48 -0800	[thread overview]
Message-ID: <cover.1517524576.git.raj.khem@gmail.com> (raw)

qemu patch is needed for it to compile with glibc 2.27

The following changes since commit a0988c3374e964170d1d24fc230306b887432d31:

  tcmode-default.inc: drop preferred version of gzip-native (2018-01-31 17:01:12 +0000)

are available in the Git repository at:

  git://git.openembedded.org/openembedded-core-contrib kraj/glibc-2.27
  http://cgit.openembedded.org/openembedded-core-contrib/log/?h=kraj/glibc-2.27

Khem Raj (1):
  glibc: Upgrade to 2.27 release

Ross Burton (1):
  qemu: fix memfd_create with glibc 2.27

 meta/conf/distro/include/tcmode-default.inc        |   2 +-
 ...tive_2.26.bb => cross-localedef-native_2.27.bb} |   4 +-
 ...glibc-initial_2.26.bb => glibc-initial_2.27.bb} |   0
 .../{glibc-locale_2.26.bb => glibc-locale_2.27.bb} |   0
 .../{glibc-mtrace_2.26.bb => glibc-mtrace_2.27.bb} |   0
 ...glibc-scripts_2.26.bb => glibc-scripts_2.27.bb} |   0
 ...libc-Look-for-host-system-ld.so.cache-as-.patch |  12 +-
 ...libc-Fix-buffer-overrun-with-a-relocated-.patch |  10 +-
 ...libc-Raise-the-size-of-arrays-containing-.patch |  28 ++--
 ...ivesdk-glibc-Allow-64-bit-atomics-for-x86.patch |   8 +-
 ...500-e5500-e6500-603e-fsqrt-implementation.patch |   6 +-
 ...-OECORE_KNOWN_INTERPRETER_NAMES-to-known-.patch |   8 +-
 ...-Fix-undefined-reference-to-__sqrt_finite.patch |   6 +-
 ...qrt-f-are-now-inline-functions-and-call-o.patch |   6 +-
 ...bug-1443-which-explains-what-the-patch-do.patch |  10 +-
 ...n-libm-err-tab.pl-with-specific-dirs-in-S.patch |  10 +-
 ...qrt-f-are-now-inline-functions-and-call-o.patch |   6 +-
 ...-configure.ac-handle-correctly-libc_cv_ro.patch |   8 +-
 .../glibc/glibc/0013-Add-unused-attribute.patch    |   8 +-
 ...thin-the-path-sets-wrong-config-variables.patch |  10 +-
 ...-timezone-re-written-tzselect-as-posix-sh.patch |   8 +-
 ...move-bash-dependency-for-nscd-init-script.patch |   6 +-
 ...c-Cross-building-and-testing-instructions.patch |   6 +-
 ...018-eglibc-Help-bootstrap-cross-toolchain.patch |   8 +-
 .../0019-eglibc-Clear-cache-lines-on-ppc8xx.patch  |  10 +-
 ...0020-eglibc-Resolve-__fpscr_values-on-SH4.patch |   8 +-
 .../glibc/0021-eglibc-Install-PIC-archives.patch   |  20 +--
 ...ward-port-cross-locale-generation-support.patch |  90 +++++------
 ...0023-Define-DUMMY_LOCALE_T-if-not-defined.patch |   8 +-
 ....c-Make-_dl_build_local_scope-breadth-fir.patch |  10 +-
 ...-locale-fix-hard-coded-reference-to-gcc-E.patch |   6 +-
 ...6-reset-dl_load_write_lock-after-forking.patch} |  29 ++--
 ...o-lock-before-switching-to-malloc_atfork.patch} |  27 +++-
 ...loc-add-missing-arena-lock-in-malloc-info.patch | 172 ---------------------
 meta/recipes-core/glibc/glibc/CVE-2017-15671.patch |  65 --------
 meta/recipes-core/glibc/glibc/CVE-2017-16997.patch | 151 ------------------
 meta/recipes-core/glibc/glibc/CVE-2017-17426.patch |  53 -------
 .../glibc/{glibc_2.26.bb => glibc_2.27.bb}         |  14 +-
 meta/recipes-devtools/qemu/qemu/memfd.patch        |  57 +++++++
 meta/recipes-devtools/qemu/qemu_2.11.0.bb          |   2 +-
 40 files changed, 258 insertions(+), 634 deletions(-)
 rename meta/recipes-core/glibc/{cross-localedef-native_2.26.bb => cross-localedef-native_2.27.bb} (93%)
 rename meta/recipes-core/glibc/{glibc-initial_2.26.bb => glibc-initial_2.27.bb} (100%)
 rename meta/recipes-core/glibc/{glibc-locale_2.26.bb => glibc-locale_2.27.bb} (100%)
 rename meta/recipes-core/glibc/{glibc-mtrace_2.26.bb => glibc-mtrace_2.27.bb} (100%)
 rename meta/recipes-core/glibc/{glibc-scripts_2.26.bb => glibc-scripts_2.27.bb} (100%)
 rename meta/recipes-core/glibc/glibc/{0027-glibc-reset-dl-load-write-lock-after-forking.patch => 0026-reset-dl_load_write_lock-after-forking.patch} (63%)
 rename meta/recipes-core/glibc/glibc/{0028-Bug-4578-add-ld.so-lock-while-fork.patch => 0027-Acquire-ld.so-lock-before-switching-to-malloc_atfork.patch} (76%)
 delete mode 100644 meta/recipes-core/glibc/glibc/0029-malloc-add-missing-arena-lock-in-malloc-info.patch
 delete mode 100644 meta/recipes-core/glibc/glibc/CVE-2017-15671.patch
 delete mode 100644 meta/recipes-core/glibc/glibc/CVE-2017-16997.patch
 delete mode 100644 meta/recipes-core/glibc/glibc/CVE-2017-17426.patch
 rename meta/recipes-core/glibc/{glibc_2.26.bb => glibc_2.27.bb} (89%)
 create mode 100644 meta/recipes-devtools/qemu/qemu/memfd.patch

-- 
2.16.1



             reply	other threads:[~2018-02-01 22:40 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-01 22:40 Khem Raj [this message]
2018-02-01 22:41 ` [PATCH 1/2] qemu: fix memfd_create with glibc 2.27 Khem Raj
2018-02-01 22:41 ` [PATCH 2/2] glibc: Upgrade to 2.27 release Khem Raj
2018-02-03 10:21   ` Burton, Ross
2018-02-12  7:32     ` Khem Raj
2018-02-15 12:12       ` Burton, Ross
2018-02-18  7:58         ` Khem Raj
2018-02-19 20:06           ` Burton, Ross
2018-02-19 20:11             ` Khem Raj
2018-02-23  3:06           ` Khem Raj
2018-02-23 12:29             ` Burton, Ross
2018-02-23 14:45               ` Khem Raj
2018-02-23 15:34                 ` Burton, Ross
2018-02-01 23:04 ` ✗ patchtest: failure for Upgrade glibc 2.27 Patchwork

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=cover.1517524576.git.raj.khem@gmail.com \
    --to=raj.khem@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    /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