From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: net-misc/ntp/, net-misc/ntp/files/
Date: Sun, 17 Oct 2021 06:21:48 +0000 (UTC) [thread overview]
Message-ID: <1634451700.7094bf58386e8970a0b96b92938f42e61c6bb656.sam@gentoo> (raw)
commit: 7094bf58386e8970a0b96b92938f42e61c6bb656
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Sun Oct 17 06:21:32 2021 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Sun Oct 17 06:21:40 2021 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=7094bf58
net-misc/ntp: fix build with glibc-2.34
Closes: https://bugs.gentoo.org/806358
Signed-off-by: Sam James <sam <AT> gentoo.org>
net-misc/ntp/files/ntp-4.2.8_p15-glibc-2.34.patch | 28 +++++++++++++++++++++++
net-misc/ntp/ntp-4.2.8_p15.ebuild | 1 +
2 files changed, 29 insertions(+)
diff --git a/net-misc/ntp/files/ntp-4.2.8_p15-glibc-2.34.patch b/net-misc/ntp/files/ntp-4.2.8_p15-glibc-2.34.patch
new file mode 100644
index 00000000000..a32f3adabd8
--- /dev/null
+++ b/net-misc/ntp/files/ntp-4.2.8_p15-glibc-2.34.patch
@@ -0,0 +1,28 @@
+https://bugs.gentoo.org/806358
+https://patchwork.openembedded.org/patch/180019/
+
+From: Khem Raj <raj.khem@gmail.com>
+Date: Sat, 31 Jul 2021 10:51:41 -0700
+Subject: [PATCH] libntp: Do not use PTHREAD_STACK_MIN on glibc
+
+In glibc 2.34+ PTHREAD_STACK_MIN is not a compile-time constant which
+could mean different stack sizes at runtime on different architectures
+and it also causes compile failure. Default glibc thread stack size
+or 64Kb set by ntp should be good in glibc these days.
+
+Upstream-Status: Pending
+Signed-off-by: Khem Raj <raj.khem@gmail.com>
+--- a/libntp/work_thread.c
++++ b/libntp/work_thread.c
+@@ -41,7 +41,7 @@
+ #ifndef THREAD_MINSTACKSIZE
+ # define THREAD_MINSTACKSIZE (64U * 1024)
+ #endif
+-#ifndef __sun
++#if !defined(__sun) && !defined(__GLIBC__)
+ #if defined(PTHREAD_STACK_MIN) && THREAD_MINSTACKSIZE < PTHREAD_STACK_MIN
+ # undef THREAD_MINSTACKSIZE
+ # define THREAD_MINSTACKSIZE PTHREAD_STACK_MIN
+--
+2.32.0
+
diff --git a/net-misc/ntp/ntp-4.2.8_p15.ebuild b/net-misc/ntp/ntp-4.2.8_p15.ebuild
index 0809ce703a5..7e9d8bc04c2 100644
--- a/net-misc/ntp/ntp-4.2.8_p15.ebuild
+++ b/net-misc/ntp/ntp-4.2.8_p15.ebuild
@@ -47,6 +47,7 @@ PATCHES=(
"${FILESDIR}"/${PN}-4.2.8_p10-fix-build-wo-ssl-or-libressl.patch
"${FILESDIR}"/${PN}-4.2.8_p14-add_cap_ipc_lock.patch #711530
"${FILESDIR}"/${PN}-4.2.8_p15-gcc10.patch #759409
+ "${FILESDIR}"/${PN}-4.2.8_p15-glibc-2.34.patch
)
src_prepare() {
next reply other threads:[~2021-10-17 6:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-17 6:21 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-04 1:15 [gentoo-commits] repo/gentoo:master commit in: net-misc/ntp/, net-misc/ntp/files/ Sam James
2023-02-14 0:40 Mike Gilbert
2022-12-01 5:17 Sam James
2022-06-03 5:32 Sam James
2020-07-27 19:02 Lars Wendler
2020-06-23 16:16 Lars Wendler
2020-05-02 18:59 Thomas Deutschmann
2020-03-05 18:51 Lars Wendler
2018-12-08 1:49 Patrick McLean
2016-01-13 10:28 Lars Wendler
2015-10-25 1:07 Mike Frysinger
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=1634451700.7094bf58386e8970a0b96b92938f42e61c6bb656.sam@gentoo \
--to=sam@gentoo.org \
--cc=gentoo-commits@lists.gentoo.org \
--cc=gentoo-dev@lists.gentoo.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