wineapploader in wine64
Hi, Any explanation for why the wineapploader script doesn't use 'wine64' instead of 'wine' in a 64bit Linux with 64bit wine? That's the script that is used to build /usr/bin/wineboot and /usr/bin/regedit, for instance. In Fedora 15 with wine 1.3.24, the upshot is that the 'wineboot' command doesn't work. /usr/lib/wine/wineboot.exe.so is not installed; only /usr/lib64/wineboot.exe.so is. Since the /usr/bin/wineboot is running 'wine' instead of 'wine64' it is looking for the 32bit /usr/lib/wine/wineboot.exe.so. It can't be found since it isn't installed so the loader gives up.
$ wineboot wine: cannot find L"C:\\windows\\system32\\wineboot.exe"
If it used wine64 instead, it would work. There must be a reason that wine64 is starting 32bit apps, but I haven't been able to glean anything from the web. Thanks for any info, -- Michael Ost
Michael Ost <most(a)museresearch.com> writes:
In Fedora 15 with wine 1.3.24, the upshot is that the 'wineboot' command doesn't work. /usr/lib/wine/wineboot.exe.so is not installed; only /usr/lib64/wineboot.exe.so is.
Since the /usr/bin/wineboot is running 'wine' instead of 'wine64' it is looking for the 32bit /usr/lib/wine/wineboot.exe.so. It can't be found since it isn't installed so the loader gives up.
It could be considered it a bug, but 64-bit-only setups are not really supported. You need to have the 32-bit side, if only to create a valid prefix (besides, there shouldn't be any reason to run wineboot by hand). -- Alexandre Julliard julliard(a)winehq.org
On Thu, Feb 16, 2012 at 14:21, Vincent Pelletier <plr.vincent(a)gmail.com> wrote:
Le jeudi 16 février 2012 20:57:10, Alexandre Julliard a écrit :
(besides, there shouldn't be any reason to run wineboot by hand).
FWIW, on wine (32bits) I use "wineboot -ks" to get rid of a crashing app (stuck eating cpu, or just willing to stay).
Most people use `wineserver -k` for that. -- -Austin
Le jeudi 16 février 2012 21:27:37, Austin English a écrit :
Most people use `wineserver -k` for that.
Woops, missed your reply. The problem with wineserver is, with debian packages, that it's not available through PATH (http://packages.debian.org/sid/amd64/libwine-unstable/filelist : /usr/lib32/wine-unstable/wineserver). But I take note anyway, as I usually build wine myself than use distro packages. -- Vincent Pelletier
On 02/16/2012 11:57 AM, Alexandre Julliard wrote:
prefix (besides, there shouldn't be any reason to run wineboot by hand).
We use it with --shutdown to cleanly terminate (as in WM_CLOSE, not "kill") all wine apps from a hardware button press. Is there a preferred way? Thanks! -- Michael Ost
Michael Ost <most(a)museresearch.com> writes:
On 02/16/2012 11:57 AM, Alexandre Julliard wrote:
prefix (besides, there shouldn't be any reason to run wineboot by hand).
We use it with --shutdown to cleanly terminate (as in WM_CLOSE, not "kill") all wine apps from a hardware button press. Is there a preferred way?
No that's OK, though in general I'd suggest using 'wine64 wineboot' in scripts so that you don't depend on the /usr/bin wrapper scripts. -- Alexandre Julliard julliard(a)winehq.org
participants (4)
-
Alexandre Julliard -
Austin English -
Michael Ost -
Vincent Pelletier