From: Thorsten Kukuk <kukuk@suse.de>
To: libc-hacker@sources.redhat.com
Subject: Re: [PATCH] PPC enable Alitvec hardware, part 3 revision b
Date: Fri, 16 Jan 2004 07:30:00 -0000 [thread overview]
Message-ID: <20040116073039.GA4465@suse.de> (raw)
In-Reply-To: <40076CFD.2000007@redhat.com>
On Thu, Jan 15, Ulrich Drepper wrote:
> I've applied the patches. Responsibility for any breakage they might
> cause is still yours.
It does not compile on PPC nor PPC64:
version GLIBC_2.3.4 not defined for libc
Thorsten
--
Thorsten Kukuk http://www.suse.de/~kukuk/ kukuk@suse.de
SuSE Linux AG Maxfeldstr. 5 D-90409 Nuernberg
--------------------------------------------------------------------
Key fingerprint = A368 676B 5E1B 3E46 CFCE 2D97 F8FD 4E23 56C6 FB4B
next prev parent reply other threads:[~2004-01-16 7:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-15 2:36 Steve Munroe
2004-01-16 4:51 ` Ulrich Drepper
2004-01-16 7:30 ` Thorsten Kukuk [this message]
2004-01-16 16:39 Steve Munroe
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=20040116073039.GA4465@suse.de \
--to=kukuk@suse.de \
--cc=libc-hacker@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).