From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] CONFIG_API, EABI and raise()
Date: Wed, 15 Jul 2009 17:10:04 +0200 [thread overview]
Message-ID: <200907151710.04262.sr@denx.de> (raw)
In-Reply-To: <200907151058.41536.vapier@gentoo.org>
On Wednesday 15 July 2009 16:58:40 Mike Frysinger wrote:
> On Tuesday 14 July 2009 09:47:26 Piotr Zi?cik wrote:
> > While working on U-Boot for our board we have found problem related to
> > CONFIG_API option. In general, enabling it causes build failure. Our
> > tests showed that problem exists also on other ARM U-Boot targets (for
> > example davinci_dvevm).
> >
> > Do you think that this problem may be caused by your libgcc-related
> > cleanups ? If so, do you have any idea how to fix it ?
>
> sounds more like it's always been a bug, but Jean's cleanup will fix it
> eventually
That's my understanding too.
I vote for accepting Jean-Christophe's libgcc patches in the latest version.
They definitely fix some ugly problems seen on ARM (build failures, etc) and
make life easier.
Best regards,
Stefan
=====================================================================
DENX Software Engineering GmbH, MD: Wolfgang Denk & Detlev Zundel
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: +49-8142-66989-0 Fax: +49-8142-66989-80 Email: office at denx.de
=====================================================================
next prev parent reply other threads:[~2009-07-15 15:10 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-14 13:47 [U-Boot] CONFIG_API, EABI and raise() Piotr Zięcik
2009-07-15 14:58 ` Mike Frysinger
2009-07-15 15:10 ` Stefan Roese [this message]
2009-07-15 15:12 ` Wolfgang Denk
2009-07-15 15:18 ` Stefan Roese
2009-07-15 15:15 ` Rafal Jaworowski
2009-07-15 16:09 ` Mike Frysinger
2009-07-16 8:37 ` Rafal Jaworowski
2009-07-16 8:46 ` Stefan Roese
2009-07-16 9:29 ` Rafal Jaworowski
2009-07-16 11:56 ` Wolfgang Denk
2009-07-17 14:18 ` Piotr Zięcik
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=200907151710.04262.sr@denx.de \
--to=sr@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 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.