public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Albert ARIBAUD <albert.u.boot@aribaud.net>
To: u-boot@lists.denx.de
Subject: [U-Boot] ARM ld: .bss overlaps section .rel.dyn
Date: Fri, 03 Feb 2012 19:24:19 +0100	[thread overview]
Message-ID: <4F2C2653.6030302@aribaud.net> (raw)
In-Reply-To: <CAEOkp44wuV=4aMn3YV0UKYoyFjsX+gR0A4aG+eZgTiDLdVxmPg@mail.gmail.com>

Hi Amit,

Le 03/02/2012 07:57, Amit Virdi a ?crit :
> Adding Albert now...

... but the wrong (old) address though :)

> On 2/3/12, Amit Virdi<amitvi128@gmail.com>  wrote:
>> Albert,
>>
>> Any suggestions?
>>
>> Thanks
>> Amit Virdi
>>
>> On 2/1/12, Amit Virdi<amitvi128@gmail.com>  wrote:
>>> Hi All,
>>>
>>> I'm in the process of updating platform support for spear series of
>>> SoC on the latest u-boot.
>>> I picked u-boot v2011.12. I tried compiling for different spear boards
>>> (spear 300, 310, 300 and spear600). In every compilation, I'm getting
>>> following errors:
>>>
>>> -----------------------
>>> arm-linux-ld: section .bss [007263cc ->  00728c5b] overlaps section
>>> .rel.dyn [007263cc ->  0072a623]
>>> arm-linux-ld: u-boot: section .bss lma 0x7263cc overlaps previous
>>> sections
>>> make: *** [u-boot] Error 1
>>> -----------------------
>>>
>>> This is one case.

In fact, .bss overlapping .rel.dyn is normal -- the linker file even 
explicitly states this with ".bss __rel_dyn_start (OVERLAY)".

Which compiler do you use and which board exactly are you building?

Amicalement,
-- 
Albert.

  reply	other threads:[~2012-02-03 18:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-01 12:26 [U-Boot] ARM ld: .bss overlaps section .rel.dyn Amit Virdi
2012-02-03  6:54 ` Amit Virdi
2012-02-03  6:57   ` Amit Virdi
2012-02-03 18:24     ` Albert ARIBAUD [this message]
2012-02-04  3:05       ` viresh kumar
2012-02-05 11:29         ` Amit Virdi
2012-02-05 13:20           ` Albert ARIBAUD
2012-02-05 16:05             ` Amit Virdi

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=4F2C2653.6030302@aribaud.net \
    --to=albert.u.boot@aribaud.net \
    --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