At present the only way to get wine to run on an amd64 box is to install a binary version from somewhere, several people on the forums have suggested unpacking a fedora core rpm into / which is IMO not such a great idea. Attached is an ebuild for a 32bit binary version of wine that can be used on amd64. I created the binarys on an amd64 box inside a 32bit chroot using the latest stable x86 wine ebuild. This seems to work just fine with the latest emul-linux-x86-* libs. Reproducible: Always Steps to Reproduce: 1. 2. 3.
Created attachment 39516 [details] wine-bin ebuild
So how is one supposed to use this ebuild? What's version etc?
err, yes sorry. I forget that bugzilla does not show the origional file name... Save the ebuild as wine-bin-20040408.ebuild and then create your digest etc.
Thanks! This works.
could you try editing the 20041019 wine ebuilds and adding --enable-win64 to the configure options ? i dont think it'll do what you want according to the description: --enable-win64 build a Win64 emulator on AMD64 (won't run Win32 binaries)
vapier: tried this out, ran into an error quite quickly interlocked.c:299:3: #error You must implement the interlocked* functions for your CPU I guess the win64 emulator is not ready yet. Even if this did work there would still be a need for a wine-bin ebuild to enable people to run win32 binaries. Maybe the wine-bin ebuild should be a wine32-bin ebuild and install to /usr/bin/wine32 to make it installable alongside a 64bit wine. I would be happy to make that change if I thought this might get added to portage, would I be wasting my time?
While this is a nice way to do it, it does require someone regular build a win32 wine in order to keep this package up to date. Has anyone tried any of the binary packages winehq makes available? http://www.winehq.org/site/download Would an ebuild using one of those make a little more sense?
Sounds right to me. There is a good how-to at http://forums.gentoo.org/viewtopic.php?t=152597&postdays=0&postorder=asc&start=0 that explains the process for this. I used the binaries for Fedora Core 3, however Fedore Core 1 binaries also work (according to the thread). I agree; a wine-bin ebuild for AMD64 users might be very popular.
This ebuild works on ia32 as well, provided one removes the emulation dependency. Might as well make that a platform-conditional dependency and mark it testing for x86 too.
Works for me, thank you. ~Amd64 2004.3
These seem to have sat here for a while now with no signs of them getting added to portage. I have updated the binarys now to match the current x86 ebuild version. This seems to have fixed the probs I was having with 2.6.10 kernels. I've also provided a .tar.bz2 of my overlay to make it easier to ppl to install even if these never get added to portage. Istallation instructions ----------------------- The following assumes that you are running a Gentoo system on amd64 and that you have PORTDIR_OVERLAY=/usr/local/portage set in /etc/make.conf. 1. cd /usr/local/portage 2. wget http://fermat.ma.rhul.ac.uk/wine-bin/wine-bin-overlay.tar.bz2 3. tar -jxvf wine-bin-overlay.tar.bz2 4. emerge wine-bin
Works. amd64, 2004.3, gcc-3.4.3, glibc-2.3.4.20041102-r0, 2.6.7-gentoo-r14 Thanks. This should be included in portage!!! :)
Thank you Mr. Hopkins, this works really well on my AMD64 system.
Created attachment 52322 [details] ebuild using winehq.org builds Simple ebuild to use the fedora core 3 rpm based ebuild from winehq.org. The following wine dll's are incomplete: glut32.dll.so (libglut.so.3 not found) twain.dll.so, twain32_dll.so (libsane.so.1, libusb-0.1.so.4, and libieee1284.so.3 not found) winealsa.drv.so (libasound.so.2 not found, it's installed via emul-linux-x86-soundlibs-1.0-r1, so not sure why it's not found) winearts.drv.so (libartsc.so.0 not found) None of the above are critical components, and are likely broken no matter what binary form of wine is installed. Comments, input? It could be modified so that the devel packages are only installed with a use flag (or not even installed, not sure how useful they really on in amd64 system). No offense to Herbie, but I think this ebuild is more ideal as it doesn't require someone to maintain a seperate wine binary build, and instead we can use one of the pre-existing ones. It'd be nice to see this get into portage.
wine now compiles natively on gentoo amd64, well sort of ;) see bug 82758 . Which kind of removes the need for a wine-bin ebuild. The patch in the linked bug enables the wine ebuild to compile an x86 version of wine on amd64 using multilib. There are however some problems with pre 2005.0 profiles i.e it fails to compile against the binary glibc version.
Is possible to have both wine-bin and the wine from bug #82758 ?
it would not be advisable no, as both create wine executables.
Wine should now compile on amd64 using multilib. Resolving as WONTFIX since this is a cleaner solution.
For me 2004.3 multilib wasn't good enough. Wine only managed to compile after I updated to 2005.0 multilib http://www.gentoo.org/proj/en/base/amd64/howtos/index.xml?part=1&chap=1#doc_chap1
