From: "Sam James" <sam@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/gentoo:master commit in: profiles/prefix/darwin/macos/
Date: Tue, 01 Apr 2025 22:02:10 +0000 (UTC) [thread overview]
Message-ID: <1743544924.bce8bb0fcacadb2cf6c57f5ae0f69bf50c99f4e1.sam@gentoo> (raw)
commit: bce8bb0fcacadb2cf6c57f5ae0f69bf50c99f4e1
Author: Sam James <sam <AT> gentoo <DOT> org>
AuthorDate: Tue Apr 1 22:01:26 2025 +0000
Commit: Sam James <sam <AT> gentoo <DOT> org>
CommitDate: Tue Apr 1 22:02:04 2025 +0000
URL: https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=bce8bb0f
profiles/prefix/darwin/macos: mask =sys-libs/gdbm-1.25
Workaround for build failure on macOS. Still needs to be reported upstream
but I don't have a macOS Prefix at the moment to do that, so leaving
for someone else.
Bug: https://bugs.gentoo.org/951918
Signed-off-by: Sam James <sam <AT> gentoo.org>
profiles/prefix/darwin/macos/package.mask | 7 ++++++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/profiles/prefix/darwin/macos/package.mask b/profiles/prefix/darwin/macos/package.mask
index 709360d865d4..8aef87c65608 100644
--- a/profiles/prefix/darwin/macos/package.mask
+++ b/profiles/prefix/darwin/macos/package.mask
@@ -1,6 +1,11 @@
-# Copyright 1999-2024 Gentoo Authors
+# Copyright 1999-2025 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
+# Sam James <sam@gentoo.org> (2025-04-01)
+# Fails to build w/ `error: implicit declaration of function 'clock_nanosleep'`
+# See bug #951918.
+=sys-libs/gdbm-1.25
+
# Benda Xu <heroxbd@gentoo.org> (2023-08-20)
# Does not play well with linkers under macOS.
# Undefined symbols for architecture x86_64:
next reply other threads:[~2025-04-01 22:02 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-01 22:02 Sam James [this message]
-- strict thread matches above, loose matches on Subject: below --
2024-07-19 11:33 [gentoo-commits] repo/gentoo:master commit in: profiles/prefix/darwin/macos/ Fabian Groffen
2024-07-17 13:27 Fabian Groffen
2024-05-28 14:10 Fabian Groffen
2023-08-20 8:44 Benda XU
2023-08-17 5:54 Benda XU
2023-08-17 4:41 Benda XU
2023-07-31 17:29 Benda XU
2023-07-24 6:56 Fabian Groffen
2023-07-17 1:51 Benda XU
2023-07-09 3:40 Benda XU
2023-06-05 13:36 Fabian Groffen
2023-05-01 6:32 Fabian Groffen
2023-04-27 10:27 Fabian Groffen
2022-07-08 7:32 Fabian Groffen
2022-06-14 14:16 Fabian Groffen
2022-01-16 12:20 Fabian Groffen
2022-01-09 22:12 Sam James
2022-01-01 10:03 Sam James
2021-12-23 7:12 Sam James
2021-12-23 7:03 Sam James
2021-09-05 21:01 Sam James
2021-08-22 12:00 Fabian Groffen
2021-02-12 23:51 Sam James
2021-01-14 13:40 Fabian Groffen
2021-01-14 12:45 Fabian Groffen
2021-01-10 14:49 Fabian Groffen
2021-01-10 10:05 Fabian Groffen
2021-01-10 10:05 Fabian Groffen
2020-12-20 16:06 Fabian Groffen
2020-12-10 12:23 Fabian Groffen
2020-12-10 10:51 Fabian Groffen
2020-12-07 20:29 Fabian Groffen
2020-11-30 7:27 Sam James
2020-11-30 3:13 Sam James
2020-11-23 16:16 Fabian Groffen
2020-11-23 16:01 Fabian Groffen
2020-11-23 13:31 Fabian Groffen
2020-06-09 16:38 Fabian Groffen
2020-06-08 18:48 Fabian Groffen
2019-07-05 14:18 Guilherme Amadio
2019-04-26 13:44 Fabian Groffen
2019-03-26 9:29 Fabian Groffen
2019-03-26 9:26 Fabian Groffen
2019-03-22 10:04 Fabian Groffen
2018-03-11 1:31 Andrey Utkin
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=1743544924.bce8bb0fcacadb2cf6c57f5ae0f69bf50c99f4e1.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