From: Peter Korsgaard <jacmet@uclibc.org>
To: buildroot@busybox.net
Subject: [Buildroot] Is this a bug? libm in uclibc 0.9.32
Date: Sun, 26 Jun 2011 23:07:57 +0200 [thread overview]
Message-ID: <87ei2g713m.fsf@macbook.be.48ers.dk> (raw)
In-Reply-To: <201106242100.45976.vapier@gentoo.org> (Mike Frysinger's message of "Fri, 24 Jun 2011 21:00:43 -0400")
>>>>> "Mike" == Mike Frysinger <vapier@gentoo.org> writes:
Mike> On Friday, June 24, 2011 17:12:30 raymond zhao wrote:
Mike> please dont top post
>> I agree.
>> But does anyone have a better solution to fix this bug?
Mike> i pointed at the correct solution. it's simply a matter of implementing it.
Mike> also, this is a uClibc issue, not buildroot, so it probably
Mike> should be taken up there. like a bug filed in their tracker.
Indeed. Please report this issue to the uClibc devs.
--
Bye, Peter Korsgaard
next prev parent reply other threads:[~2011-06-26 21:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-24 19:52 [Buildroot] Is this a bug? libm in uclibc 0.9.32 raymond zhao
2011-06-24 20:50 ` Mike Frysinger
2011-06-24 21:12 ` raymond zhao
2011-06-25 1:00 ` Mike Frysinger
2011-06-26 21:07 ` Peter Korsgaard [this message]
2011-06-27 12:43 ` raymond zhao
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=87ei2g713m.fsf@macbook.be.48ers.dk \
--to=jacmet@uclibc.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox