From: Keith Clayton <kclayton@jps.net>
To: linuxppc-user@lists.linuxppc.org, linuxppc-dev@lists.linuxppc.org
Subject: glibc 2.1?
Date: Tue, 26 Jan 1999 15:55:07 -0800 [thread overview]
Message-ID: <36AE55DB.96CC94ED@jps.net> (raw)
My understanding is that one of the holdups for r5 is glibc2.1 Anyone
privy to glibc2 development? I've been putting on hold any non-critical
upgrades/compilations b/c I'd like to link against glibc2 and not have
to visit the whole libc5, glibc2, fix0961212 adventure. I haven't seen
anything mentioned on the lists but I've seen a glibc2.0.1xx rpm on
ftp.linuxppc.org.
TIA,
Keith Clayton
kclayton@jps.net
[[ This message was sent via the linuxppc-dev mailing list. Replies are ]]
[[ not forced back to the list, so be sure to Cc linuxppc-dev if your ]]
[[ reply is of general interest. To unsubscribe from linuxppc-dev, send ]]
[[ the message 'unsubscribe' to linuxppc-dev-request@lists.linuxppc.org ]]
reply other threads:[~1999-01-26 23:55 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=36AE55DB.96CC94ED@jps.net \
--to=kclayton@jps.net \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=linuxppc-user@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).