public inbox for gentoo-amd64@lists.gentoo.org
 help / color / mirror / Atom feed
From: Chris Brennan <xaero@xaerolimit.net>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] Re: Enabling debug info in Wine?
Date: Fri, 07 Mar 2008 11:59:21 -0500	[thread overview]
Message-ID: <47D17469.70703@xaerolimit.net> (raw)
In-Reply-To: <5bdc1c8b0803070847y3094bde9j7aa9a6a64500a033@mail.gmail.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

I'm not a developer, but I use the following

Leviathan ~ # grep FEAT /etc/make.conf
FEATURES="parallel-fetch distclean ccache confcache"
Leviathan ~ #

For the average user, these are a safe bet, the last two are apps you'll
need to emerge and set up as well. pretty simple and straight forward.

Mark Knecht wrote:
| On Fri, Mar 7, 2008 at 8:09 AM, Mark Knecht <markknecht@gmail.com> 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
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFH0XRp8hUIAnGfls4RAi+aAKCS89m1eZ6DjvJe7SkUNgtMvYLWpgCdEsZp
58LKFc6R3KJkKJ3wr0fnayc=
=h8oX
-----END PGP SIGNATURE-----
-- 
gentoo-amd64@lists.gentoo.org mailing list



  reply	other threads:[~2008-03-07 16:59 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-07 16:09 [gentoo-amd64] Enabling debug info in Wine? Mark Knecht
2008-03-07 16:47 ` [gentoo-amd64] " Mark Knecht
2008-03-07 16:59   ` Chris Brennan [this message]
2008-03-07 17:21     ` Mark Knecht
2008-03-07 18:54       ` Duncan
2008-03-07 19:03         ` Mark Knecht
2008-03-07 19:05           ` Mark Knecht
2008-03-08  1:15             ` Duncan
2008-03-08  5:06               ` Duncan
2008-03-08 18:40                 ` Mark Knecht
2008-03-09  0:15                   ` Duncan

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=47D17469.70703@xaerolimit.net \
    --to=xaero@xaerolimit.net \
    --cc=gentoo-amd64@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox