Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@lists.openembedded.org
Subject: Re: angstrom-2008.1, uclibc: git-native: sysroot-destdir 6, 4 GB big, since some executables are 100 MB each
Date: Sat, 17 Jul 2010 14:17:54 +0200	[thread overview]
Message-ID: <i1s71i$d1j$2@dough.gmane.org> (raw)
In-Reply-To: <AANLkTin6E1D5KENkaXn4lf4dF8hog7f-bnDmDXSWQn7L@mail.gmail.com>

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

On 17-07-10 04:06, Khem Raj wrote:
> On Fri, Jul 16, 2010 at 4:03 PM, Koen Kooi <k.kooi@student.utwente.nl> wrote:
> On 16-07-10 17:23, Khem Raj wrote:
>>>> On Fri, Jul 16, 2010 at 2:03 AM, Paul Menzel
>>>> <paulepanter@users.sourceforge.net> wrote:
>>>>> Dear OE folks,
>>>>>
>>>>>
>>>>> Am Donnerstag, den 15.07.2010, 19:55 +0200 schrieb Paul Menzel:
>>>>>
>>>>>> I ran out of space and noticed
>>>>>>
>>>>>>     /angstrom-dev/work/i686-linux/git-native-1.7.0.2-r4
>>>>>>
>>>>>> is 8,1G big.
>>>>>>
>>>>>> Some of the executable files in
>>>>>>
>>>>>>     /angstrom-dev/work/i686-linux/git-native-1.7.0.2-r4/sysroot-destdir/angstrom-dev/sysroots/i686-linux/usr/libexec/git-core/
>>>>>>
>>>>>> are 101 MB big.
>>>>
>>>> its most probably the -g3/-ggdb3 bloat.
> 
> No, it's git not creating (hard)links but copies of the same app. Run an
> md5sum on the binaries, they will all match. I suggest you stop
> spreading FUD about -ggdb3, it is not being appriciated.
> 
>> Hi Koen
> 
>> Its not FUD and I only speak of what I see with my eyes. I have data
>> to prove it. Compile uclibc with ggdb3 and it ends up with 202M of
>> shared library and without its only ~600K. (with gcc 4.4 and 4.5) I
>> have similar experience with 4.3 but I dont
>> have a build handy to see how big the binaries got.

And I was saying that the 8GB of git, if a bug in git, not with gdb3. I
know gdb3 makes unstripped executables bigger and don't deny that.

I do take offence with you saying that the root cause is -ggdb3, when
it's actually git being buggy. And as you have seen, instead of fixing
git, people are removing -ggdb3 :(

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFMQZ9yMkyGM64RGpERAvrYAJ0XYJZ40fAfTpWs5eCdEuWZlidzQgCgnDiw
sWRwYL9QbYfPDgdyp47pwzk=
=hKZ3
-----END PGP SIGNATURE-----




  reply	other threads:[~2010-07-17 12:20 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-15 17:55 angstrom-2008.1, uclibc: git-native: sysroot-destdir 6, 4 GB big, since some executables are 100 MB each Paul Menzel
2010-07-16  9:03 ` Paul Menzel
2010-07-16 15:23   ` Khem Raj
2010-07-16 23:03     ` Koen Kooi
2010-07-17  2:06       ` Khem Raj
2010-07-17 12:17         ` Koen Kooi [this message]
2010-07-17 17:17           ` Phil Blundell
2010-07-17  7:32       ` Khem Raj
2010-07-17  8:35       ` Paul Menzel
2010-07-17 12:15         ` Koen Kooi
2010-07-18 14:48           ` Paul Menzel
2010-07-20 21:14             ` Paul Menzel
2010-07-20 22:44               ` Khem Raj
2010-07-21 10:20                 ` Paul Menzel

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='i1s71i$d1j$2@dough.gmane.org' \
    --to=k.kooi@student.utwente.nl \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox