On (17/07/10 01:03), Koen Kooi wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> 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


I built minimal-image/uclibc from scratch on a ubuntu maverick (gcc 4.4.4)
host
once with -g and secong time using -ggdb3 instead
in both FULL_OPTIMIZATION and BUILD_OPTIMIZATION



Total tmp size with -g = 15G
Total tmp size with -ggdb3 = 70G

Total sysroot size with -g = 1.1G (868M is native sysroot )
Total sysroot size with -ggdb3 = 13.4G ( 12.7G is native sysroot )

Total size of cross directory with -g = 158M
Total size of cross directory with -gdb3 = 567M

Because I did not strip the binaries

Total size of deploy with -g = 135M
Total size of deploy with -ggdb3 = 521M

Attached is a list of files in sysroot which are larger than 2M in size
sorted in increasing size order for both -g and -ggdb

generated by using

find . -type f -size +2000k -exec ls -lh {} \; 2> /dev/null | awk '{ print
$NF ": " $5 }' | sort -nk 2,2

btw git-native build tree is 24G which is a problem
but if we ignore that tmp still is ~45G for a minimal-image

Does that clear the FUD ? :)

anyway my point was that users know what to expect. If we put it in
minimum requirement to build a distro its fine atleast it sets expectation
on how much disk space would be needed.

btw. now may I request you for some emperical evidence on
"gcc 4.4 is slow on ARMv7" or is it another FUD or hearsay ? :)

Thanks

-Khem

ps: I also noticed that the build with -ggdb3 took noticeable longer time. I wish I
had timed it but may be next time.