From: "Kevin B. Hendricks" <khendricks@ivey.uwo.ca>
To: Kaoru Fukui <k_fukui@highway.ne.jp>
Cc: Keith Clayton <keith@claytons.org>, linuxppc-dev@lists.linuxppc.org
Subject: Re: glibc 2.1 -> 2.2 gotchas?
Date: Sat, 25 Aug 2001 13:44:34 -0400 [thread overview]
Message-ID: <01082513443402.16172@localhost.localdomain> (raw)
In-Reply-To: <20010826005515.Postino-022357@smtp01.highway.ne.jp>
Hi
> it's no needs.
> Please read glibc's FAQ which has glibc source
>
> I have here also at
>
> ftp://ftp.linuxppc.org/users/kfukui/glibc-2.2.x-room/RPMS/FAQ.glibc-2.2.3
All I saw here was for installing after building from source code. I did not
see anything about installing using a package manager.
Perhaps my use of "ldconfig -v; sync; sync; shutdown -r now" comes from the
days when rpm was not always staticaly linked with libc?
What I recommend won't hurt and can certainly help flush older shared
libraries out of memory.
It is of-course Keith's choice but I still recommend it.
Kevin
(ps. you might want to check out RedHat's instructions for using rpm to
upgrade glibc, that used to be on their site. That is what I based my
procedure on a long time ago (around mklinux rel 1).
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-08-25 17:44 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-25 14:55 glibc 2.1 -> 2.2 gotchas? Keith Clayton
2001-08-25 15:31 ` Kevin B. Hendricks
2001-08-25 15:35 ` Michel Dänzer
2001-08-25 15:42 ` Kevin B. Hendricks
2001-08-25 15:55 ` Kaoru Fukui
2001-08-25 17:44 ` Kevin B. Hendricks [this message]
2001-08-25 18:06 ` Kaoru Fukui
2001-08-25 22:31 ` Michel Dänzer
2001-08-25 22:42 ` Tom Rini
2001-08-25 22:54 ` Daniel Jacobowitz
2001-08-26 4:36 ` Tom Rini
2001-08-29 21:08 ` Daniel Jacobowitz
2001-08-26 14:52 ` Keith Clayton
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=01082513443402.16172@localhost.localdomain \
--to=khendricks@ivey.uwo.ca \
--cc=k_fukui@highway.ne.jp \
--cc=keith@claytons.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.