From: Albert ARIBAUD <albert.aribaud@free.fr>
To: u-boot@lists.denx.de
Subject: [U-Boot] Build failures with older toolchain
Date: Mon, 22 Nov 2010 15:31:39 +0100 [thread overview]
Message-ID: <4CEA7ECB.1050803@free.fr> (raw)
In-Reply-To: <B85A65D85D7EB246BE421B3FB0FBB59302477EB3A4@dbde02.ent.ti.com>
Le 22/11/2010 14:50, Premi, Sanjeev a ?crit :
> Tried the same stuff for overo and no issues!
>
> Since there linker scripts are same between omap3_evm, omap3_beagle
> and omap3_overo, only difference could have been board specific code.
>
> I was hoping to find some code that might be offending the linker;
> unable to find by inspection, I reduced the default configuration
> for the evm to as low as I could - still see:
>
> arm-none-linux-gnueabi-ld: section .bss [800fe358 -> 800fee1b] overlaps section .rel.dyn [800fe358 -> 8010076f]
> arm-none-linux-gnueabi-ld: u-boot: section .bss vma 0x800fe358 overlaps previous sections
>
> I am still not sure why the start of .bss and .rel.dyn for omap3_evm start at same address
That is because they are voluntarily overlapped. This looks like the
patch I recently did, which in essence does overlap BSS (which is not
used before relocation) and relocation tables (which are not used after
relocation) so that the FLASH and RAM footprint remain minimal.
This should not result in a linker message unless the .lds does not
follow the same structure (order and attributes of output sections) as,
for instance, the arm926ejs u-boot.lds.
> but
>
> Looking for more pointers!
> Specifically, a "big" generic change that somehow didn't touch the omap3evm; but did touch others.
> ....will start looking at the git-log immediately after this mail.
>
> ~sanjeev
Look up the u-boot.lds files. Are they shared?
Amicalement,
--
Albert.
next prev parent reply other threads:[~2010-11-22 14:31 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-19 18:50 [U-Boot] Build failures with older toolchain Premi, Sanjeev
2010-11-19 19:43 ` Premi, Sanjeev
2010-11-19 20:13 ` Wolfgang Denk
2010-11-22 9:14 ` Premi, Sanjeev
2010-11-22 13:50 ` Premi, Sanjeev
2010-11-22 14:31 ` Albert ARIBAUD [this message]
2010-11-22 14:42 ` Premi, Sanjeev
2010-11-22 15:02 ` Premi, Sanjeev
2010-11-22 15:23 ` Albert ARIBAUD
2010-11-22 15:27 ` Premi, Sanjeev
2010-11-22 15:35 ` Albert ARIBAUD
2010-11-29 9:47 ` Premi, Sanjeev
2010-11-29 10:32 ` Albert ARIBAUD
2010-11-29 10:37 ` Premi, Sanjeev
2010-11-29 11:29 ` Wolfgang Denk
2010-11-29 11:48 ` Premi, Sanjeev
2010-11-29 12:05 ` Wolfgang Denk
2010-11-29 15:08 ` Premi, Sanjeev
2010-11-29 15:33 ` Albert ARIBAUD
2010-11-29 15:39 ` Premi, Sanjeev
2010-11-30 14:25 ` Premi, Sanjeev
2010-11-30 16:44 ` Dirk Behme
2010-11-30 18:23 ` Premi, Sanjeev
2010-12-01 14:56 ` Premi, Sanjeev
2010-12-01 15:02 ` Albert ARIBAUD
2010-12-01 15:18 ` Premi, Sanjeev
2010-11-29 10:35 ` Wolfgang Denk
2010-11-29 10:44 ` Premi, Sanjeev
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=4CEA7ECB.1050803@free.fr \
--to=albert.aribaud@free.fr \
--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