[Compatibility BUG]. Unusual additional system calls generated by uutils

uutils produces odd system calls (with null pathnames?) that are not present with GNU utils.

This causes oddities for processes running though pseudo (such as Yocto/OpenEmbeded builds).

This script (run on Kubuntu 25.10) shows the difference.

#!/bin/sh
# Assumes that pseudo is installed in /usr/bin
# and that libpseudo.so is in /usr/lib/x86_64-linux-gnu/pseudo/
#

# Set up the environment
#
rm -rf testenv testnew
mkdir -p testenv/bin testenv/var/pseudo
ln -s /usr/bin/pseudo testenv/bin/pseudo

# Set the environment variables to run pseudo
#
LD_PRELOAD=/usr/lib/x86_64-linux-gnu/pseudo/libpseudo.so
PSEUDO_PREFIX=`pwd`/testenv
export LD_PRELOAD PSEUDO_PREFIX

# GNU install
#
echo "Running GNU install"
gnuinstall -d -m 755 testnew/dir/here
find testnew
echo "remove testnew with GNU rm"
gnurm -rf testnew
echo "GNU test done"
echo

# uutils (Rust) install
#
echo "Running uutils install"
install -d -m 755 testnew/dir/here
find testnew
echo "remove testnew with uutils rm"
rm -rf testnew
echo "uutils test done"

The output from this is:

[gmllaptop]: ./test.sh 
Running GNU install
testnew
testnew/dir
testnew/dir/here
remove testnew with GNU rm
GNU test done

Running uutils install
couldn't allocate absolute path for 'null'.
testnew
testnew/dir
testnew/dir/here
remove testnew with uutils rm
couldn't allocate absolute path for 'null'.
uutils test done

Note the "couldn't allocate absolute path for 'null'." messages (from pseudo) messages produces by using uutils. From both the install and rm commands.
I suspect other commands do the same.

Run the supplied test.sh reproduction on Kubuntu with pseudo and compare GNU install/rm against the uutils commands. Trace the additional system calls or null pathnames from the install and rm entry points, then verify the pseudo warnings no longer appear and the behavior matches GNU utilities.