From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [RFC] glibc fails with -march=i686 or pentiumpro or pentium3
Date: Sat, 08 Nov 2008 22:45:29 -0500 [thread overview]
Message-ID: <20081109034529.GA14320@denix.org> (raw)
In-Reply-To: <c384c5ea0811081134t2119fb80r1e316c8e2dec883b@mail.gmail.com>
On Sat, Nov 08, 2008 at 08:34:26PM +0100, Leon Woestenberg wrote:
> Hello,
>
> On Fri, Nov 7, 2008 at 12:10 AM, Denys Dmytriyenko <denis@denix.org> wrote:
> > On Mon, Nov 03, 2008 at 03:22:04PM -0500, Denys Dmytriyenko wrote:
> >> glibc fails with -march=i686 or pentiumpro or pentium3 - it's a known issue
> > Any comments for the patch? Can somebody please push it in? Thanks.
> >
>
> In the bug tracker Khem Raj confirms he committed this:
> http://bugs.openembedded.net/show_bug.cgi?id=4798
>
> Could you verify it works and close the bug?
>
> Thanks both to Khem and you!
Leon,
It has already been done. Thanks.
--
Denys
prev parent reply other threads:[~2008-11-09 4:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-03 20:22 [RFC] glibc fails with -march=i686 or pentiumpro or pentium3 Denys Dmytriyenko
2008-11-06 23:10 ` Denys Dmytriyenko
2008-11-08 19:34 ` Leon Woestenberg
2008-11-09 3:45 ` Denys Dmytriyenko [this message]
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=20081109034529.GA14320@denix.org \
--to=denis@denix.org \
--cc=openembedded-devel@lists.openembedded.org \
/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