From: Khem Raj <raj.khem@gmail.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 1/2] glibc: Fix pthread_rwlock_try*lock stalls
Date: Mon, 4 Feb 2019 11:59:17 -0800 [thread overview]
Message-ID: <20190204195918.8726-1-raj.khem@gmail.com> (raw)
Brings in a backport as described in
https://sourceware.org/git/?p=glibc.git;a=commit;h=86013ef5cea322b8f4b9c22f230c22cce369e947
Signed-off-by: Khem Raj <raj.khem@gmail.com>
---
meta/recipes-core/glibc/cross-localedef-native_2.29.bb | 2 +-
meta/recipes-core/glibc/glibc_2.29.bb | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-core/glibc/cross-localedef-native_2.29.bb b/meta/recipes-core/glibc/cross-localedef-native_2.29.bb
index edb4fd40dc..8bc7cd649b 100644
--- a/meta/recipes-core/glibc/cross-localedef-native_2.29.bb
+++ b/meta/recipes-core/glibc/cross-localedef-native_2.29.bb
@@ -23,7 +23,7 @@ UPSTREAM_CHECK_GITTAGREGEX = "(?P<pver>\d+\.\d+(\.(?!90)\d+)*)"
PV = "2.29"
-SRCREV_glibc ?= "56c86f5dd516284558e106d04b92875d5b623b7a"
+SRCREV_glibc ?= "86013ef5cea322b8f4b9c22f230c22cce369e947"
SRCREV_localedef ?= "cd9f958c4c94a638fa7b2b4e21627364f1a1a655"
SRC_URI = "${GLIBC_GIT_URI};branch=${SRCBRANCH};name=glibc \
diff --git a/meta/recipes-core/glibc/glibc_2.29.bb b/meta/recipes-core/glibc/glibc_2.29.bb
index 362c172833..72db00cdb7 100644
--- a/meta/recipes-core/glibc/glibc_2.29.bb
+++ b/meta/recipes-core/glibc/glibc_2.29.bb
@@ -9,7 +9,7 @@ DEPENDS += "gperf-native bison-native make-native"
PV = "2.29"
-SRCREV ?= "56c86f5dd516284558e106d04b92875d5b623b7a"
+SRCREV ?= "86013ef5cea322b8f4b9c22f230c22cce369e947"
SRCBRANCH ?= "release/${PV}/master"
--
2.20.1
next reply other threads:[~2019-02-04 19:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-04 19:59 Khem Raj [this message]
2019-02-04 19:59 ` [PATCH 2/2] binutils: Upgrade to binutils 2.32 Khem Raj
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=20190204195918.8726-1-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