From: Alex Stewart <alex@foogod.com>
To: buildroot@busybox.net
Subject: [Buildroot] ARM EABI builds
Date: Thu, 28 Jun 2007 18:42:06 -0700 [thread overview]
Message-ID: <20070629014206.GL24520@foogod.com> (raw)
In-Reply-To: <20070628230131.GJ4096@aon.at>
Umm, I don't really know anything about Buildroot on ARM or EABI, but reading
through this discussion I did feel compelled to point out one thing I noticed:
On Fri, Jun 29, 2007 at 01:01:31AM +0200, Bernhard Fischer wrote:
> >work for libc, have you tried? (PS: Even if it did, bug #1406 is
> >probably the better fix, in particular as buildroot users might use its
>
> bug #1406 is completely crap. Let me cite:
> <quote>
> Reporter bjdooks
> Summary 0001403: printf and anything using vfprintf() hangs
> system
As noted in the "Summary" line, the bug you quoted is 1403, not 1406.
Bug 1406 does appear to have a clear description of the issue and a proposed
patch to fix it, so while I can't comment on the merit of the patch contents,
the bug report itself, at least, does not appear to be "completely crap"..
-alex
next prev parent reply other threads:[~2007-06-29 1:42 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-28 19:54 [Buildroot] ARM EABI builds Stuart Wood
2007-06-28 23:01 ` Bernhard Fischer
2007-06-29 1:00 ` Tom
2007-06-29 9:31 ` Ben Dooks
2007-06-29 1:42 ` Alex Stewart [this message]
2007-06-29 7:16 ` Bernhard Fischer
2007-06-29 9:26 ` Ben Dooks
-- strict thread matches above, loose matches on Subject: below --
2007-06-26 13:33 Ben Dooks
2007-06-26 21:19 ` Tom
2007-06-26 22:25 ` Ben Dooks
2007-06-27 8:19 ` Ben Dooks
2007-06-27 9:03 ` Konstantin Kletschke
2007-06-27 15:25 ` Ben Dooks
2007-06-27 17:44 ` Tom
2007-06-28 10:34 ` Ben Dooks
2007-06-28 19:13 ` Tom
2007-06-29 13:52 ` Ben Dooks
2007-06-28 22:50 ` Ulf Samuelsson
2007-06-28 23:57 ` Tom
2007-06-29 13:53 ` Ben Dooks
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=20070629014206.GL24520@foogod.com \
--to=alex@foogod.com \
--cc=buildroot@busybox.net \
/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.