Thank you all,
I've recently found this possible solution that it's native to Guix: <https://guix.gnu.org/en/blog/2023/the-filesystem-hierarchy-standard-comes-to-guix-containers/>. So there we have the technical words we were looking for, since Guix System does not conform with FHS the binary did not work. But if I execute it in a shell container with a FHS emulated file system then it would probably work (I've to try it yet)! Best regards, Marius. El 21 de noviembre de 2024 11:31:33 UTC, woshilapin <woshila...@tuziwo.info> escribió: >Hi Marius, > >> I'm trying to execute a pre compiled program (on a Guix System) that I think >> is trying to call /lib64/ld-linux-x86-64.so.2 by its absolute path. Since >> Guix System does use the store and usually makes use of variables like >> "SHELL", "LIBRARY_PATH", etc. How do I wrap executables that technically are >> gnu-linux cross platform but use absolute paths that depend on distribution? > >It might not be exactly the same problem, but I remember getting around this >kind of problem by providing guix's version of the library with >`LD_LIBRARY_PATH`. Doing something like this. > >``` >eval "$(guix shell --search-paths)" >export LD_LIBRARY_PATH="${LIBRARY_PATH}" >``` > >It's probably a horrible hack (I honestly don't know enough to know if it's >nice or horrible), but it got me something to work with. > >Hope this helps, and I'd be happy to know of a cleaner solution. > >Sincerely, >-- >woshilapin / Jean
