[U-Boot-Users] objcopy stalled, large binary size for sc520 based board

[U-Boot-Users] objcopy stalled, large binary size for sc520 based board

[Aras Vaichas]

I have the same problem as Sreedhar Payavala had back in June.

I am porting sc520_cdp and sc520_spunk to my sc520 based board. I had several 
issues relating to differences between versions of gcc and ld. I fixed them and 
then got stuck for a while with this ld error:

ld: section .data [00000000387d4de4 -> 00000000387d5a76] overlaps section 
.rodata.str1.1 [00000000387d4de4 -> 00000000387d9aca]
ld: section .realmode [00000000387d5a77 -> 00000000387d5bdc] overlaps section 
.rodata.str1.1 [00000000387d4de4 -> 00000000387d9aca]
ld: section .bios [00000000387d5bdd -> 00000000387d611a] overlaps section 
.rodata.str1.1 [00000000387d4de4 -> 00000000387d9aca]
make: *** [u-boot] Error 1

I added the command line argument --no-check-sections to LDFLAGS in config.mk 
and this problem went away (perhaps).

Now I have a problem with objcopy, objcopy never ends and uses massive amounts 
of memory. If I ctrl-c, and check the output files I see:

rwxrwxr-x    1 root  root  594727 Sep 29 13:12 u-boot

I am using ld version "GNU ld version 2.14.90.0.8 20040114" and gcc version 
"gcc (GCC) 3.3.4 20040623"

If anyone can help, it would be appreciated.

regards,

Aras Vaichas

[U-Boot-Users] objcopy stalled, large binary size for sc520 based board

[Wolfgang Denk]

In message <415A28E9.7050102@magellan-technology.com> you wrote:
> 
> then got stuck for a while with this ld error:
> 
> ld: section .data [00000000387d4de4 -> 00000000387d5a76] overlaps section 
> .rodata.str1.1 [00000000387d4de4 -> 00000000387d9aca]
> ld: section .realmode [00000000387d5a77 -> 00000000387d5bdc] overlaps section 
> .rodata.str1.1 [00000000387d4de4 -> 00000000387d9aca]
> ld: section .bios [00000000387d5bdd -> 00000000387d611a] overlaps section 
> .rodata.str1.1 [00000000387d4de4 -> 00000000387d9aca]
> make: *** [u-boot] Error 1
> 
> I added the command line argument --no-check-sections to LDFLAGS in config.mk 
> and this problem went away (perhaps).

This is definitely a BAD idea. Instead  of  shutting  off  the  error
messages you should fix the obvious problems in the linker script.

> If anyone can help, it would be appreciated.

Fix the linker script.

Best regards,

Wolfgang Denk

-- 
Software Engineering:  Embedded and Realtime Systems,  Embedded Linux
Phone: (+49)-8142-4596-87  Fax: (+49)-8142-4596-88  Email: wd at denx.de
The ideal situation is to have massive computing power right at home.
Something that dims the streetlights and shrinks the picture  on  the
neighbours' TVs when you boot it up.