[U-Boot] [PATCH] yaffs2: Fix GCC 4.6 compile warnings

[Scott Wood]

On 10/06/2012 11:59:17 AM, Albert ARIBAUD wrote:
> Hi Anatolij,
> 
> On Sat,  6 Oct 2012 11:31:03 +0200, Anatolij Gustschin <agust at denx.de>
> wrote:
> 
> > Fix:
> > yaffs_guts.c: In function 'yaffs_check_chunk_erased':
> > yaffs_guts.c:324:6: warning: variable 'result' set but not used
> > [-Wunused-but-set-variable]
[snip]
> Tested-by: Albert ARIBAUD <albert.u.boot at aribaud.net>
> 
> This effectively makes VCMA9 and smdk2410 (the two boards which had
> the yaffs warnings) build clean.

It takes care of the warnings, but I still see this:

Configuring for VCMA9 board...
make: *** [u-boot] Error 139
/home/scott/fsl/tc/arm-gentoo-linux-gnu/bin/arm-gentoo-linux-gnu-size:  
./u-boot: File format not recognized
fs/yaffs2/libyaffs2.o: In function `cmd_yaffs_devconfig':
/home/scott/fsl/git/u-boot/upstream/fs/yaffs2/yaffs_uboot_glue.c:187:  
undefined reference to `__udivdi3'
fs/yaffs2/libyaffs2.o: In function `yaffsfs_DoStat':
/home/scott/fsl/git/u-boot/upstream/fs/yaffs2/yaffsfs.c:1606: undefined  
reference to `__divdi3'
   
/home/scott/fsl/tc/arm-gentoo-linux-gnu/bin/arm-gentoo-linux-gnu-ld.bfd:  
BFD (GNU Binutils) 2.21.1 assertion fail  
/var/tmp/portage/cross-arm-gentoo-linux-gnu/binutils-2.21.1-r1/work/binutils-2.21.1/bfd/elf32-arm.c:12478
/bin/bash: line 1:  6558 Segmentation fault      (core dumped)  
/home/scott/fsl/tc/arm-gentoo-linux-gnu/bin/arm-gentoo-linux-gnu-ld.bfd  
-pie -T u-boot.lds -Bstatic -Ttext 0x0 $UNDEF_SYM  
arch/arm/cpu/arm920t/start.o --start-group api/libapi.o  
arch/arm/cpu/arm920t/libarm920t.o  
arch/arm/cpu/arm920t/s3c24x0/libs3c24x0.o arch/arm/lib/libarm.o  
common/libcommon.o disk/libdisk.o drivers/bios_emulator/libatibiosemu.o  
drivers/block/libblock.o drivers/dfu/libdfu.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/ext4/libext4fs.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 fs/zfs/libzfs.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 test/libtest.o board/mpl/vcma9/libvcma9.o  
--end-group /home/scott/fsl/git/u-boot/upstream/arch/arm/lib/libgcc.o  
-Map u-boot.map -o u-boot
make: *** [u-boot] Error 139

This is with USE_PRIVATE_LIBGCC=yes and "gcc version 4.6.2 (Gentoo 4.6.2
p1.0, pie-0.4.5)" from Mike Frysinger's toolchain set.

Turning off USE_PRIVATE_LIBGCC produces more errors (lots of hard/soft  
FP
conflicts, undefined "raise", and the same linker segfault).

Is this toolchain expected to work?

-Scott