Extra error output when running coreutils command in a yocto build environment #8914
Description
I have installed ubuntu 25.10 and I am doing yocto builds on this machine. The yocto build is using some of the coreutils in the build process.
The problem is that most of them print the error message: couldn't allocate absolute path for 'null'.
Here an extract of the strace output of running the command ls:
2207467 lstat("/usr", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
2207467 lstat("/usr/lib", {st_mode=S_IFDIR|0755, st_size=16384, ...}) = 0
2207467 lstat("/usr/lib/cargo", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
2207467 lstat("/usr/lib/cargo/bin", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
2207467 lstat("/usr/lib/cargo/bin/coreutils", {st_mode=S_IFDIR|0755, st_size=4096, ...}) = 0
2207467 lstat("/usr/lib/cargo/bin/coreutils/locales", 0x7ffdeb6e1d90) = -1 ENOENT (No such file or directory)
2207467 lstat("/usr/lib/cargo/bin/coreutils/locales/ls", 0x7ffdeb6e1d90) = -1 ENOENT (No such file or directory)
2207467 statx(AT_FDCWD, "/usr/lib/cargo/bin/coreutils/locales/ls", AT_STATX_SYNC_AS_STAT, STATX_ALL, 0x7ffdeb6e2040) = -1 ENOENT (No such file or directory)
2207467 rt_sigprocmask(SIG_SETMASK, [], NULL, 8) = 0
2207467 rt_sigprocmask(SIG_BLOCK, [HUP USR1 USR2 ALRM TERM CHLD], [], 8) = 0
2207467 write(2, "couldn't allocate absolute path for 'null'.\n", 44) = 44
Creating the following symbolic link, locales -> /usr/share/locales, inside the directory /usr/lib/cargo/bin/coreutils makes this message not printed anymore.