[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

[pkg-wine-party] Bug#769234: marked as done (wine: automatically detect and launch wine32 or wine64)

Your message dated Sun, 10 Jan 2016 16:56:27 +0100
with message-id <56927F2B.2050106@gmail.com>
and subject line Re: Bug#769234: wine: automatically detect and launch wine32 or wine64
has caused the Debian Bug report #769234,
regarding wine: automatically detect and launch wine32 or wine64
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
769234: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=769234
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: wine-binfmt
Version: 1.6.2-16

Back on wheezy `wine` shell script used to do the following trick to
decide to call wine32 or wine64 using:

[...]
wine=/usr/bin/wine32
if test "$(file -b -L "$1" | cut -d\  -f1)" = "PE32+" -o "$WINEARCH" =
"win64"; then
    wine=/usr/bin/wine64
fi
[...]

This made it possible to execute: $ ./bla.exe without knowing whether
or not bla.exe was meant for x64 arch ahead of time.

Please resurrect this code path in current wine. I'm affecting the bug
to binfmts since it really lies at this level, feel free to reassign
to `wine` package (package which used to provide the wine indirection
described above).

Alternate solution:

Technically a new magic number could used to decide to call wine64
and/or wine32 since the binary files differ:

 $ file bla.exe
 bla.exe: PE32 executable (console) Intel 80386, for MS Windows
 $ file bla2.exe
 bla2.exe: PE32+ executable (console) x86-64, for MS Windows

Eg:


$ cat /usr/share/binfmts/wine32
package wine-binfmt
interpreter /usr/bin/wine32
magic XYZ

$ cat /usr/share/binfmts/wine64
package wine-binfmt
interpreter /usr/bin/wine64
magic UVW

This is a simplification of #733556, which I'll close shorty.

--- End Message ---
--- Begin Message --- 
version:1.8-2

On 12/31/2015 09:49 PM, Jens Reyer wrote:
> Instead the complete WoW64 setup seems to be possible and imo is a
> better solution, see #762058.

Wine now supports and uses shared WoW64/64-bit wineprefixes if wine,
wine32 and wine64 are installed. So this should work now for all newly
created default (=64-bit) prefixes and existing 64-bit prefixes.

WoW64 works in Wine by adapting the /usr/bin/wine script, adding a
/usr/bin/wineserver script that defaults to the 64-bit wineserver, and
not installing wineserver in wine's configured bindir (= libdir)
(/usr/lib/*/wine/wineserver).

I hope this turns out well, I experienced no issues when testing locally.

jre

--- End Message ---
Reply to: