From: Larry McVoy <lm@bitmover.com>
To: linuxppc-dev@lists.linuxppc.org
Subject: BK/glibc 2.1?
Date: Sat, 24 May 2003 13:23:10 -0700 [thread overview]
Message-ID: <200305242023.h4OKNAB19952@work.bitmover.com> (raw)
Hey, it's been a long time since we updated the machine on which we build BK
for Linux/PPC. We are currently dynamically linking against glibc 2.1. Is
that causing anyone any problems? I don't want to upgrade if I don't have to.
Thanks.
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
reply other threads:[~2003-05-24 20:23 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=200305242023.h4OKNAB19952@work.bitmover.com \
--to=lm@bitmover.com \
--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).