public inbox for glibc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "balkohen at gmail dot com" <sourceware-bugzilla@sourceware.org>
To: glibc-bugs@sources.redhat.com
Subject: [Bug ports/2660] ppc builds with --without-fp broken for glibc 2.4
Date: Mon, 15 May 2006 21:44:00 -0000 [thread overview]
Message-ID: <20060515214447.16713.qmail@sourceware.org> (raw)
In-Reply-To: <20060515211916.2660.raj.khem@gmail.com>
------- Additional Comments From balkohen at gmail dot com 2006-05-15 21:44 -------
Subject: Re: New: ppc builds with --without-fp broken for glibc 2.4
I reported something similar. Have a look at bug #2444. I've been
told that nofpu for long double is on Steven's list :)
--
http://sourceware.org/bugzilla/show_bug.cgi?id=2660
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
next prev parent reply other threads:[~2006-05-15 21:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-15 21:19 [Bug ports/2660] New: " raj dot khem at gmail dot com
2006-05-15 21:44 ` balkohen at gmail dot com [this message]
2006-05-16 14:08 ` [Bug ports/2660] " decimal at us dot ibm dot com
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=20060515214447.16713.qmail@sourceware.org \
--to=sourceware-bugzilla@sourceware.org \
--cc=glibc-bugs@sources.redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).