Status of WINE on amd64

[Michael Hopkins]

> 
> Michael Hopkins wrote:
> |
> | Hi all
> |
> | After having built a bunch of win32 executables on amd64 5.3 using
> mingw32,
> | I'm now keen to run them as well.
> |
> | I tried to build WINE from ports and was told i386 only, so cheated by
> | adding amd64 to the archs to see what happened.  Got quite a long way then
> | this:
> |
> | cc -c -I. -I. -I../../include -I../../include  -D__WINESRC__ -D_REENTRANT
> | -fPIC -Wall -pipe -fno-strict-aliasing -gstabs+ -Wpointer-arith
> | -I/usr/local/include -O2 -o interlocked.o interlocked.c
> | interlocked.c:299:3: #error You must implement the interlocked* functions
> | for your CPU
> | *** Error code 1
> |
> | Stop in /usr/ports/emulators/wine/work/wine-20050310/libs/port.
> | *** Error code 1
> |
> | Stop in /usr/ports/emulators/wine/work/wine-20050310/libs.
> | *** Error code 1
> |
> | Stop in /usr/ports/emulators/wine/work/wine-20050310.
> | *** Error code 1
> |
> |
> | Anyone have an idea how far we are from WINE working?
> |
> | How about building it within the Linux compatibility layer?  ;o)  I don't
> | need speed, just to test that some command line tools work properly.
> |
> | TIA
> |
> | Michael
> |
On 9/4/05 10:38 am, "Ulrik Guenther" <ulrik at 00t.org> wrote:

> 
> Heya,
> 
> I think this has been the state since for quite a while.
> Additionally, this is not meant to be easily fixed (nevertheless, you
> might want to have a look at the sourcecode). I'd suggest trying
> a binary version of wine under the linux compatibility layer.
> (There has been a report of somebody who got the binary version of
> WineX/Cedega running on i386, it might also be possible on amd64, but I
> have not tried it so far...)
> 
> Regards,
> 
> Ulrik


Hi Ulrik

I just tried this 10 minutes ago!  I installed the latest Redhat 8 WINE i386
RPMs into /compat/linux and branded the wine* ELFs etc, but trying to run it
gives this:

root at Athlon # /compat/linux/usr/bin/wine test
wine: failed to initialize: /usr/lib/wine/ntdll.dll.so: failed to map
segment from shared object: Cannot allocate memory

I wonder if building from source using linux_devtools might work better?

Michael


_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/

        _/    _/   _/_/_/             Hopkins Research Ltd
       _/    _/   _/    _/
      _/_/_/_/   _/_/_/          http://www.hopkins-research.com/
     _/    _/   _/   _/
    _/    _/   _/     _/               'touch the future'
                   
_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/_/