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:15:11 +0200	[thread overview]
Message-ID: <i1s6sg$d1j$1@dough.gmane.org> (raw)
In-Reply-To: <1279355702.14848.3.camel@mattotaupa>

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

On 17-07-10 10:35, Paul Menzel wrote:
> Am Samstag, den 17.07.2010, 01:03 +0200 schrieb Koen Kooi:
>> 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:
> 
>>>> 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.
> 
> I do not know anything about the technical background. I can only report
> that removing `-ggdb3` fixed it for me.

Are you saying that removing -ggdb3 made git create proper (hard)links?

regards.

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

iD8DBQFMQZ7PMkyGM64RGpERAilSAJ0Xh7q/84Ls1fu9SiqPiX4FcOS+9ACfRG/L
0sRjnr5z7xFxOVC7oSc1aG8=
=MEay
-----END PGP SIGNATURE-----




  reply	other threads:[~2010-07-17 12:15 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
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 [this message]
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='i1s6sg$d1j$1@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