[U-Boot-Users] linking error with insight cross compiler

[VanBaren, Gerald (AGRE)]

I'm not familiar with your board or tools, but the first error is "uses hardware FP, whereas u-boot uses software FP".  Does your target hardware have hardware floating point?  If so, turn off the "soft float" switch in your u-boot build.  If not, you need a library that supports soft floating point instead of hard.

In your second email, you stated you switched linkers.  The linker isn't the problem, either the compiler switches (hard vs. soft floating point) or your libraries are the problem.

Rules for debugging:
1) Always fix the first problem first.
2) Always fix know problems before fixing unknown problems.
3) Always fix the problem or it will bite you in strange and wonderous ways later.

gvb


> -----Original Message-----
> From: u-boot-users-admin at lists.sourceforge.net
> [mailto:u-boot-users-admin at lists.sourceforge.net]On Behalf Of Himansu
> Doshi
> Sent: Saturday, January 10, 2004 5:03 AM
> To: u-boot-users at lists.sourceforge.net
> Subject: [U-Boot-Users] linking error with insight cross compiler
> 
> 
> Hi,
> 
> I am compiling u-boot for at91rm9200dk board. I am using insight for 
> debugging and the cross compiler for arm is also from 
> insight. I am able to 
> compile all the file's properly. However when the linking 
> take place I get 
> an error for the libgcc.a file. The error is as follows----
> 
>                 -Map u-boot.map -o u-boot
> /insight/usr/local/csb337/bin/arm-linux-ld: ERROR: he 
> /insight/usr/local/csb337/bin/../lib/gcc-lib/arm-linux/3.3.1/l
> ibgcc.a(_udivsi3.oS) 
> uses hardware FP, whereas u-boot uses software FP
> File in wrong format: failed to merge target specific data of file 
> /insight/usr/local/csb337/bin/../lib/gcc-lib/arm-linux/3.3.1/l
> ibgcc.a(_udivsi3.oS)
> /insight/usr/local/csb337/bin/arm-linux-ld: ERROR: 
> /insight/usr/local/csb337/bin/../lib/gcc-lib/arm-linux/3.3.1/l
> ibgcc.a(_umodsi3.oS) 
> uses hardware FP, whereas u-boot uses software FP
> File in wrong format: failed to merge target specific data of file 
> /insight/usr/local/csb337/bin/../lib/gcc-lib/arm-linux/3.3.1/l
> ibgcc.a(_umodsi3.oS)
> /insight/usr/local/csb337/bin/arm-linux-ld: ERROR: 
> /insight/usr/local/csb337/bin/../lib/gcc-lib/arm-linux/3.3.1/l
> ibgcc.a(_dvmd_lnx.oS) 
> uses hardware FP, whereas u-boot uses software FP
> File in wrong format: failed to merge target specific data of file 
> /insight/usr/local/csb337/bin/../lib/gcc-lib/arm-linux/3.3.1/l
> ibgcc.a(_dvmd_lnx.oS)
> make: *** [u-boot] Error 1
> 
> can you please help me out with this problem.....
> 
> Thanks
> 
> _________________________________________________________________
> Free drafts to 700 locations. 
> http://server1.msn.co.in/msnleads/suvidha/dec03.asp?type=hotta
g Click here.



-------------------------------------------------------
This SF.net email is sponsored by: Perforce Software.
Perforce is the Fast Software Configuration Management System offering
advanced branching capabilities and atomic changes on 50+ platforms.
Free Eval! http://www.perforce.com/perforce/loadprog.html
_______________________________________________
U-Boot-Users mailing list
U-Boot-Users at lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/u-boot-users



******************************************
The information contained in, or attached to, this e-mail, may contain confidential information and is intended solely for the use of the individual or entity to whom they are addressed and may be subject to legal privilege.  If you have received this e-mail in error you should notify the sender immediately by reply e-mail, delete the message from your system and notify your system manager.  Please do not copy it for any purpose, or disclose its contents to any other person.  The views or opinions presented in this e-mail are solely those of the author and do not necessarily represent those of the company.  The recipient should check this e-mail and any attachments for the presence of viruses.  The company accepts no liability for any damage caused, directly or indirectly, by any virus transmitted in this email.
******************************************