From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jean-Christophe PLAGNIOL-VILLARD Date: Sun, 23 Nov 2008 01:27:15 +0100 Subject: [U-Boot] U-boot build failes with armv5tel-reghat-linux-gnueabi-gcc (4.1.2) In-Reply-To: <20081119120613.GA30468@game.jcrosoft.org> References: <914A49A27B87C143AC977D773E7E79B791BDE2@msiexch01.marvell.com> <20081119120613.GA30468@game.jcrosoft.org> Message-ID: <20081123002715.GC7930@game.jcrosoft.org> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 13:06 Wed 19 Nov , Jean-Christophe PLAGNIOL-VILLARD wrote: > On 03:10 Wed 19 Nov , Prafulla Wadaskar wrote: > > Hi > > I am using u-boot-1.1.6 and building u-boot from my new board which includes nand flash support > > > > If I build using armv5tel-reghat-linux-gnueabi-gcc (4.1.2) toolchain it gives build failure with below log > > > > --start-group lib_generic/libgeneric.a board/Marvell/rd6281/librd6281.a cpu/arm926ejs/libarm926ejs.a cpu/arm926ejs/feroceon/libferoceon.a lib_arm/libarm.a fs/cramfs/libcramfs.a fs/fat/libfat.a fs/fdos/libfdos.a fs/jffs2/libjffs2.a fs/reiserfs/libreiserfs.a fs/ext2/libext2fs.a net/libnet.a disk/libdisk.a rtc/librtc.a dtt/libdtt.a drivers/libdrivers.a drivers/nand/libnand.a drivers/nand_legacy/libnand_legacy.a drivers/sk98lin/libsk98lin.a post/libpost.a post/cpu/libcpu.a common/libcommon.a --end-group -L /usr/lib/gcc/armv5tel-redhat-linux-gnueabi/4.1.2 -lgcc \ > > -Map u-boot.map -o u-boot > > /usr/lib/gcc/armv5tel-redhat-linux-gnueabi/4.1.2/libgcc.a(_divdi3.o):(.ARM.exidx+0x0): undefined reference to `__aeabi_unwind_cpp_pr0' > > /usr/lib/gcc/armv5tel-redhat-linux-gnueabi/4.1.2/libgcc.a(_udivdi3.o):(.ARM.exidx+0x0): undefined reference to `__aeabi_unwind_cpp_pr0' > > make: *** [u-boot] Error 1 > > > > Whereas, > > If I build the same code using codesoucery toolchain (arm2008q1) release (gcc ver 4.2.3) the build is sucessfull. > > > > I want to go ahead with armv5tel-reghat-linux-gnueabi-gcc (4.1.2) > > Can someone suggest what is problem and how should I proceed? > update the divdi3 and _udivdi3 implementation > > I'll said > > so please try this patch > > please note I've just test it on one board > > Best Regards, > J. Any news? Best Regards, J.