From: Wolfgang Denk <wd@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] "raise" not defined, when compiler uses its own div0
Date: Tue, 11 Aug 2009 23:58:59 +0200 [thread overview]
Message-ID: <20090811215859.E199D833DBD2@gemini.denx.de> (raw)
In-Reply-To: <4A81E724.3070205@atmel.com>
Dear Ulf Samuelsson,
In message <4A81E724.3070205@atmel.com> you wrote:
>
> > 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.
Did you use "USE_PRIVATE_LIBGCC=yes", and it still needed raise(),
or did you implement that workaround instead of using
"USE_PRIVATE_LIBGCC=yes".
Normally no raise() should be needed when using USE_PRIVATE_LIBGCC=yes
> 2) Changes mapi to "-mapi=aapcs-linux" in cpu/arm926ej-s/config.mk
> Some toolchains want to keep apcs-gnu I guess.
I wonder why we enforce a specific API at all - would it not be better
to use the toolchain provided default settings?
Best regards,
Wolfgang Denk
--
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de
Single tasking: Just Say No.
next prev parent reply other threads:[~2009-08-11 21:58 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
2009-08-11 21:58 ` Wolfgang Denk [this message]
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=20090811215859.E199D833DBD2@gemini.denx.de \
--to=wd@denx.de \
--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