From owner-freebsd-amd64@FreeBSD.ORG Sun Dec 31 02:02:19 2006 Return-Path: X-Original-To: freebsd-amd64@freebsd.org Delivered-To: freebsd-amd64@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 7472216A403 for ; Sun, 31 Dec 2006 02:02:19 +0000 (UTC) (envelope-from nathanw@uchicago.edu) Received: from vms046pub.verizon.net (vms046pub.verizon.net [206.46.252.46]) by mx1.freebsd.org (Postfix) with ESMTP id 568D013C46C for ; Sun, 31 Dec 2006 02:02:19 +0000 (UTC) (envelope-from nathanw@uchicago.edu) Received: from [192.168.0.100] ([71.243.84.150]) by vms046.mailsrvcs.net (Sun Java System Messaging Server 6.2-6.01 (built Apr 3 2006)) with ESMTPA id <0JB400HQN8AK5OZB@vms046.mailsrvcs.net> for freebsd-amd64@freebsd.org; Sat, 30 Dec 2006 20:02:09 -0600 (CST) Date: Sat, 30 Dec 2006 21:02:08 -0500 From: Nathan Whitehorn In-reply-to: <20061231003901.GA76688@slackbox.xs4all.nl> To: Siavosh Benabbas , freebsd-amd64@freebsd.org Message-id: <3AE0FE6A-EA8A-44A0-98A5-E2D7E28BC38A@uchicago.edu> MIME-version: 1.0 (Apple Message framework v752.2) X-Mailer: Apple Mail (2.752.2) Content-type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Content-transfer-encoding: 7bit References: <32d8477c0612301410q2aaf9d39k859d242739554fd6@mail.gmail.com> <20061231003901.GA76688@slackbox.xs4all.nl> Cc: Subject: Re: i386_set_ldt and wine on AMD64 X-BeenThere: freebsd-amd64@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Porting FreeBSD to the AMD64 platform List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 31 Dec 2006 02:02:19 -0000 On Dec 30, 2006, at 7:39 PM, Roland Smith wrote: > On Sat, Dec 30, 2006 at 05:10:08PM -0500, Siavosh Benabbas wrote: >> Hi, >> I know that this is brought up several time on this list, but I >> wanted to >> run wine on my FreeBSD AMD64 machine. >> I know that a 64-bit wine is nearly impossible but I thought that >> an i386 >> compilation should work. > > You'd need a cross-compiler to start with. That's the easy part. > > Then you'd need ports infrastructure to compile 32-bit ports on > amd64. At > this moment that doesn't exist yet: > http://wikitest.freebsd.org/G%C3%A1borK%C3%B6vesd%C3%A1n > > This could be a _huge_ undertaking, because things like patches and > parts > of the port Makefile might depend on if you're cross-compiling or > not. I'm not sure if that is worth the effort. Time might be better > spent getting ports to compile natively for all supported platforms > and > using a virtual machine for things that don't work. > > Then you'd need to compile 32 bit versions of all the libraries > that wine > depends on. If you have a look at the dependancies of wine, and > recurse > through them, you'll see that this is a lot of libraries. > > Do you have any programs that require amd64 because of address > space or > other concerns? (if you have processes that run out of memory, have > you > played with the kernel tunables? See /boot/defaults/loader.conf) > Otherwise, why not run i386 if you require wine? One thing you can do (I had to do this for ghostscript, which is broken on amd64) is to set up a second machine with i386, build the ports there, too, and then run the binaries out of an NFS-mounted / usr/local/bin32. This requires also setting up a lib32 to go with it, and setting up some scripts to set LD_32_LIBRARY_PATH to the right things (ldconfig -32 is broken in interesting ways on 6-STABLE at the moment). Of course, with wine dynamically loading libraries at run time, it might have /usr/local/lib hardcoded into it and might break anyway. Hard to say. So, in sum: if you need wine, just run i386. -Nathan