From: "Michel Dänzer" <michdaen@iiic.ethz.ch>
To: "Kevin B. Hendricks" <khendricks@ivey.uwo.ca>
Cc: Kaoru Fukui <k_fukui@highway.ne.jp>,
Keith Clayton <keith@claytons.org>,
linuxppc-dev@lists.linuxppc.org
Subject: Re: glibc 2.1 -> 2.2 gotchas?
Date: Sun, 26 Aug 2001 00:31:37 +0200 [thread overview]
Message-ID: <3B882749.346A0B39@iiic.ethz.ch> (raw)
In-Reply-To: 01082513443402.16172@localhost.localdomain
"Kevin B. Hendricks" wrote:
> > 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?
dpkg still isn't.
> What I recommend won't hurt and can certainly help flush older shared
> libraries out of memory.
The point is probably that in the Debian packages, the maintainer scripts take
care of the necessary steps, so the user doesn't have to.
--
Earthling Michel Dänzer (MrCooper) \ Debian GNU/Linux (powerpc) developer
CS student, Free Software enthusiast \ XFree86 and DRI project member
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-08-25 22:31 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
2001-08-25 18:06 ` Kaoru Fukui
2001-08-25 22:31 ` Michel Dänzer [this message]
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=3B882749.346A0B39@iiic.ethz.ch \
--to=michdaen@iiic.ethz.ch \
--cc=k_fukui@highway.ne.jp \
--cc=keith@claytons.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).