All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ulf Samuelsson <ulf.samuelsson@atmel.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] "raise" not defined, when compiler uses its own div0
Date: Tue, 11 Aug 2009 23:48:20 +0200	[thread overview]
Message-ID: <4A81E724.3070205@atmel.com> (raw)
In-Reply-To: <20090811084728.4E968833DBD2@gemini.denx.de>

Wolfgang Denk skrev:
> Dear Ulf Samuelsson,
> 
> In message <4A810DBC.50805@atmel.com> you wrote:
>> When trying to build U-Boot under Buildroot and OpenEmbedded,
> 
> These probably count to the tool chains with "broken" ARM cross
> compilers.

Maybe,
Buildroot is even more broken, if you try to use an external toolchain
and I would be surprised if openembedded is better.
In the end, noone wants to mess around with one compiler per application
so it is better if a small fix to u-boot can be applied.

> 
>> When linking u-boot the linker seems to use the div0 from
>> the C compiler libgcc instead of the u-boot div0.
> 
> Try setting USE_PRIVATE_LIBGCC=yes in your envrionment, like
> 
> 	USE_PRIVATE_LIBGCC=yes make ...

I have done two fixes to make it build with openembedded.
1) Define "raise" in libarm/board.c which calls hang.
2) Changes mapi to "-mapi=aapcs-linux" in cpu/arm926ej-s/config.mk
   Some toolchains want to keep apcs-gnu I guess.

> 
> Best regards,
> 
> Wolfgang Denk
> 

BR
Ulf Samuelsson

  reply	other threads:[~2009-08-11 21:48 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-11  6:20 [U-Boot] "raise" not defined, when compiler uses its own div0 Ulf Samuelsson
2009-08-11  8:14 ` Gaye Abdoulaye Walsimou
2009-08-11  8:48   ` Wolfgang Denk
2009-08-11  8:47 ` Wolfgang Denk
2009-08-11 21:48   ` Ulf Samuelsson [this message]
2009-08-11 21:58     ` Wolfgang Denk
2009-08-12  6:22       ` Ulf Samuelsson
2009-08-12 12:04         ` Wolfgang Denk
2009-08-13  4:55           ` Mike Frysinger

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=4A81E724.3070205@atmel.com \
    --to=ulf.samuelsson@atmel.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.