Sorry about that. I didn't quite understand the post but can see he wants a pure 64 bit wine application rather to run only 64 bit windows applications.
If you glance on
this page,
There's more info in the comments section.
Quote:
You may be confusing the fact that I built wine to run on a 64-bit Slackware… but the wine binaries are still 32-bit binaries. The version of wine which my SlackBuild creates can only run 32-bit Windows programs.
You can compile wine differently on a x86_64 platform, and then you will get “wine64″ which is able to run 64-bit Windows programs. This version of wine allows 64-bit Windows programs to call 32-bit Windows programs and vice versa.
See http://wiki.winehq.org/Wine64 . I have been wanting to try this for my x86_64 package but have not gotten around to actually do it, mostly because of reports of instabilities and the fact that there are not so many purely 64-bit WIndows programs yet.
And yes, running “WINEARCH=win32 winecfg” will require that you delete your existing .wine directory.
That is why I suggested the alternative approach in my main article, to define a different WINEPREFIX and give each Windows program you want to run its own “.wine” directory.
|
No I didn't expect an answer. Chromium is working good. It certainly bugged something there compared to an out of the box install. It has been really helpful ever since making /root directory a separate 20gb partition for these type situation
