Date: Thu, 19 Nov 2009 07:38:18 +0000 From: xorquewasp@googlemail.com To: Julian Elischer <julian@elischer.org> Cc: freebsd-hackers@freebsd.org Subject: Re: Wine on amd64 in 32 bit jail Message-ID: <20091119073818.GA81272@logik.internal.network> In-Reply-To: <4B04F172.7070803@elischer.org> References: <20091119065742.GA28159@logik.internal.network> <4B04F172.7070803@elischer.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 2009-11-18 23:19:14, Julian Elischer wrote: > > Wine is an exceptional bit of software, in many ways. > One way it is exceptional is that it uses the system in a number of > ways that nothing else does. For example it sets various special > segment register settings and defines several different > segments on the LDT. This is something that is different to some > extent between i386 and amd64 and it is possible that > the code for 386 LDT syscalls under amd64 may not work correctly. > nothing else would test this. > I agree and would also have likely not even tried if it wasn't for reading on FreeBSD's own wiki (amonst other places) that it should actually work fine. I've tried various versions and always get the same result: http://wiki.freebsd.org/Wine "FreeBSD currently lacks support for 32bit ports on a 64bit system. However, with a little bit of effort you can build and use the 32 bit wine executable on an amd64 system (Diablo 2 works just fine)." His instructions show an essentially identical setup to mine (apart from the fact that he's running a chroot and I'm running a jail). Even any ideas on how to debug this would help. xw
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20091119073818.GA81272>