-
-
Notifications
You must be signed in to change notification settings - Fork 407
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Workaround missing /usr/bin/wine64. #2035
Workaround missing /usr/bin/wine64. #2035
Conversation
f9418a4
to
872c944
Compare
I appreciate the patch, but not everyone has wine installed in /usr/bin ;). This will need a more general solution (see also #2030). |
Also only the gnu version of readlink supports -f, using that option would effectively break winetricks on platforms that don’t use gnu utility’s. |
FWIW, the version of readlink that I see on macOS 12.6 (gcc104 from https://cfarm.tetaneutral.net/machines/list/): supports |
Hum So maybe macOS Monterey (12.x) and macOS Ventura (13.x) have a new enough version of Might need to require |
I just want to clarify that Winetricks won't be "broken" if readlink -f is not working. Only this specific workaround wouldn't work. |
Does austin987@05c43b5 work for the debian package? |
Unfortunately not, even with the -preloader packages installed. Their binaries are also only installed to Wine's bindir (I just had a quick glance at the commit, but I assume that's the issue).
|
I've tested on the latest Debian Docker container and PR seems to fix the problems as per #2119 (comment). |
I have the same problem with WineGUI, it impact various distros now. And you're indeed correct there is no wine64 binary, but only a I hope a final solution can soon be released for Winetricks, solving this urgent issue once and for all. |
f1ed0c9
to
f77baf6
Compare
I updated this PR for both issues mentioned here before: Instead of hardcoding /usr/bin/wineboot I use WINESERVER_BIN to figure out wineboot's path. If this doesn't work there shouldn't be a regression, just a missed opportunity to figure out where wine64 might be after other attempts also failed. readlink exists on MacOS, but does not support "-f" on MacOS < 12.3. So I use perl there now. There are further readlink-related optimizations possible which I might implement with the help of some MacOS users if someone thinks it's worth the effort (I don't). See https://stackoverflow.com/questions/1055671/how-can-i-get-the-behavior-of-gnus-readlink-f-on-a-mac
Feedback and testing welcome, especially from MacOS users. EDIT: the new commit b449a07 below just fixes the commit message, no changes. |
f77baf6
to
b449a07
Compare
b449a07
to
9b0b98c
Compare
Updated to allow for parent dirs containing wineserver in their name (same as in PR 2189) |
Hopefully @austin987 now agrees with this. |
9b0b98c
to
2b71d0e
Compare
I moved the basics for determining Wine's bindir (readlink and wineboot) to a place where it can be used both for determining the wineserver and wine arch (#2189), and the wine64-only-in-BINDIR workaround (this PR). These basics are in a seperate commit that is shared by both PRs. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks @Chiitoo, and sorry for the delay in reviewing!
Workaround case where wine and related binaries are in /usr/bin, but wine64 is only in Wine's bindir (as in Debian wine 8.0~repack-4). Use /usr/bin/wineboot (which is a symlink in Debian packaging) to figure out the bindir, because /usr/bin/wine is a wrapper script in Debian.
See discussion in https://bugs.debian.org/1031649.
I'm not sure if this already should be added in Winetricks, probably this depends on the next set of Debian Wine packages. For now I applied this patch in Debian.
Tested with the deb packages from Debian wine 8.0~repack-2 and 8.0~repack-4, and Winehq winehq-staging 8.2~bookworm-1.