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

[pkg-wine-party] Bug#770813: 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
Version: 1.6.2-16
Severity: normal

I have a number of project written in C that I cross compile from Linux
to Windows. These projects often have test programs also written in C
and these I run under Wine.

This all works fine when I'm compiling 32 bit windows binaries but for
64 bit binaries there's a bit of a problem, the /usr/bin/wine script
fails for 64 bit windows binaries although if I set some environment
variables I can run 64 bit binaries, eg:

    WINARCH=wine64 WINEPREFIX=~/.wine64 wine hello64.exe

My suggestion is that if $WINEARCH and $WINEPREFIX are both empty
strings, the script could use the file command to figure out whether
the binary is 32 or 64 bits and set those variables appropriately.

-- System Information:
Debian Release: jessie/sid
  APT prefers testing
  APT policy: (900, 'testing'), (800, 'unstable'), (500, 'experimental')
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.17-rc5-amd64 (SMP w/4 CPU cores)
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8) (ignored: LC_ALL set to en_AU.UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages wine depends on:
ii  file    1:5.20-2
ii  wine32  1.6.2-16
ii  wine64  1.6.2-16

wine recommends no packages.

Versions of packages wine suggests:
pn  avscan | klamav | clamav   <none>
ii  binfmt-support             2.1.5-1
ii  ttf-mscorefonts-installer  3.6
pn  winbind                    <none>

-- no debconf information

--- 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: