From: Ross Burton <ross.burton@arm.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH] classes/base: prefer gnu-prefixed HOSTTOOLS
Date: Wed, 29 Oct 2025 13:03:10 +0000 [thread overview]
Message-ID: <20251029130310.2882818-1-ross.burton@arm.com> (raw)
Ubuntu 25.10 has changed the default coreutils implementation from GNU
coreutils to uutils/coreutils. Unfortunately this causes build problems:
couldn't allocate absolute path for 'null'.
tail: cannot open 'standard input' for reading: No such file or directory
install: failed to chown '...': Invalid argument (os error 22)
Clear build failures happen in 'install' and 'tail', but there may be
further breakage.
Luckily, Ubuntu also installs GNU coreutils with a binary prefix of
'gnu', so whilst these issues are root-caused and fixed in either pseudo
or uutils we can prefer the gnu-prefixed binaries where they are present.
[ YOCTO #16028 ]
Signed-off-by: Ross Burton <ross.burton@arm.com>
---
meta/classes-global/base.bbclass | 6 +++++-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/meta/classes-global/base.bbclass b/meta/classes-global/base.bbclass
index 6de17d1bb5d..cf303c237a5 100644
--- a/meta/classes-global/base.bbclass
+++ b/meta/classes-global/base.bbclass
@@ -127,7 +127,11 @@ def setup_hosttools_dir(dest, toolsvar, d, fatal=True):
# clean up dead symlink
if os.path.islink(desttool):
os.unlink(desttool)
- srctool = bb.utils.which(path, tool, executable=True)
+
+ # Prefer gnu-prefixed binaries, if available
+ srctool = (bb.utils.which(path, "gnu" + tool, executable=True) or
+ bb.utils.which(path, tool, executable=True))
+
# gcc/g++ may link to ccache on some hosts, e.g.,
# /usr/local/bin/ccache/gcc -> /usr/bin/ccache, then which(gcc)
# would return /usr/local/bin/ccache/gcc, but what we need is
--
2.43.0
next reply other threads:[~2025-10-29 13:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-29 13:03 Ross Burton [this message]
2026-02-16 9:32 ` [OE-core] [PATCH] classes/base: prefer gnu-prefixed HOSTTOOLS Ernst Persson
2026-02-16 10:25 ` Yoann Congal
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=20251029130310.2882818-1-ross.burton@arm.com \
--to=ross.burton@arm.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