From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Question: is 'gcc' supposed to replace the libstdc++.la installed by 'gcc-cross'?
Date: Mon, 17 May 2010 11:52:35 -0700 [thread overview]
Message-ID: <20100517185235.GA7868@gmail.com> (raw)
In-Reply-To: <1274119962.25944.147.camel@trini-m4400>
On (17/05/10 11:12), Tom Rini wrote:
> On Mon, 2010-05-17 at 10:45 -0700, Khem Raj wrote:
> > On Mon, May 17, 2010 at 10:02 AM, Koen Kooi <k.kooi@student.utwente.nl> wrote:
> > > -----BEGIN PGP SIGNED MESSAGE-----
> > > Hash: SHA1
> > >
> > > On 17-05-10 18:49, Khem Raj wrote:
> > >> On Mon, May 17, 2010 at 2:38 AM, Koen Kooi <k.kooi@student.utwente.nl> wrote:
> > >
> > >> I could not build a console-image as I ran out of disk space. Have you
> > >> considered removing
> > >> -g3 from default angstrom builds.
> >
> > what is -g3 offering over -g at -O2 and how good the additional debug info is ?
>
> -g3 offers lots of stuff, spelled out in some doc or another is macro
> expansion, for example. I don't know if it offers enough stuff that you
> say don't need the sources themselves around still too tho. Koen?
If -g3 is intended, some options to reduce debug info size should be
considered like
-feliminate-dwarf2-dups -femit-struct-debug-baseonly
-femit-struct-debug-reduced
etc.
-Khem
next prev parent reply other threads:[~2010-05-17 18:56 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-17 5:44 Question: is 'gcc' supposed to replace the libstdc++.la installed by 'gcc-cross'? Koen Kooi
2010-05-17 5:55 ` Khem Raj
2010-05-17 9:38 ` Koen Kooi
2010-05-17 13:52 ` Koen Kooi
2010-05-17 16:49 ` Khem Raj
2010-05-17 17:02 ` Koen Kooi
2010-05-17 17:45 ` Khem Raj
2010-05-17 18:12 ` Tom Rini
2010-05-17 18:52 ` Khem Raj [this message]
2010-05-20 13:39 ` Phil Blundell
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=20100517185235.GA7868@gmail.com \
--to=raj.khem@gmail.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.