From: "Andreas K. Hüttel" <dilfridge@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: profiles/default/linux/x86/23.0/i686/time64/
Date: Fri, 1 Nov 2024 22:59:05 +0000 (UTC) [thread overview]
Message-ID: <1730501934.3b1a8039ea49696c6f315168f164971929d823d9.dilfridge@gentoo> (raw)
commit: 3b1a8039ea49696c6f315168f164971929d823d9
Author: Andreas K. Hüttel <dilfridge <AT> gentoo <DOT> org>
AuthorDate: Fri Nov 1 22:55:09 2024 +0000
Commit: Andreas K. Hüttel <dilfridge <AT> gentoo <DOT> org>
CommitDate: Fri Nov 1 22:58:54 2024 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=3b1a8039
profiles: time64 needs newer glibc patchlevel
Signed-off-by: Andreas K. Hüttel <dilfridge <AT> gentoo.org>
profiles/default/linux/x86/23.0/i686/time64/package.accept_keywords | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/profiles/default/linux/x86/23.0/i686/time64/package.accept_keywords b/profiles/default/linux/x86/23.0/i686/time64/package.accept_keywords
index f065ec275cad..0d0241ad4db0 100644
--- a/profiles/default/linux/x86/23.0/i686/time64/package.accept_keywords
+++ b/profiles/default/linux/x86/23.0/i686/time64/package.accept_keywords
@@ -4,3 +4,7 @@
# For better testing of time64, we use gcc-14 here already in an otherwise stable
# environment.
sys-devel/gcc:14 ~x86
+
+# We need glibc-2.39-r11 at least so we can handle the compiler that auto-sets _TIME_BITS
+# etc
+=sys-libs/glibc-2.39* ~x86
next reply other threads:[~2024-11-01 22:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-01 22:59 Andreas K. Hüttel [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-11-01 20:26 [gentoo-commits] repo/gentoo:master commit in: profiles/default/linux/x86/23.0/i686/time64/ Andreas K. Hüttel
2024-08-19 14:11 Andreas K. Hüttel
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=1730501934.3b1a8039ea49696c6f315168f164971929d823d9.dilfridge@gentoo \
--to=dilfridge@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