From: Dirk Behme <dirk.behme@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] ARM ld: section .bss overlaps section .rel.dyn
Date: Sun, 30 Oct 2011 12:33:13 +0100 [thread overview]
Message-ID: <4EAD35F9.8090703@googlemail.com> (raw)
In-Reply-To: <4EAD2D9B.9010008@aribaud.net>
On 30.10.2011 11:57, Albert ARIBAUD wrote:
> Le 30/10/2011 11:24, Albert ARIBAUD a ?crit :
>> Hi Dirk,
>>
>> Le 30/10/2011 10:47, Dirk Behme a ?crit :
>>>
>>> Doing a ./MAKEALL ARMV7 (gcc [1]) with the recent git head I get a
>>> lot of
>>>
>>> arm-none-linux-gnueabi-ld: section .bss [...] overlaps section
>>> .rel.dyn [...]
>>> arm-none-linux-gnueabi-ld: section .dynsym [...] overlaps section .bss
>>> [...]
>>> ...
>>> make: *** [u-boot] Error 1
>>>
>>> for various boards [2]. I wasn't able to track this down to specific
>>> commit, yet.
>>>
>>> Anybody with an idea?
>>
>> Weird... Linker file says explicitly that .bss does overlay above
>> .rel.dyn, so the first message should not ever happen. As for the
>> second, it could happen depending on the bss, .re.dyn and .dynsym
>> sizes,
>> maybe.
>>
>> I'll have a look today.
>
> I've tried ./MAKEALL efikamx with ELDK32, and did not see any warning
> nn either u-boot/master (ce5207e191c59b3135303fd03b98dd2ac3701ba2) or
> u-boot-arm/master (8305f7e98b5f7b9b6070777e68f3fe1871b9cd92).
>
> Can you check your setup for locally modified/added files and let me
> know which exact commit ID you're building in (git rev-parse HEAD) and
> which ARM repo it is from?
I'm using u-boot/master (ce5207e191c59b3135303fd03b98dd2ac3701ba2).
Anyway, git bisect seems to point to
http://git.denx.de/?p=u-boot.git;a=commit;h=3cce8a5496452285e1828984ad3945417205cfc3
Not sure why, though. Using omap3_pandora as an example:
> git rev-parse HEAD
3cce8a5496452285e1828984ad3945417205cfc3
> make distclean
> ./MAKEALL omap3_pandora
Configuring for omap3_pandora board...
arm-none-linux-gnueabi-ld: section .bss [8005d1e8 -> 8008fddb]
overlaps section .rel.dyn [8005d1e8 -> 80063e97]
arm-none-linux-gnueabi-ld: section .dynsym [80063e98 -> 80063f57]
overlaps section .bss [8005d1e8 -> 8008fddb]
arm-none-linux-gnueabi-ld: u-boot: section .bss vma 0x8005d1e8
overlaps previous sections
make: *** [u-boot] Error 1
size: './u-boot': No such file
--------------------- SUMMARY ----------------------------
Boards compiled: 1
Boards with warnings or errors: 1 ( omap3_pandora )
----------------------------------------------------------
...
> git rev-parse HEAD
70d52f9a4e661f00814ed2160bdedd3cc49aa44c
> make distclean
> ./MAKEALL omap3_pandora
Configuring for omap3_pandora board...
text data bss dec hex filename
368690 7972 207860 584522 8eb4a ./u-boot
--------------------- SUMMARY ----------------------------
Boards compiled: 1
----------------------------------------------------------
Hmm?
Best regards
Dirk
next prev parent reply other threads:[~2011-10-30 11:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-30 9:47 [U-Boot] ARM ld: section .bss overlaps section .rel.dyn Dirk Behme
2011-10-30 10:24 ` Albert ARIBAUD
2011-10-30 10:57 ` Albert ARIBAUD
2011-10-30 11:33 ` Dirk Behme [this message]
2011-10-30 12:46 ` Albert ARIBAUD
2011-10-30 16:05 ` Albert ARIBAUD
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=4EAD35F9.8090703@googlemail.com \
--to=dirk.behme@googlemail.com \
--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