public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RESEND] ca9x4_ct_vxp build error
Date: Tue, 20 Mar 2012 22:11:08 +0100	[thread overview]
Message-ID: <201203202211.08661.marex@denx.de> (raw)

As my previous remark about this board not building was ignored, I'm resending 
it one more time. I'll do one more resend of this note and if noone fixes this 
I'll submit a removal patch.

$ CROSS_COMPILE=arm-linux-gnueabi- ARCH=arm ./MAKEALL ca9x4_ct_vxp
Configuring for ca9x4_ct_vxp board...
common/libcommon.o: In function `cread_line':
/home/marex/U-Boot/u-boot-marex/common/main.c:695: undefined reference to 
`get_ticks'
/home/marex/U-Boot/u-boot-marex/common/main.c:695: undefined reference to 
`get_tbclk'
/home/marex/U-Boot/u-boot-marex/common/main.c:698: undefined reference to 
`get_ticks'
arm-linux-gnueabi-ld: BFD (GNU Binutils for Debian) 2.22 assertion fail 
../../bfd/elf32-arm.c:7498
arm-linux-gnueabi-ld: BFD (GNU Binutils for Debian) 2.22 assertion fail 
../../bfd/elf32-arm.c:7498
arm-linux-gnueabi-ld: BFD (GNU Binutils for Debian) 2.22 assertion fail 
../../bfd/elf32-arm.c:13830
/bin/sh: line 1: 11250 Segmentation fault      arm-linux-gnueabi-ld -pie -T u-
boot.lds -Bstatic -Ttext 0x60800000 $UNDEF_SYM arch/arm/cpu/armv7/start.o --
start-group api/libapi.o arch/arm/cpu/armv7/libarmv7.o arch/arm/lib/libarm.o 
common/libcommon.o disk/libdisk.o drivers/bios_emulator/libatibiosemu.o 
drivers/block/libblock.o drivers/dma/libdma.o drivers/fpga/libfpga.o 
drivers/gpio/libgpio.o drivers/hwmon/libhwmon.o drivers/i2c/libi2c.o 
drivers/input/libinput.o drivers/misc/libmisc.o drivers/mmc/libmmc.o 
drivers/mtd/libmtd.o drivers/mtd/nand/libnand.o drivers/mtd/onenand/libonenand.o 
drivers/mtd/spi/libspi_flash.o drivers/mtd/ubi/libubi.o drivers/net/libnet.o 
drivers/net/phy/libphy.o drivers/pci/libpci.o drivers/pcmcia/libpcmcia.o 
drivers/power/libpower.o drivers/rtc/librtc.o drivers/serial/libserial.o 
drivers/spi/libspi.o drivers/twserial/libtws.o drivers/usb/eth/libusb_eth.o 
drivers/usb/gadget/libusb_gadget.o drivers/usb/host/libusb_host.o 
drivers/usb/musb/libusb_musb.o drivers/usb/phy/libusb_phy.o 
drivers/usb/ulpi/libusb_ulpi.o drivers/video/libvideo.o 
drivers/watchdog/libwatchdog.o fs/cramfs/libcramfs.o fs/ext2/libext2fs.o 
fs/fat/libfat.o fs/fdos/libfdos.o fs/jffs2/libjffs2.o fs/reiserfs/libreiserfs.o 
fs/ubifs/libubifs.o fs/yaffs2/libyaffs2.o lib/libfdt/libfdt.o lib/libgeneric.o 
lib/lzma/liblzma.o lib/lzo/liblzo.o lib/zlib/libz.o net/libnet.o post/libpost.o 
board/armltd/vexpress/libvexpress.o --end-group /home/marex/U-Boot/u-boot-
marex/arch/arm/lib/eabi_compat.o -L /usr/lib/gcc/arm-linux-gnueabi/4.4.6 -lgcc -
Map u-boot.map -o u-boot
make: *** [u-boot] Error 139
arm-linux-gnueabi-size: ./u-boot: File format not recognized

--------------------- SUMMARY ----------------------------
Boards compiled: 1
Boards with warnings or errors: 1 ( ca9x4_ct_vxp )
----------------------------------------------------------

             reply	other threads:[~2012-03-20 21:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-20 21:11 Marek Vasut [this message]
2012-03-21 17:22 ` [U-Boot] [RESEND] ca9x4_ct_vxp build error Matt Waddel
2012-03-21 19:24   ` Marek Vasut

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=201203202211.08661.marex@denx.de \
    --to=marex@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