From: Sam James <sam@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: toolchain@gentoo.org, sandbox@gentoo.org, musl@gentoo.org,
Sam James <sam@gentoo.org>
Subject: [gentoo-dev] [PATCH] profiles: workaround sandbox bug with getcwd() configure test (gl_cv_func_getcwd_path_max)
Date: Mon, 22 Jan 2024 16:14:29 +0000 [thread overview]
Message-ID: <20240122161434.991554-1-sam@gentoo.org> (raw)
Workaround for sandbox bug which causes this gnulib configure test to take
many real hours on slower machines, and certainly a huge amount of CPU hours
on others.
Spoof the same result as configure gets on a modern glibc & musl system for now.
Bug: https://bugs.gentoo.org/447970
Closes: https://bugs.gentoo.org/922652
Signed-off-by: Sam James <sam@gentoo.org>
---
profiles/default/linux/make.defaults | 9 ++++++++-
profiles/features/musl/make.defaults | 7 +++++++
2 files changed, 15 insertions(+), 1 deletion(-)
diff --git a/profiles/default/linux/make.defaults b/profiles/default/linux/make.defaults
index 74dd59d5d8179..4e21cd58fdf22 100644
--- a/profiles/default/linux/make.defaults
+++ b/profiles/default/linux/make.defaults
@@ -1,4 +1,4 @@
-# Copyright 1999-2023 Gentoo Authors
+# Copyright 1999-2024 Gentoo Authors
# Distributed under the terms of the GNU General Public License v2
#
# System-wide defaults for the Portage system
@@ -54,3 +54,10 @@ LDFLAGS="-Wl,-O1 -Wl,--as-needed"
# Prevent automagic use of 64-bit time_t.
# https://bugs.gentoo.org/828001
enable_year2038="no"
+
+# Sam James <sam@gentoo.org> (2024-01-22)
+# Workaround for sandbox bug which causes this gnulib configure test to take
+# many real hours on slower machines, and certainly a huge amount of CPU hours
+# on others. Spoof the same result as configure gets on a modern glibc system
+# for now. See bug #447970 and bug #922652.
+gl_cv_func_getcwd_path_max="yes"
diff --git a/profiles/features/musl/make.defaults b/profiles/features/musl/make.defaults
index 3078bdd61b09c..ca792276e3945 100644
--- a/profiles/features/musl/make.defaults
+++ b/profiles/features/musl/make.defaults
@@ -17,3 +17,10 @@ FEATURES="-multilib-strict"
# that use a charset, it causes package collisons.
# Note: we use a full path for locale.alias for bug #799437
INSTALL_MASK="charset.alias /usr/share/locale/locale.alias"
+
+# Sam James <sam@gentoo.org> (2024-01-22)
+# Workaround for sandbox bug which causes this gnulib configure test to take
+# many real hours on slower machines, and certainly a huge amount of CPU hours
+# on others. Spoof the same result as configure gets on a modern musl system
+# for now. See bug #447970 and bug #922652.
+gl_cv_func_getcwd_path_max="no, but it is partly working"
--
2.43.0
next reply other threads:[~2024-01-22 16:15 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-22 16:14 Sam James [this message]
2024-01-22 16:35 ` [gentoo-dev] [PATCH] profiles: workaround sandbox bug with getcwd() configure test (gl_cv_func_getcwd_path_max) David Seifert
2024-01-22 16:45 ` [gentoo-dev] " Arsen Arsenović
2024-01-23 3:32 ` [gentoo-dev] [PATCH] cargo.eclass: add CARGO_TOML_DIR orbea
2024-01-23 3:48 ` Michał Górny
2024-01-23 14:13 ` orbea
2024-01-23 16:48 ` Michał Górny
2024-01-23 19:43 ` orbea
2024-01-24 18:59 ` orbea
2024-01-23 4:06 ` Eli Schwartz
2024-01-23 14:11 ` orbea
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=20240122161434.991554-1-sam@gentoo.org \
--to=sam@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=musl@gentoo.org \
--cc=sandbox@gentoo.org \
--cc=toolchain@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