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] OMAP3: EVM: Linker errors across tool chain versions
Date: Sun, 12 Dec 2010 12:40:27 +0100	[thread overview]
Message-ID: <4D04B4AB.7080405@free.fr> (raw)
In-Reply-To: <4D04A4BD.6070705@googlemail.com>

Le 12/12/2010 11:32, Dirk Behme a ?crit :

 >> 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

Actually that's not exact. If you do a ./MAKEALL omap3_evm, yes, the 
build will fail. But (with 2010q1 at least, but I d'wager this works 
with 2009q3 as well) a 'make distclean; make omap3_evm_config; make' 
builds despite the linker message.

Can you try this as a diagnostic measure?

Also, you may want to try adding --no-check-sections to the linker flags 
-- again as a diagnostic measure only, not as a fix -- because a quick 
test shows me that the .bin is really different then.

Amicalement,
-- 
Albert.

  reply	other threads:[~2010-12-12 11:40 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
2010-12-12 11:40     ` Albert ARIBAUD [this message]
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=4D04B4AB.7080405@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