public inbox for u-boot@lists.denx.de
 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 09:25:34 +0100	[thread overview]
Message-ID: <4D0486FE.9080601@googlemail.com> (raw)


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?

Thanks

Dirk

[1]
ARMv7: Fix linker errors across toolchain versions
http://lists.denx.de/pipermail/u-boot/2010-December/082874.html

[2]
omap3evm: Clean-up EVM detection code
http://lists.denx.de/pipermail/u-boot/2010-December/082950.html

[3]
  board/ti/evm/evm.c |    4 ++--
  board/ti/evm/evm.h |    2 +-
  2 files changed, 3 insertions(+), 3 deletions(-)

Index: u-boot.git/board/ti/evm/evm.c
===================================================================
--- u-boot.git.orig/board/ti/evm/evm.c
+++ u-boot.git/board/ti/evm/evm.c
@@ -37,9 +37,9 @@
  #include <asm/mach-types.h>
  #include "evm.h"

-static u8 omap3_evm_version;
+static int omap3_evm_version;

-u8 get_omap3_evm_rev(void)
+int get_omap3_evm_rev(void)
  {
  	return omap3_evm_version;
  }
Index: u-boot.git/board/ti/evm/evm.h
===================================================================
--- u-boot.git.orig/board/ti/evm/evm.h
+++ u-boot.git/board/ti/evm/evm.h
@@ -45,7 +45,7 @@ enum {
  	OMAP3EVM_BOARD_GEN_2,		/* EVM Rev >= Rev E */
  };

-u8 get_omap3_evm_rev(void);
+int get_omap3_evm_rev(void);

  #if defined(CONFIG_CMD_NET)
  static void setup_net_chip(void);

             reply	other threads:[~2010-12-12  8:25 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-12  8:25 Dirk Behme [this message]
2010-12-12 10:08 ` [U-Boot] OMAP3: EVM: Linker errors across tool chain versions Albert ARIBAUD
2010-12-12 10:32   ` Dirk Behme
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=4D0486FE.9080601@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