My last comment ("The issue seems to be fixed, even without the symlink for /usr/<cpu>-linux-gnu/etc/ld.so.cache.") was incorrect. When this symlink is set, the program accesses /etc/ld.so.cache after accessing /usr/<cpu>-linux-gnu/etc/ld.so.cache. In some cases, it works, in some cases it doesn't — depending on the contents of /etc/ld.so.cache.
The better fix is to replace /usr/<cpu>-linux-gnu/etc/ld.so.cache with an empty file:
My last comment ("The issue seems to be fixed, even without the symlink for /usr/<cpu> -linux- gnu/etc/ ld.so.cache. ") was incorrect. When this symlink is set, the program accesses /etc/ld.so.cache after accessing /usr/<cpu> -linux- gnu/etc/ ld.so.cache. In some cases, it works, in some cases it doesn't — depending on the contents of /etc/ld.so.cache.
The better fix is to replace /usr/<cpu> -linux- gnu/etc/ ld.so.cache with an empty file:
rm -f "/usr/< cpu>-linux- gnu/etc/ ld.so.cache" cpu>-linux- gnu/etc" cpu>-linux- gnu/etc/ ld.so.cache"
mkdir -p "/usr/<
: > "/usr/<