https://bugs.winehq.org/show_bug.cgi?id=54941
--- Comment #8 from Francisco Casas fcasas@codeweavers.com --- (In reply to Olivier F. R. Dierick from comment #7)
It doesn't matter that the username doesn't exist. You may create the /home/fcasas/Builds inside the container and bind directly to it, or make /home/fcasas/Builds as a symlink to /root/Builds. Build from /home/fcasas/Builds in the container. With everything in place just like on the host you should get the right paths.
Yes, that is an easy solution, but the user has to be aware of it. If we keep it, I suggest we mention this in the "Containers" section of the "Building Wine" wiki page.
Using relative paths may be better though, since it would also allow the user to move their build folders to another directory (as long as it is the same for all of them).
(In reply to Olivier F. R. Dierick from comment #7)
(In reply to Francisco Casas from comment #4)
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:
I forgot to say that you have to run autoconf after applying the patch. Did you?
Yes, I configured and build everything from scratch in another directory, starting solely from a fresh copy of the wine source code with the patch applied.