From: Jan Nieuwenhuizen <janneke@gnu.org>
To: khendricks@ivey.uwo.ca
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Please Help!, Need to test glibc 2.1.3 with these additional patches under 2.3 kernels
Date: Wed, 16 Feb 2000 17:26:43 +0100 [thread overview]
Message-ID: <200002161626.RAA20871@appel.flower> (raw)
In-Reply-To: Your message of "Wed, 16 Feb 2000 08:18:57 EST." <00021608270801.00938@localhost.localdomain>
On Wednesday, 16 February 2000, Kevin Hendricks writes:
Will do.
Please send us the cvs command.
Greetings,
Jan.
--
Jan Nieuwenhuizen <janneke@gnu.org> | GNU LilyPond - The music typesetter
http://www.xs4all.nl/~jantien | http://www.lilypond.org
> Hi,
>
> glibc 2.1.3 is just about to go *final*
>
> BUT...If we want glibc 2.1.3 to compile out of the box under PPC under 2.3.XX
> kernels and actually work we really need people running 2.3.XX kernels to gra
+ b
> the source from glibc cvs and apply the following patch and test this thing
> asap and report some results.
>
> please note, glibc 2.1.3 is now very *stable* under 2.2.X kernels with lots o
+ f
> bug fixes and things.
>
> The key issue here is finding out whether glibc 2.1.3 will compile and run
> under 2.3.XX kernels.
>
> If you are willing to help, please let me know and give this a try.
>
> They will *not* hold up the release just for us, so your help and feedback wo
+ uld
> be greatly appreciated.
>
> Thanks,
>
> Kevin
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-02-16 16:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-16 13:18 Please Help!, Need to test glibc 2.1.3 with these additional patches under 2.3 kernels Kevin Hendricks
2000-02-16 16:26 ` Jan Nieuwenhuizen [this message]
2000-02-16 16:32 ` Kevin Hendricks
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=200002161626.RAA20871@appel.flower \
--to=janneke@gnu.org \
--cc=khendricks@ivey.uwo.ca \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).