From: Tom Rini <tom_rini@mentor.com>
To: <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 09:07:09 -0700 [thread overview]
Message-ID: <4D6D19AD.5010505@mentor.com> (raw)
In-Reply-To: <1298970609-4974-1-git-send-email-Martin.Jansa@gmail.com>
On 03/01/2011 02:10 AM, Martin Jansa wrote:
> Signed-off-by: Martin Jansa<Martin.Jansa@gmail.com>
> ---
> conf/distro/include/sane-toolchain-eglibc.inc | 12 ++++++------
> conf/distro/include/sane-toolchain-glibc.inc | 10 +++++-----
> conf/distro/include/sane-toolchain-uclibc.inc | 6 +++---
> .../include/sane-toolchain-uclinux-uclibc.inc | 2 +-
> 4 files changed, 15 insertions(+), 15 deletions(-)
While we're in here, we should look at what the angstrom ones do
correctly which is that BUILD_OPTIMIZATION is only for -native recipes.
And personally I'd like to see the -g flag (for both target and the
rest) be a variable that can be tweaked as needed (for more or less
debug in the area).
--
Tom Rini
Mentor Graphics Corporation
next prev parent reply other threads:[~2011-03-01 16:08 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 [this message]
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
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=4D6D19AD.5010505@mentor.com \
--to=tom_rini@mentor.com \
--cc=openembedded-devel@lists.openembedded.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 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.