From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] Build failures at bb3bcfa2
Date: Wed, 16 Dec 2009 11:03:48 +0100 [thread overview]
Message-ID: <200912161103.48600.sr@denx.de> (raw)
In-Reply-To: <B85A65D85D7EB246BE421B3FB0FBB59301E157AF1F@dbde02.ent.ti.com>
On Wednesday 16 December 2009 10:52:44 Premi, Sanjeev wrote:
> Just pulled latest master at:
>
> commit bb3bcfa2426cc6a0aecec7270e3ee67ca843a125
> Merge: a200a7c 4b142fe
> Author: Wolfgang Denk <wd@denx.de>
> Date: Tue Dec 15 23:38:34 2009 +0100
>
> Merge branch 'next' of ../next
>
> However, I am noticing build failures. See log below:
>
> Best regards,
> Sanjeev
>
> premi # make distclean
> premi # make omap3_evm_config
> Configuring for omap3_evm board...
> premi # make ARCH=arm CROSS_COMPILE=arm-none-linux-gnueabi-
> Generating include/autoconf.mk
> Generating include/autoconf.mk.dep
> for dir in tools examples/standalone examples/api ; do make -C $dir _depend
> ; done make[1]: Entering directory `/home/premi/u-boot/tools'
> make[1]: Leaving directory `/home/premi/u-boot/tools'
> make[1]: Entering directory `/home/premi/u-boot/tools'
> make[1]: Nothing to be done for `_depend'.
> make[1]: Leaving directory `/home/premi/u-boot/tools'
> make[1]: Entering directory `/home/premi/u-boot/examples/standalone'
> make[1]: Leaving directory `/home/premi/u-boot/examples/standalone'
> make[1]: Entering directory `/home/premi/u-boot/examples/standalone'
> make[1]: Nothing to be done for `_depend'.
> make[1]: Leaving directory `/home/premi/u-boot/examples/standalone'
> make[1]: Entering directory `/home/premi/u-boot/examples/api'
> make[1]: Nothing to be done for `_depend'.
> make[1]: Leaving directory `/home/premi/u-boot/examples/api'
> make -C tools all
> make[1]: Entering directory `/home/premi/u-boot/tools'
> arm-none-linux-gnueabi-gcc -g -Os -fno-common -ffixed-r8 -msoft-float
> -D__KERNEL__ -DTEXT_BASE=0x80e80000 -I/home/premi/u-boot/include
> -fno-builtin -ffreestanding -nostdinc -isystem
> /opt/codesourcery/2009q1-203/bin/../lib/gcc/arm-none-linux-gnueabi/4.3.3/i
> nclude -pipe -DCONFIG_ARM -D__ARM__ -marm -mabi=aapcs-linux
> -mno-thumb-interwork -march=armv5 -Wall -Wstrict-prototypes
> -fno-stack-protector -o crc32.o crc32.c -c arm-none-linux-gnueabi-gcc
> -g -Os -fno-common -ffixed-r8 -msoft-float -D__KERNEL__
> -DTEXT_BASE=0x80e80000 -I/home/premi/u-boot/include -fno-builtin
> -ffreestanding -nostdinc -isystem
> /opt/codesourcery/2009q1-203/bin/../lib/gcc/arm-none-linux-gnueabi/4.3.3/i
> nclude -pipe -DCONFIG_ARM -D__ARM__ -marm -mabi=aapcs-linux
> -mno-thumb-interwork -march=armv5 -Wall -Wstrict-prototypes
> -fno-stack-protector -o env_embedded.o env_embedded.c -c gcc -Wall
> -Wstrict-prototypes -O2 -fomit-frame-pointer -idirafter
> /home/premi/u-boot/include -idirafter /home/premi/u-boot/include2
> -idirafter /home/premi/u-boot/include -I /home/premi/u-boot/libfdt -I
> /home/premi/u-boot/tools -DTEXT_BASE=0x80e80000 -DUSE_HOSTCC
> -D__KERNEL_STRICT_NAMES -pedantic -o envcrc.o envcrc.c -c
> arm-none-linux-gnueabi-gcc -g -Os -fno-common -ffixed-r8 -msoft-float
> -D__KERNEL__ -DTEXT_BASE=0x80e80000 -I/home/premi/u-boot/include
> -fno-builtin -ffreestanding -nostdinc -isystem
> /opt/codesourcery/2009q1-203/bin/../lib/gcc/arm-none-linux-gnueabi/4.3.3/i
> nclude -pipe -DCONFIG_ARM -D__ARM__ -marm -mabi=aapcs-linux
> -mno-thumb-interwork -march=armv5 -Wall -Wstrict-prototypes
> -fno-stack-protector -o sha1.o sha1.c -c gcc -Wall -Wstrict-prototypes
> -O2 -fomit-frame-pointer -idirafter /home/premi/u-boot/include -idirafter
> /home/premi/u-boot/include2 -idirafter /home/premi/u-boot/include -I
> /home/premi/u-boot/libfdt -I /home/premi/u-boot/tools
> -DTEXT_BASE=0x80e80000 -DUSE_HOSTCC -D__KERNEL_STRICT_NAMES -pedantic -o
> envcrc crc32.o env_embedded.o envcrc.o sha1.o /usr/bin/ld: crc32.o:
> Relocations in generic ELF (EM: 40)
> crc32.o: could not read symbols: File in wrong format
> collect2: ld returned 1 exit status
> make[1]: *** [envcrc] Error 1
> make[1]: Leaving directory `/home/premi/u-boot/tools'
> make: *** [tools] Error 2
Most likely the same problem I stumbled upon a few days ago. Here my thread:
http://thread.gmane.org/gmane.comp.boot-loaders.u-boot/71125/focus=72327
Do you by any chance have a copy of/link to crc32.c, env_embedded.c, etc.
sitting in your tools directory?
Cheers,
Stefan
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-0 Fax: (+49)-8142-66989-80 Email: office at denx.de
next prev parent reply other threads:[~2009-12-16 10:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-16 9:52 [U-Boot] Build failures at bb3bcfa2 Premi, Sanjeev
2009-12-16 10:03 ` Stefan Roese [this message]
2009-12-16 11:49 ` Premi, Sanjeev
2009-12-16 12:00 ` Stefan Roese
2009-12-16 15:17 ` Wolfgang Denk
2009-12-16 15:19 ` Premi, Sanjeev
2009-12-16 21:07 ` Wolfgang Denk
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=200912161103.48600.sr@denx.de \
--to=sr@denx.de \
--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