On Fri, Mar 7, 2008 at 8:09 AM, Mark Knecht <[EMAIL PROTECTED]> wrote: > Hi all, > What would be a sufficient set of actions for me to take to get > backtrace info from Wine that would be useful to Wine devlopers? Their > Bugzilla folks are are saying, correctly I think, that everything > necessary is stripped out and that the info I'm providing doesn't > help. I don't see anything specific in the Wine flags. > > Is this some sort of major effort required where I have to go back > and recompile many things on my system or is there a way to compile > just Wine to give them what they need? > > I found this page to read: > > http://www.gentoo.org/proj/en/qa/backtraces.xml > > I do not understand the nostrip/splitdebug topic. I do not find > either word in man emerge or man portage. Is this a gcc thing? > > My current gcc flags look like this: > > CFLAGS="-march=k8 -O2 -pipe" > CHOST="x86_64-pc-linux-gnu" > CXXFLAGS="${CFLAGS}" > MAKEOPTS="-j2" > > Any comments about whether those are good or not for a > non-developer, desktop user type like me would be appreciated. I don't > mind changing cflags to get these folks what they want. > > Thanks, > Mark >
OK, so this seems to be part of using the FEATURES=" ... " line in make.conf. I do not have a FEATURES line at all so I'm hesitant to just start throwing things in. <<glug...help...>> I've heard of things like sandbox and ccache but I've never touched them. Would they be good things to use all the time or are they more for developers? Anyway, if someone can help clear this up I would appreciate it. Thanks, Mark -- [email protected] mailing list
