Hello Duncan: Pleae read my comments. On Sat Mar 13,2010 10:20 pm, Duncan wrote: > Volker Armin Hemmann posted on Sat, 13 Mar 2010 16:29:06 +0100 as > excerpted: > > > On Samstag 13 M??rz 2010, Mansour Al Akeel wrote: > >> Hello all, > >> > >> I have been looking into installing wine and a cross dev tool chain. I > >> didn't get much luck, since I have amd64 and I use no-multilib. I found > >> this http://bugs.gentoo.org/269439 and I am wondering if any one can > >> provide an advice. Is it be possible to run wine on amd64 with > >> no-multilib ? > > > > you won't be able to run any 32bit windows app. Which makes wine pretty > > useless. > > FWIW, I have no-multilib, but with the 32-bit compatibility turned on in > the kernel, I'm able to do the 32-bit chroot thing as in the gentoo/amd64 > documentation. > > In my case, I'm doing a full 32-bit chroot image, which then gets > transferred to my AA1 netbook. (The big machine has far more memory and > power to do the compiles, so it makes more sense to do that and not even > have the gentoo tree on the netbook, just transfer over the prebuilt, > preconfigured image, and rsync it again after every update. I've never > booted the 32-bit image on the big machine, tho, and indeed, couldn't, as > the kernel drivers, etc, are all built-in and configured for the netbook.)
Are you saying that you have another 32bit gentoo image, and you mount it somewhere and chroot to it? If so, what does the memory has to do with this ? Can you please elaborate on this ? The space is not a concern to me, but I'd rather not mix 32 and 64 libs. > > For just running 32-bit stuff on the same machine, tho, you'd not need the > full system image, as you'd be able to skip stuff like syslog and the > kernel, as they'd be 64-bit hosted. > > That'd give you the 32-bit stuff including wine in its own little chroot, > fully built from source as any Gentooer should appreciate, without > dirtying up your 64-bit-clean no-mulilib main install as the 32-bit stuff > would be in its own chroot, and without the compromise of the prebuilt 32- > bit libraries the typical multilib installation uses. It's a bit more > work to keep updated than a multilib install, but because the main install > is 64-bit clean no-multilib, you don't have the broken 32-bit toolchain > issues that seem to strike many multilib users after awhile. (...that I > got tired of after a few times, and that I was VERY glad to be rid of, > when I dumped multilib myself.) > > -- > Duncan - List replies preferred. No HTML msgs. > "Every nonfree program has a lord, a master -- > and if you use the program, he is your master." Richard Stallman > >
