Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Ulf Samuelsson <ulf.samuelsson@atmel.com>
To: buildroot@busybox.net
Subject: [Buildroot] UBOOT 2009.08 & ARM Link Error
Date: Mon, 14 Sep 2009 08:02:49 +0200	[thread overview]
Message-ID: <4AADDC89.7070302@atmel.com> (raw)
In-Reply-To: <2FAA2DE137CA432EBF8BEE2E967A7993@apexjs>

Sagaert Johan skrev:
> Hi
>  
> Did anyone succeed in building the UBOOT 2009.08 version for ARM 
> (at91sam9260_config)?
>  
> I always end up with this error :
>  

Yes, I can build 2009.08 in my personal git tree.
git://git.busybox.net/~ulf/git/atmel-2009-08

You need some fixes, which are present there.
While I did not test the SAM9260 as such, this is a generic
problem for ARM, which gets fixed by my patches.

My git tree also contains linux-2.6.30.2 and an updated
at91bootstrap.
Still a lot of testing to be done.
Help appreciated.




> arm-linux-ld: ERROR: 
> /home/johan/buildroot/build_arm/staging_dir/usr/bin-ccache/../lib/gcc/arm-linux-uclibc/4.3.3/libgcc.a(_udivsi3.o) 
> uses hardware FP, whereas u-boot uses software FP
> arm-linux-ld: failed to merge target specific data of file 
> /home/johan/buildroot/build_arm/staging_dir/usr/bin-ccache/../lib/gcc/arm-linux-uclibc/4.3.3/libgcc.a(_udivsi3.o)
> arm-linux-ld: ERROR: 
> /home/johan/buildroot/build_arm/staging_dir/usr/bin-ccache/../lib/gcc/arm-linux-uclibc/4.3.3/libgcc.a(_divsi3.o) 
> uses hardware FP, whereas u-boot uses software FP
> arm-linux-ld: failed to merge target specific data of file 
> /home/johan/buildroot/build_arm/staging_dir/usr/bin-ccache/../lib/gcc/arm-linux-uclibc/4.3.3/libgcc.a(_divsi3.o)
> arm-linux-ld: ERROR: 
> /home/johan/buildroot/build_arm/staging_dir/usr/bin-ccache/../lib/gcc/arm-linux-uclibc/4.3.3/libgcc.a(_umodsi3.o) 
> uses hardware FP, whereas u-boot uses software FP
> arm-linux-ld: failed to merge target specific data of file 
> /home/johan/buildroot/build_arm/staging_dir/usr/bin-ccache/../lib/gcc/arm-linux-uclibc/4.3.3/libgcc.a(_umodsi3.o)
> arm-linux-ld: ERROR: 
> /home/johan/buildroot/build_arm/staging_dir/usr/bin-ccache/../lib/gcc/arm-linux-uclibc/4.3.3/libgcc.a(_modsi3.o) 
> uses hardware FP, whereas u-boot uses software FP
> arm-linux-ld: failed to merge target specific data of file 
> /home/johan/buildroot/build_arm/staging_dir/usr/bin-ccache/../lib/gcc/arm-linux-uclibc/4.3.3/libgcc.a(_modsi3.o)
> arm-linux-ld: ERROR: 
> /home/johan/buildroot/build_arm/staging_dir/usr/bin-ccache/../lib/gcc/arm-linux-uclibc/4.3.3/libgcc.a(_dvmd_lnx.o) 
> uses hardware FP, whereas u-boot uses software FP
> arm-linux-ld: failed to merge target specific data of file 
> /home/johan/buildroot/build_arm/staging_dir/usr/bin-ccache/../lib/gcc/arm-linux-uclibc/4.3.3/libgcc.a(_dvmd_lnx.o)
> arm-linux-ld: ERROR: 
> /home/johan/buildroot/build_arm/staging_dir/usr/bin-ccache/../lib/gcc/arm-linux-uclibc/4.3.3/libgcc.a(_lshrdi3.o) 
> uses hardware FP, whereas u-boot uses software FP
> arm-linux-ld: failed to merge target specific data of file 
> /home/johan/buildroot/build_arm/staging_dir/usr/bin-ccache/../lib/gcc/arm-linux-uclibc/4.3.3/libgcc.a(_lshrdi3.o)
> arm-linux-ld: ERROR: 
> /home/johan/buildroot/build_arm/staging_dir/usr/bin-ccache/../lib/gcc/arm-linux-uclibc/4.3.3/libgcc.a(_ashldi3.o) 
> uses hardware FP, whereas u-boot uses software FP
> arm-linux-ld: failed to merge target specific data of file 
> /home/johan/buildroot/build_arm/staging_dir/usr/bin-ccache/../lib/gcc/arm-linux-uclibc/4.3.3/libgcc.a(_ashldi3.o)
> arm-linux-ld: ERROR: 
> /home/johan/buildroot/build_arm/staging_dir/usr/bin-ccache/../lib/gcc/arm-linux-uclibc/4.3.3/libgcc.a(_ashrdi3.o) 
> uses hardware FP, whereas u-boot uses software FP
> arm-linux-ld: failed to merge target specific data of file 
> /home/johan/buildroot/build_arm/staging_dir/usr/bin-ccache/../lib/gcc/arm-linux-uclibc/4.3.3/libgcc.a(_ashrdi3.o)
> make: *** [u-boot] Error 1
>  
> The 2009.06 version does not produce this error, so i will be using this 
> one i guess .
>  
> I wonder if this is a toolchain issue or a uboot error .
>  
> If a recent version gets pushed into buildroot, does someone then 
> verifies it works ?
>  
> Johan
>  
>  
> 
> 
> ------------------------------------------------------------------------
> 
> _______________________________________________
> buildroot mailing list
> buildroot at busybox.net
> http://lists.busybox.net/mailman/listinfo/buildroot

  parent reply	other threads:[~2009-09-14  6:02 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-10  7:50 [Buildroot] UBOOT 2009.08 & ARM Link Error Sagaert Johan
2009-09-10  8:14 ` Peter Korsgaard
2009-09-14  6:02 ` Ulf Samuelsson [this message]
2009-09-14  9:36   ` Peter Korsgaard
2009-09-14 15:42     ` Ulf Samuelsson
     [not found] <A41BAEC7EC0449D8BB97311F11270777@apexjs>
2009-09-10  9:06 ` Peter Korsgaard
2009-09-10 14:02   ` Shinya Kuribayashi

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=4AADDC89.7070302@atmel.com \
    --to=ulf.samuelsson@atmel.com \
    --cc=buildroot@busybox.net \
    /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