|
|
Posted by "Chris Boget" on 09/28/05 00:41
So I'm trying to install PHP with XML support. During configuration, I get
an error saying I need a newer version of libxml2. So I download
libxml2-2.6.22-1.i386.rpm and try to upgrade. No go as I get failed
dependancies. I then also download libxml2-devel-2.6.22-1.i386.rpm and
libxml2-python-2.6.22-1.i386.rpm to try to solve those dependencies. Nope,
still no go. I'm told that I need a newer version of libc. Specifically,
libc.so.6(GLIBC_2.3.4) is needed.
So I then download the newest version, glibc-2.3.90-12.i386.rpm. I also
download glibc-common-2.3.90-12.i386.rpm, glibc-devel-2.3.90-12.i386.rpm and
glibc-headers-2.3.90-12.i386.rpm. I try to upgrade all of those packages
hoping to finally get the ball rolling but no, still no go. In attempting
to upgrade glibc, I'm given the following error:
--------------------------------------------------
error: Failed dependencies:
shadow-utils < 2:4.0.3-20 conflicts with glibc-2.3.90-12
nscd < 2.3.3-52 conflicts with glibc-2.3.90-12
binutils < 2.15.94.0.2-1 conflicts with glibc-devel-2.3.90-12
tzdata >= 2003a is needed by glibc-common-2.3.90-12
--------------------------------------------------
I'm not sure what the conflict errors indicate. Do I need to uninstall
those packages? Because I don't quite understand those errors, I focus on
the problem I do understand. So I need to upgrade tzdata. Fine. I
download tzdata-2005m-2.noarch.rpm and try to upgrade it hoping finally I'll
be able to get some work done and install PHP. As a huge slap in the face,
I'm given the error
--------------------------------------------------
error: Failed dependencies:
glibc-common <= 2.3.2-63 conflicts with tzdata-2005m-2
--------------------------------------------------
No kidding! Really? </sar> So I can't install glibc-common without tzdata
and I can't install tzdata without glibc-common. What a very frustrating
and vicious circle I am in. And all I wanted to do was install PHP with xml
support.
*sigh*
So the next step I too was to run Redhat's up2date utility. It updated all
of
my installed packages, which included the packages I had been trying to
install manually. The entire process took a while but went without a hitch.
When it was finished, I ran up2date again to make sure there were no other
outstanding packages I needed to update and saw that there were none. So
I use rpm to query the currently installed libxml2 package and it's still
reporting
the old package - 2.5.4. It's also reporting the old glibc package as well.
Huh? So what happened during the up2date process? Where were all the
updated rpm packages installed, including the new glibc and libxml2?
I'm running a freshly installed Redhat 9, kernel version 2.4.20. Well, at
least
that's what rpm is reporting though I know the up2date utility (supposedly)
updated my kernel as well.
Has anyone else had problems similar to this? If so, how did you end up
resolving those problems? Alternately, if anyone has an idea on what I can
do next, it would be most appreciative. My limited experience with Linux
in general and RedHat in particular has me at the end of my rope.
thnx,
Chris
[Back to original message]
|