From: Khem Raj <raj.khem@gmail.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Broken git-native in dev
Date: Tue, 14 Jul 2009 10:55:39 -0700 [thread overview]
Message-ID: <20090714175539.GA5298@gmail.com> (raw)
In-Reply-To: <20090714170415.GA24919@rhein.zuhause.netz>
On (14/07/09 19:04), Henning Heinold wrote:
> Hi,
>
> today I stumbled over some mess up with git-native. I wondered why disk was full. I examined
> that my staging dir was about 3 gig's. I examined further and found ot that most of the space comes
> from i686-linux/libexec/git-core. Problem is we install git-bins without calling strip
> so each 130 executables is about 22 Megs. If no one has a quick solution I will try dig further.
>
I think this is due to -ggdb3 flag being passed to native recipes.
Unless we want to debug native recipes we should avoid excessive debug
info for those packages to save on disk space.
> Maybee we should put a test in the native class which checks if the executables are striped.
yeah that would work too but then why generate debug info at all if we
do not want to keep it.
Thx
-Khem
next prev parent reply other threads:[~2009-07-14 18:09 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-14 17:04 Broken git-native in dev Henning Heinold
2009-07-14 17:46 ` Henning Heinold
2009-07-14 17:55 ` Khem Raj [this message]
2009-07-14 19:10 ` Florian Boor
2009-07-14 20:04 ` Richard Purdie
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=20090714175539.GA5298@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.