RE: init hang after upgrading ARM-Linux toolchain

["Creech, Matthew L" <MatthewLCreech at eaton dot com>]

crossgcc-owner@sourceware.org wrote:
> 
> How I read over this page:
> 
> http://wiki.debian.org/ArmEabiPort
> 
> several times and totally glossed over that part is beyond me.  From
> that page, it sounds like it was just a mistake that kept v4t support
> out of 4.1.0, then?  (Maybe my search terms are off, but I
> couldn't turn
> up any direct information on this)
> 
> Thanks for the help!  For the time being I'll just see if I
> can get the
> non-EABI toolchain to work, and keep my fingers crossed for 4.1.1...
> 

FYI, the finger-crossing worked!  :)  I updated crosstool to use
binutils-2.16.93 and gcc-4.1.1, and the new toolchain builds and runs a
full EABI kernel + userspace on my AT91RM9200.

I do have trouble with my bootloader, though.  U-boot gets to the final
link stage, then bails out with this error:

/home/mlcreech/toolchain/gcc-4.1.1-glibc-2.4/arm-linux-gnueabi/lib/gcc/a
rm-linux-gnueabi/4.1.1/libgcc.a(_dvmd_lnx.o): In function `__div0':
/home/mlcreech/crosstool/crosstool-0.42/build/arm-linux-gnueabi/gcc-4.1.
1-glibc-2.4/gcc-4.1.1/gcc/config/arm/lib1funcs.asm:1000: undefined
reference to `raise'
make[4]: *** [u-boot] Error 1

Is this a toolchain issue, or a U-boot issue?  If it's U-boot, any ideas
on what needs to be done to fix it?  Google turned up no hits, but it
looks like I might need to prevent it from linking in libgcc's __div0
(total guess)...

Thanks in advance

-- 
Matthew L. Creech

--
For unsubscribe information see http://sourceware.org/lists.html#faq