public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Scott Wood <scottwood@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH v2] makefiles: fixes for building build tools
Date: Thu, 03 Dec 2009 11:49:26 -0600	[thread overview]
Message-ID: <4B17FA26.3060203@freescale.com> (raw)
In-Reply-To: <200912030826.59587.sr@denx.de>

Stefan Roese wrote:
> Hi Scott,
> 
> On Wednesday 02 December 2009 22:59:03 Wolfgang Denk wrote:
>>>  config.mk               |   34 ++++++++++++-
>>>  rules.mk                |   13 ++++-
>>>  tools/Makefile          |  121
>>> +++++++++++++---------------------------------
>>>  tools/easylogo/Makefile |    9 ++-
>>>  tools/gdb/Makefile      |   15 ++----
>>>  tools/imls/Makefile     |   29 ++++-------
>>>  6 files changed, 98 insertions(+), 123 deletions(-)
>> Applied to "next".  Thanks.
> 
> This patch causes some problems, at least on 4xx platforms (others as well I 
> suspect):
> 
> [stefan at stefan-desktop u-boot (next)]$ ./MAKEALL kilauea
> Configuring for kilauea board...
> /usr/bin/ld: crc32.o: Relocations in generic ELF (EM: 20)
> /usr/bin/ld: crc32.o: Relocations in generic ELF (EM: 20)
> /usr/bin/ld: crc32.o: Relocations in generic ELF (EM: 20)
> /usr/bin/ld: crc32.o: Relocations in generic ELF (EM: 20)
> /usr/bin/ld: crc32.o: Relocations in generic ELF (EM: 20)
> /usr/bin/ld: crc32.o: Relocations in generic ELF (EM: 20)
> /usr/bin/ld: crc32.o: Relocations in generic ELF (EM: 20)
> crc32.o: could not read symbols: File in wrong format
> collect2: ld returned 1 exit status
> 
> 
> This is on "next" with ELDK 4.2. Scott, do you have any ideas what's going 
> wrong here?

I don't see that here -- instead, I get this, with or without this patch:

$ CROSS_COMPILE=powerpc-linux- ./MAKEALL kilauea
Configuring for kilauea board...
powerpc-linux-ld: u-boot: section `.text' can't be allocated in segment 0
powerpc-linux-ld: final link failed: Bad value
make: *** [u-boot] Error 1

This is with binutils 2.18.  Do I need to upgrade?

Git bisect says:
4649913ea5f440d756d150a6fdf2fb2e8ecb75fd is the first bad commit
commit 4649913ea5f440d756d150a6fdf2fb2e8ecb75fd
Author: Stefan Roese <sr@denx.de>
Date:   Tue Oct 27 16:11:26 2009 +0100

     ppc4xx: Add common ppc4xx linker script

     This linker script can be used by all PPC4xx platforms. It works for
     PPC405 and PPC440 platforms. Boards which need a board specific linker
     script can override this default linker script in board/*/config.mk.

     Signed-off-by: Stefan Roese <sr@denx.de>

Can you post a full boot log of your error?  I'm guessing host crc32.o is 
getting linked into target code or vice versa, though I don't see why that would 
happen only on 4xx.  One should be tools/crc32.o and the other should be 
lib_generic/crc32.o.

-Scott

  reply	other threads:[~2009-12-03 17:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-05  0:41 [U-Boot] [PATCH v2] makefiles: fixes for building build tools Scott Wood
2009-11-13 18:51 ` Mike Frysinger
2009-11-13 18:53   ` Scott Wood
2009-11-13 23:07     ` Mike Frysinger
2009-12-02 21:59 ` Wolfgang Denk
2009-12-03  7:26   ` Stefan Roese
2009-12-03 17:49     ` Scott Wood [this message]
2009-12-03 18:17       ` Stefan Roese
2009-12-03 19:09         ` Scott Wood
2009-12-04  3:45           ` Stefan Roese

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=4B17FA26.3060203@freescale.com \
    --to=scottwood@freescale.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