Adding a debug target to the make's which do this is fine, but shouldn't
be the default.

James

>
>My build of ramdisk-tiny.fs is currently exploding (1515520 bytes),
>this could easily be due to a local change pulling in an unexpected
>chunk of libc.
>
>However the build does make it rather difficult to work out what
>has happened.  In particular leaving an unstripped ramdiskbin
>and making ld output a mapfile would make finding what has grown
>or been unexpectedly included (and why) a lot easier.
>
>This would be particulary true if something in the source tree
>indicated which bits of libc are expected to be included.
>
>I've also just noticed that 'objdump -h ramdiskbin' shows:
> 12 .note         00002ef4  00000000  00000000  00115420  2**0
>                  CONTENTS, READONLY
> 13 .ident        00006d9f  00000000  00000000  00118314  2**0
>                  CONTENTS, READONLY
>I think these could be safely deleted (saving 40k).
>
>	David
>
>-- 
>David Laight: david@l8s.co.uk
>
>
>