All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dirk Behme <dirk.behme@googlemail.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] OMAP3: EVM: Linker errors across tool chain versions
Date: Sun, 12 Dec 2010 11:32:29 +0100	[thread overview]
Message-ID: <4D04A4BD.6070705@googlemail.com> (raw)
In-Reply-To: <4D049F2C.6010005@free.fr>

On 12.12.2010 11:08, Albert ARIBAUD wrote:
> Hi Dirk,
>
> Le 12/12/2010 09:25, Dirk Behme a ?crit :
>>
>> What's the status of the linker errors across tool chain versions seen
>> by building the 'omap3_evm' board?
>>
>> This was already discussed in the threads [1] and [2], but it seems to
>> me that there was no acceptable fix, yet?
>>
>> E.g. with CodeSourcery's tool chain 2009q1-203 I get
>>
>> arm-none-linux-gnueabi-ld: section .bss [8003f5e0 -> 8007e33f] overlaps
>> section .rel.dyn [8003f5e0 -> 80044e6f]
>> arm-none-linux-gnueabi-ld: section .dynsym [80044e70 -> 80044f0f]
>> overlaps section .bss [8003f5e0 -> 8007e33f]
>> arm-none-linux-gnueabi-ld: u-boot: section .bss vma 0x8003f5e0 overlaps
>> previous sections
>>
>> What we learned from [2] is that using [3] fixes the build (at least
>> for
>> me with the tool chain mentioned above). I.e. converting
>> omap3_evm_version from u8 to int
>>
>> -static u8 omap3_evm_version;
>> +static int omap3_evm_version;
>>
>> makes the issue disappear.
>>
>> But if I understood the discussion correctly, this is no acceptable fix
>> and can be used only as debug help (?).
>>
>> Any further hints?
>
> Three comments at least:
>
> 1. I personally would agree with the change to int, but since Wolfgang
> considers it a workaround to the linker issue, I won't accept it either.
>
> 2. IIRC, the linker emits a warning, not an error. We can live some
> time with a warning if it is documented and it is being worked on.

With 2009q1-203 it's an error and 'omap3_evm'  isn't built:

arm-none-linux-gnueabi-ld: section .bss [8003f5e0 -> 8007e33f] 
overlaps section .rel.dyn [8003f5e0 -> 80044e6f] 
 

arm-none-linux-gnueabi-ld: section .dynsym [80044e70 -> 80044f0f] 
overlaps section .bss [8003f5e0 -> 8007e33f] 
 

arm-none-linux-gnueabi-ld: u-boot: section .bss vma 0x8003f5e0 
overlaps previous sections
make: *** [u-boot] Error 1 

size: './u-boot': No such file

Thanks

Dirk

> 3. I did offer to try and find a minimal test case (one .c file, one
> .lds file, one simple command line) to cause the warning and submit it
> to the binutils list, but haven't had time so far.
>
>> Thanks
>>
>> Dirk
>
> Amicalement,

  reply	other threads:[~2010-12-12 10:32 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-12  8:25 [U-Boot] OMAP3: EVM: Linker errors across tool chain versions Dirk Behme
2010-12-12 10:08 ` Albert ARIBAUD
2010-12-12 10:32   ` Dirk Behme [this message]
2010-12-12 11:40     ` Albert ARIBAUD
2010-12-14 15:42       ` Dirk Behme
2010-12-14 16:01         ` Albert ARIBAUD
2010-12-14 16:14           ` Wolfgang Denk
2010-12-16 13:47           ` Alexander Holler
2010-12-16 14:31             ` Alexander Holler
2010-12-16 15:20             ` Dirk Behme
2010-12-16 16:55               ` Alexander Holler
2010-12-14 16:21         ` Wolfgang Denk
2010-12-16 10:10           ` Dirk Behme
2010-12-17 10:39             ` Dirk Behme
2010-12-30 12:04               ` 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=4D04A4BD.6070705@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.