From owner-freebsd-emulation@FreeBSD.ORG Thu Jan 19 19:57:52 2012 Return-Path: Delivered-To: freebsd-emulation@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 02E01106564A for ; Thu, 19 Jan 2012 19:57:52 +0000 (UTC) (envelope-from nerv@dawncrow.de) Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.126.186]) by mx1.freebsd.org (Postfix) with ESMTP id 903738FC0C for ; Thu, 19 Jan 2012 19:57:51 +0000 (UTC) Received: from [192.168.178.20] (pD9530439.dip0.t-ipconnect.de [217.83.4.57]) by mrelayeu.kundenserver.de (node=mreu0) with ESMTP (Nemesis) id 0MVHuk-1S9Iw90ITm-00ZAQ4; Thu, 19 Jan 2012 20:45:15 +0100 Message-ID: <4F1872C9.50000@dawncrow.de> Date: Thu, 19 Jan 2012 20:45:13 +0100 From: =?ISO-8859-15?Q?Andr=E9_Hentschel?= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:9.0) Gecko/20111220 Thunderbird/9.0 MIME-Version: 1.0 To: freebsd-emulation@freebsd.org Content-Type: text/plain; charset=ISO-8859-15 Content-Transfer-Encoding: 8bit X-Provags-ID: V02:K0:C5hXQXh/IzVyfaONMUcFcvoahqbH3V2Gzi74RQuiN2H zKAThsi3B6j02E4opY/wW6w00v7lQoSftIPLM+4pURKT9rHKXb vDij8U8y0ivFj7Ca9Z9DgHo/2ObWwvnSEaSYrsfWPMgN7zNR4H G8CXY/CrNUEgjGbzJmxEza3Nzs6HBxL7nfiXTyDIcHihTg1fxm Bm4O6+gV5Qjx9b6ckFWnf3GZD+0HaCOamVfK/5wlOuTzD/z6eD KTcdvBetHC7/x4PFtlOHw39+QnpGVVT6/FE1SKxJy1CUj58s8+ OKTbSjrAsGL8mdlWP37RKr5zem9YF7t76aqUO7+pSMstNvDkQZ 49hIAXteHn0U6JnbzlV8= X-Mailman-Approved-At: Thu, 19 Jan 2012 19:59:36 +0000 Subject: Re: Wine-fbsd64 updated to 1.3.36 (32bit Wine for 64bit FreeBSD) X-BeenThere: freebsd-emulation@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Development of Emulators of other operating systems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 19 Jan 2012 19:57:52 -0000 >> >>> The latter makes this statement "Wine 64bit works at the moment only on >> >>> Linux." which would indicate that, at this stage, FreeBSD is precluded. That, >> >>> however, is just my speculation. worth a try :) (be free to report bugs about not working on freebsd to wine as enhancement) >> >>> >> >>> To answer your question directly, I have put no thought or effort into wine64. >> >> >> >> There is still a need for the 32bit wine, as the wow64 build will ONLY >> >> run 64bit windows apps, so for the majority of applications and games, >> >> we'll still need the 32bit wine. >> > >> > Is that because wow64 is unstable in wine64? >> > >> > Wow64's reason for existence is to run 32-bit Windows binaries on 64-bit >> > Windows/Wine and it works pretty well for most applications. >> > >> > __Martin >> > _______________________________________________ >> > freebsd-emulation at freebsd.org mailing list >> > http://lists.freebsd.org/mailman/listinfo/freebsd-emulation >> > To unsubscribe, send any mail to "freebsd-emulation-unsubscribe at freebsd.org" >> wow64 doesnt -exist- in wine64 unless you compile the 32bit wine >> alongside it. >> >> You have to build it twice, to get two binaries "wine" and "wine64" and >> if you build them "properly" what happens when you attempt to execute a >> 64bit app with "wine" it's automatically relaunched with "wine64" But >> the reverse is NOT true. > > OK, that's what I would call unstable. Eventually though, I would expect a > packaged wine64 to include wow64, just like Windows does. That's not unstable, that's the way it needs to be done. To clarify this confusing thread: wine64 as standalone can run 64-bit windows apps (on a 64-bit processor of course) wine(32) can run 32-bit windows apps a wow64 setup means wine64 and wine(32) side by side with some exchange mechanisms to run 32-bit apps in the same wineprefix as 64-bit ones Linux distros handle packaging that differently: fedora uses the i386 package as a dependency, arch builds both together -- Best Regards, André Hentschel