Duncan <[EMAIL PROTECTED]> posted [EMAIL PROTECTED], excerpted below, on Sat, 08 Mar 2008 01:15:10 +0000:
> There's a big caveat here, however. AFAIK wine is 32-bit only. (??) If > so, that means it and/or some of its libraries are likely to be binary- > only 32-bit compatibility packages, if you are using a standard multilib > profile. All these compiling options obviously aren't going to do a lot > of good on binary-only stuff. You can of course go the 32-bit chroot > route and thereby compile everything from source, but that's going to be > an awful lot of work just to debug something if you aren't extremely > motivated. OTOH, it DOES give you the opportunity to build the entire > 32- bit side with -g if you want, without interfering with your 64-bit > main system. This would be a blocker for many, but I'm not /sure/ wine > is 32- bit only. I just checked, wine does appear to be 32-bit only, as it's masked on my no-multilib profile. I don't know if it's binary-only or if it's actually built as 32-bit on multilib profiles, but it's certainly 32-bit only, and therefore masked by the no-multilib profile. FWIW. -- 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 -- [email protected] mailing list
