public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
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 16:23:30 +0100	[thread overview]
Message-ID: <4CEA8AF2.40904@free.fr> (raw)
In-Reply-To: <B85A65D85D7EB246BE421B3FB0FBB59302477EB3EC@dbde02.ent.ti.com>

Le 22/11/2010 16:02, Premi, Sanjeev a ?crit :
>> -----Original Message-----
>> From: Albert ARIBAUD [mailto:albert.aribaud at free.fr]
>> Sent: Monday, November 22, 2010 8:02 PM
>> To: Premi, Sanjeev
>> Cc: Wolfgang Denk; u-boot at lists.denx.de
>> Subject: Re: Build failures with older toolchain
>>
>> 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.
>
> [sp] Are you referring to this patch?
>       http://git.denx.de/?p=u-boot.git;a=commitdiff;h=aaeb0a890a050b58be87fa2b165eec5fa947dc86
>
>       I see the change for arm926ejs/u-boot.lds and armv7/u-boot.lds
>       to be similar.
>
>       Your commit mentions about the new ld vs. old; I had seen this
>       earlier as well. It was the reason for me to try CodeSourcery
>       Lite 2010-q1 but there I get a different error - mentioned in my
>       first post.
>
>       Which toolchain version are you using?

I usually try the 2009q3 Code Sourcery and the ELDK 4.2 toolchains.

Can you compare the ld invocation command lines for a failure case and a 
success case? The difference could be in the linker options.

Amicalement,
-- 
Albert.

  reply	other threads:[~2010-11-22 15:23 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
2010-11-22 14:42           ` Premi, Sanjeev
2010-11-22 15:02           ` Premi, Sanjeev
2010-11-22 15:23             ` Albert ARIBAUD [this message]
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=4CEA8AF2.40904@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