public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Philip Balister <philip@balister.org>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Trouble building u-boot 1.2 with NAND  support
Date: Wed, 30 May 2007 11:56:28 -0400	[thread overview]
Message-ID: <465D9EAC.6080608@balister.org> (raw)
In-Reply-To: <465C68CA.7070505@balister.org>

Let me try again, with a specific questions

Philip Balister wrote:

> /home/balister/oe_home/tmp/cross/lib/gcc/arm-angstrom-linux-gnueabi/4.1.2/libgcc.a(_udivsi3.o): 
> In function `__aeabi_uidiv':
> /home/balister/oe_home/tmp/work/armv5te-angstrom-linux-gnueabi/gcc-cross-4.1.2-r4/gcc-4.1.2/gcc/config/arm/lib1funcs.asm:730: 
> multiple definition of `__udivsi3'
> lib_arm/libarm.a(_udivsi3.o):/home/balister/src/sffsdr/koi8_u-boot/lib_arm/_udivsi3.S:17: 
 > first defined here

It seems like libarm in u-boot defines some of the helper functions 
normally found in libgcc. For some reason I am linking against both 
libraries. Maybe there is a problem using an EABI compiler with u-boot? 
Although I build u-boot fine for omap5912osk with the same toolchain.

Philip
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 3303 bytes
Desc: S/MIME Cryptographic Signature
Url : http://lists.denx.de/pipermail/u-boot/attachments/20070530/58e2abcf/attachment.bin 

      reply	other threads:[~2007-05-30 15:56 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-29 17:54 [U-Boot-Users] Trouble building u-boot 1.2 with NAND support Philip Balister
2007-05-30 15:56 ` Philip Balister [this message]

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=465D9EAC.6080608@balister.org \
    --to=philip@balister.org \
    --cc=u-boot@lists.denx.de \
    /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