https://bugs.winehq.org/show_bug.cgi?id=54941
--- Comment #4 from Francisco Casas fcasas@codeweavers.com ---
(What is the logic behind using different file hierarchy structures between the 32-bit and 64-bit parts of the same project?)
When working with containers, it is often convenient to mount a directory from the host within the container:
podman run -dt --name debian-cont --mount="type=bind,source=/home/fcasas/Builds/,destination=/root/Builds" docker.io/library/debian
In this case, I mounted /home/fcasas/Builds/ in /root/Builds (since the container doesn't have the "fcasas" username).
Please test the attached patch.
Does it fix the issue or break anything?
Regards.
I applied the patch and recompiled everything in a fresh directory inside the container.
The injected symlinks, which in this case are located in
/root/Builds/temp/wine64/loader
Still end up with absolute paths:
lrwxrwxrwx 1 root root 36 May 16 00:12 wine -> /root/Builds/temp/wine32/loader/wine lrwxrwxrwx 1 root root 46 May 16 00:12 wine-preloader -> /root/Builds/temp/wine32/loader/wine-preloader
So in the host system, where the route is
/home/fcasas/Builds/temp/wine64/loader
they are broken.