From: Keith Clayton <keith@claytons.org>
To: linuxppc-dev@lists.linuxppc.org
Subject: Re: glibc 2.1 -> 2.2 gotchas?
Date: 26 Aug 2001 07:52:02 -0700 [thread overview]
Message-ID: <998837522.12597.161.camel@yoda> (raw)
In-Reply-To: <01082511314308.15847@localhost.localdomain>
Thanks to all who responded to my query . . you guys are great.
I was gone all day yesterday and woke up to find my inbox full of great
info!
Looks like I've got some work cut out for me no matter which route I
head. Guess my labor day weekend will live up to its name ;)
Thanks again . . this gives me lots to chew on
Cheers,
Keith
On 25 Aug 2001 11:31:43 -0400, (null) wrote:
> Hi Keith,
>
> If you are using an RPM based distribution, please be careful. When I tried
> to do the upgrade manually awhile back I ran into trouble with many of the
> new rpms being usable in RPM 4 format only and not working under RPM 3.
>
> If I were you I would rebuild glibc 2.2.4 from a source rpm (from Franz) and
> run make check first just to make sure all is well. I would then focus on
> building RPM 4 and then try to convert your rpm database over from RPM 3 to
> RPM 4.o and then continue upgrading pieces.
>
> The other easy way to make this move is to simply upgrade to YDL 2, SuSE 7.1,
> Debian, Mandrake, etc. They are all glibc 2.2.X based and come with all of
> the other things that need to be upgraded since they are so old (Perl, etc).
>
> Upgrading them from glibc-2.2.1 to glibc 2.2.4 is easily done with rpm a few
> syncs and a restart.
>
> Hope this helps,
>
> Kevin
>
> On Saturday 25 August 2001 10:55, Keith Clayton wrote:
> > Hi all,
> >
> > I'm considering moving from glibc 2.1.3 to 2.2.4 Any known problems
> > with the move to 2.2, apps that break, etc.
> >
> > I'm hoping to minimize any surprises
> >
> >
> > Thanks
> > Keith
> >
> >
> > --
> > <><><><><><><><><><><><>
> > Keith Clayton
> > keith@claytons.org
> >
> > "If you don't trust me with your source code,
> > why should I trust you with my computer?"
> >
> > GPG key: http://home.pacbell.net/clay-ton/keith_public_key.html
> > http://www.keyserver.net
> >
> > GPG fingerprint: 33FF 1D80 4562 1600 4BAB 5018 BCB7 635C B0CC 99EE
> >
> >
--
<><><><><><><><><><><><>
Keith Clayton
keith@claytons.org
"If you don't trust me with your source code,
why should I trust you with my computer?"
GPG key: http://home.pacbell.net/clay-ton/keith_public_key.html
http://www.keyserver.net
GPG fingerprint: 33FF 1D80 4562 1600 4BAB 5018 BCB7 635C B0CC 99EE
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2001-08-26 14:52 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
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 [this message]
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=998837522.12597.161.camel@yoda \
--to=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 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).