From: Tolunay Orkun <listmember@orkun.us>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Section overlap
Date: Tue, 23 May 2006 12:25:10 -0500 [thread overview]
Message-ID: <44734576.6090606@orkun.us> (raw)
In-Reply-To: <BAY105-F16366015E401A8668F788D8EAE0@phx.gbl>
k bisla wrote:
> Hi,
> I'm using U-boot-1.0.0 on an ebony board (ppc),
> and running into section overlap error at the time of linking.
> here's what the output looks like ...
>
> section .u_boot_cmd [ffffef50 -> fffff567] overlaps section .bootpg
> [fffff000 -> fffff29f]
>
> 1) how do i get around this ?
Section overlap is due to a toolchain issue. One of the patches after
1.1.4 fixed this issue by updating all .lds files as a workaround. If
you use the top of the tree with updated .lds, linker will no longer
overlap sections incorrectly.
Best regards,
Tolunay
prev parent reply other threads:[~2006-05-23 17:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-09 20:49 [U-Boot-Users] RAM mapping repeats Antonio Di Bacco
2006-05-09 22:13 ` Wolfgang Denk
2006-05-10 1:05 ` [U-Boot-Users] Section overlap k bisla
2006-05-10 7:20 ` Wolfgang Denk
2006-05-10 22:44 ` k bisla
2006-05-10 23:00 ` Wolfgang Denk
2006-05-23 17:25 ` Tolunay Orkun [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=44734576.6090606@orkun.us \
--to=listmember@orkun.us \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox