From owner-freebsd-emulation@FreeBSD.ORG Thu Jan 12 14:38:29 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 5C1221065673 for ; Thu, 12 Jan 2012 14:38:29 +0000 (UTC) (envelope-from martin@lispworks.com) Received: from lwfs1-cam.cam.lispworks.com (mail.lispworks.com [193.34.186.230]) by mx1.freebsd.org (Postfix) with ESMTP id C7D258FC19 for ; Thu, 12 Jan 2012 14:38:28 +0000 (UTC) Received: from higson.cam.lispworks.com (higson [192.168.1.7]) by lwfs1-cam.cam.lispworks.com (8.14.3/8.14.3) with ESMTP id q0CEcPk9035530; Thu, 12 Jan 2012 14:38:25 GMT (envelope-from martin@lispworks.com) Received: from higson.cam.lispworks.com (localhost.localdomain [127.0.0.1]) by higson.cam.lispworks.com (8.14.4) id q0CEcPeq028421; Thu, 12 Jan 2012 14:38:25 GMT Received: (from martin@localhost) by higson.cam.lispworks.com (8.14.4/8.14.4/Submit) id q0CEcPFV028417; Thu, 12 Jan 2012 14:38:25 GMT Date: Thu, 12 Jan 2012 14:38:25 GMT Message-Id: <201201121438.q0CEcPFV028417@higson.cam.lispworks.com> From: Martin Simmons To: freebsd-emulation@freebsd.org In-reply-to: <4F0DCB3C.4060807@gmail.com> (message from Chuck Burns on Wed, 11 Jan 2012 11:47:40 -0600) References: <201201092017.19776.naylor.b.david@gmail.com> <4F0B2FC4.7090002@gmail.com> <201201101849.29845.naylor.b.david@gmail.com> <4F0CC7A4.4010707@gmail.com> <201201111624.q0BGOLlk030092@higson.cam.lispworks.com> <4F0DCB3C.4060807@gmail.com> 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, 12 Jan 2012 14:38:29 -0000 >>>>> On Wed, 11 Jan 2012 11:47:40 -0600, Chuck Burns said: > > On 01/11/12 10:24, Martin Simmons wrote: > >>>>>> On Tue, 10 Jan 2012 17:20:04 -0600, Chuck Burns said: > >> > >> On 01/10/12 10:49, David Naylor wrote: > >>> I wasn't aware of WoW64 (and how it will make my packages redundent :->). I > >>> see there are two wiki pages: > >>> + http://wiki.winehq.org/Wine64 > >>> + http://wiki.winehq.org/Wine64ForPackagers > >>> > >>> 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. > >>> > >>> 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@freebsd.org mailing list > > http://lists.freebsd.org/mailman/listinfo/freebsd-emulation > > To unsubscribe, send any mail to "freebsd-emulation-unsubscribe@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. __Martin