Enormous linux kernel after objcopy

[Daniel Jacobowitz]

On Sun, Jun 01, 2008 at 10:07:08AM -0700, David Goodlad wrote:
> Using any version of binutils compiled locally (2.16, 2.17, 2.18*) using
> crosstool-ng, and gcc 4.2.2, I end up with a kernel image that is far
> too large. The file arch/arm/boot/Image ends up being 3.1-3.2 GB!
> However, this is a bit of a trick, since there is only about 200 bytes
> of 'data' at the beginning of that file, then 0s until 0xc0008000 (the
> kernel's base address on my architecture - RAM starts at 0xc0000000).
> This seems to be a result of the objcopy from vmlinux, which is only a
> couple of megs in size.

This means something created by your local tools is missing from the
linker script.  Place whatever it is at a sensible address.  It's
likely to be fixed in the latest kernel sources, this happens
frequently.

-- 
Daniel Jacobowitz
CodeSourcery