https://bugs.winehq.org/show_bug.cgi?id=53529
Bug ID: 53529 Summary: Make possible to use wine with custom ld-linux.so.2 32-bit preloader, without hacks Product: Wine Version: 7.14 Hardware: x86-64 OS: Linux Status: UNCONFIRMED Severity: normal Priority: P2 Component: -unknown Assignee: wine-bugs@winehq.org Reporter: ruanformigoni@gmail.com Distribution: ---
Some references of this limitation of wine:
- https://github.com/AppImage/AppImageKit/wiki/Bundling-Windows-applications - https://github.com/Hackerl/Wine_Appimage/issues/11 - https://github.com/AppImage/AppImageKit/issues/361
The issue is that, although it is possible to use another preloader, wine seems to launch instances that still use the standard ld.so.2 path instead of the modified one.
More details:
- https://www.winehq.org/pipermail/wine-devel/2017-November/119906.html - https://www.winehq.org/pipermail/wine-devel/2017-November/119944.html
https://bugs.winehq.org/show_bug.cgi?id=53529
formigoni ruanformigoni@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Summary|Make possible to use wine |Use wine with custom |with custom ld-linux.so.2 |ld-linux.so.2 32-bit |32-bit preloader, without |preloader, without hacks |hacks |
https://bugs.winehq.org/show_bug.cgi?id=53529
--- Comment #1 from Alexandre Julliard julliard@winehq.org --- Did you try the suggested hack? Does it work?
https://bugs.winehq.org/show_bug.cgi?id=53529
--- Comment #2 from formigoni ruanformigoni@gmail.com --- (In reply to Alexandre Julliard from comment #1)
Did you try the suggested hack? Does it work?
Thanks for the reply. I Managed to get it working with this guide:
- https://github.com/AppImage/AppImageKit/wiki/Bundling-Windows-applications
The other pre-packaged wine versions would segfault for me, so creating the appimage was the way to go. To know all the information needed to do this, and find these useful links, took me a few days of research and understanding libc, library paths, preloader, etc. That is why I opened this issue, creating 32-bit portable wine applications is really appealing, but for someone else that has less knowledge it might not be viable or too time consuming.
So as stated in the guide, it would be nice to solve this issue just with this snipped, as is for other programs:
wget -c http://security.ubuntu.com/ubuntu/pool/main/g/glibc/libc6-i386_2.24-9ubuntu2... dpkg -x ./libc6*.deb .
HERE="$(dirname "$(readlink -f "${0}")")"
WINEPREFIX="$HERE/wineprefix/" \ "$HERE/lib32/ld-linux.so.2" \ --library-path "$HERE/lib32" \ "$HERE/wine-stable/bin/wine" \ "$WINEPREFIX/drive_c/Program Files/App/App.exe" "$@"
https://bugs.winehq.org/show_bug.cgi?id=53529
--- Comment #3 from Alexandre Julliard julliard@winehq.org --- OK, I see. That's probably good enough for now.
The plan is to make it possible to run 32-bit apps with only 64-bit host libraries, so that would be a better long term strategy that adding hacks for the 32-bit ld-linux.so.
https://bugs.winehq.org/show_bug.cgi?id=53529
formigoni ruanformigoni@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |FIXED Status|UNCONFIRMED |RESOLVED
--- Comment #4 from formigoni ruanformigoni@gmail.com --- Fixed by wow64 in jammy builds.
https://bugs.winehq.org/show_bug.cgi?id=53529
Zeb Figura z.figura12@gmail.com changed:
What |Removed |Added ---------------------------------------------------------------------------- CC| |z.figura12@gmail.com
--- Comment #5 from Zeb Figura z.figura12@gmail.com --- (In reply to formigoni from comment #4)
Fixed by wow64 in jammy builds.
What do you mean by this? wow64 isn't fully implemented upstream...
https://bugs.winehq.org/show_bug.cgi?id=53529
--- Comment #6 from formigoni ruanformigoni@gmail.com --- Hi, although that is the case, the issues seems to be fixed. The "No such file or directory" is gone and wine opens. I conducted some testing here: https://github.com/mmtrt/WINE_AppImage/issues/15, an appimage built on ubuntu jammy works on focal and bionic, without the need to install libc6-i386.
https://bugs.winehq.org/show_bug.cgi?id=53529
Alexandre Julliard julliard@winehq.org changed:
What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |CLOSED
--- Comment #7 from Alexandre Julliard julliard@winehq.org --- Closing bugs fixed in 7.22.