From: Mike Frysinger <vapier@gentoo.org>
To: u-boot@lists.denx.de
Subject: [U-Boot] CONFIG_API, EABI and raise()
Date: Wed, 15 Jul 2009 12:09:30 -0400 [thread overview]
Message-ID: <200907151209.31131.vapier@gentoo.org> (raw)
In-Reply-To: <F7BA952D-DC19-42CA-832E-192DBA572CF9@semihalf.com>
On Wednesday 15 July 2009 11:15:46 Rafal Jaworowski wrote:
> On 2009-07-15, at 16:58, 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
>
> CONFIG_API worked fine for ARM builds some time ago, and this breakage
> seems like a recent development.
or, it still works fine if your toolchain doesnt suck and isnt broken
-mike
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 836 bytes
Desc: This is a digitally signed message part.
Url : http://lists.denx.de/pipermail/u-boot/attachments/20090715/1ca79592/attachment.pgp
next prev parent reply other threads:[~2009-07-15 16:09 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
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 [this message]
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=200907151209.31131.vapier@gentoo.org \
--to=vapier@gentoo.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