From: Tom Rini <tom_rini@mentor.com>
To: Otavio Salvador <otavio@ossystems.com.br>
Cc: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH] sane-toolchain-*: add -g to FULL_OPTIMIZATION to make -dbg packages more usefull
Date: Tue, 1 Mar 2011 10:54:01 -0700 [thread overview]
Message-ID: <4D6D32B9.9080708@mentor.com> (raw)
In-Reply-To: <AANLkTik7Cm2P6KL5aRDVf4sOUGsnAbpACyS+PucRpHiX@mail.gmail.com>
On 03/01/2011 10:50 AM, Otavio Salvador wrote:
> On Tue, Mar 1, 2011 at 17:39, Tom Rini<tom_rini@mentor.com> wrote:
>> On 03/01/2011 10:03 AM, Otavio Salvador wrote:
>>> Having -g shouldn't hurt since the debugging symbols end up on the
>>> -dbg packages. Why having it "disabled" by default?
>>
>> In the case of host packages, I disable debug symbols (don't want, takes up
>> space when shipping). In the case of target stuff, we may want more debug
>> info to be available. Or one may want to have less because again, it takes
>> up space when shipping.
>
> I see but this could be overriden by distro, couldn't it?
That's why I'm asking for the -g part to be put into a variable so that
it can be overriden easily, in all cases, without needing to know the
special cases (ie glibc).
--
Tom Rini
Mentor Graphics Corporation
next prev parent reply other threads:[~2011-03-01 17:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-01 9:10 [PATCH] sane-toolchain-*: add -g to FULL_OPTIMIZATION to make -dbg packages more usefull Martin Jansa
2011-03-01 11:15 ` Otavio Salvador
2011-03-01 16:07 ` Tom Rini
2011-03-01 17:03 ` Otavio Salvador
2011-03-01 17:39 ` Tom Rini
2011-03-01 17:50 ` Otavio Salvador
2011-03-01 17:54 ` Tom Rini [this message]
2011-03-01 18:10 ` Phil Blundell
2011-03-01 18:29 ` Tom Rini
2011-03-01 19:14 ` Khem Raj
2011-03-01 19:33 ` Tom Rini
2011-03-01 19:37 ` Khem Raj
2011-03-01 20:17 ` Phil Blundell
2011-03-02 19:55 ` [PATCHv2] sane-toolchain-*: define DEBUG_FLAGS and add it " Martin Jansa
2011-03-02 22:29 ` Tom Rini
2011-03-02 23:22 ` Khem Raj
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=4D6D32B9.9080708@mentor.com \
--to=tom_rini@mentor.com \
--cc=openembedded-devel@lists.openembedded.org \
--cc=otavio@ossystems.com.br \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.