Re: [gentoo-amd64] Re: Enabling debug info in Wine?

[Mark Knecht]

On Fri, Mar 7, 2008 at 9:06 PM, Duncan <1i5t5.duncan@×××.net> wrote:
> Duncan <1i5t5.duncan@×××.net> posted pan.2008.03.08.01.15.10@×××.net,
>  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,
   Thanks for the responses. Even though they are a bit over my head
They were helpful.

   One comment about Wine. There is both Open Source software as well
as free binary distribution software for Windows, especially in the
audio area. Small signal processing units like reverb and
synthesizers, etc. Not everythign compiled for Windows is created by
the Dark Lords of the North West. Anyway, just because we run Wine
doesn't mean we have to go against your free software mantra. That's a
good portion of how I've used Wine in the past. Other than that I try,
once in awhile, to run a game which I've already purchased. Not the
best, I know, but better than continuing to purchase, or at least I
think so. To each his/her own.

   I ended up doing two things:

1) I built Wine using the nostrip feature. This did not produce
anything extra in the output. Maybe I'm somehow not taking the most
advantage, I don't know.

2) I built Wine using the WineHQ.org tarball but didn't install it. I
then ran it from its build directory. This worked fine and produced
backtrace data that the folks on the Wine list say looks pretty good
and should be helpful.

   Again, and as always, I really appreciate all your inputs. They are
often enlightening!

Cheers,
Mark
-- 
gentoo-amd64@l.g.o mailing list