-----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.k...@student.utwente.nl> wrote: > On 16-07-10 17:23, Khem Raj wrote: >>>> On Fri, Jul 16, 2010 at 2:03 AM, Paul Menzel >>>> <paulepan...@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----- _______________________________________________ Openembedded-devel mailing list Openembedded-devel@lists.openembedded.org http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
