SEO

Dear Experts,


To install some software, I need to upgrade the package,
glic, to a newer version.


I downloaded the newer version, and compiled it.
Interestingly, it took over ONE HOUR to compile.

And, it also produced MANY files.

/usr/src/redhat/RPMS/i386/glibc-2.3.2-95.27.i386.rpm
/usr/src/redhat/RPMS/i386/glibc-devel-2.3.2-95.27.i386.rpm
/usr/src/redhat/RPMS/i386/glibc-headers-2.3.2-95.27.i386.rpm
/usr/src/redhat/RPMS/i386/glibc-profile-2.3.2-95.27.i386.rpm
/usr/src/redhat/RPMS/i386/glibc-common-2.3.2-95.27.i386.rpm
/usr/src/redhat/RPMS/i386/nscd-2.3.2-95.27.i386.rpm
/usr/src/redhat/RPMS/i386/glibc-debug-2.3.2-95.27.i386.rpm
/usr/src/redhat/RPMS/i386/glibc-utils-2.3.2-95.27.i386.rpm
/usr/src/redhat/RPMS/i386/glibc-debuginfo-2.3.2-95.27.i386.rpm
/usr/src/redhat/RPMS/i386/glibc-debuginfo-common-2.3.2-95.27.i386.rpm



When I test to see if I can install one of them, I get:

rpm -Uvh --test /usr/src/redhat/RPMS/i386/glibc-2.3.2-95.27.i386.rpm

error: Failed dependencies:
glibc-common = 2.3.2-95.27 is needed by glibc-2.3.2-95.27
glibc = 2.3.2-95.20 is needed by (installed) glibc-
utils-2.3.2-95.20



When I test to see if I can install all of them, I get Failed
dependencies again:

rpm -Uvh --test glibc-2.3.2-95.27.i386.rpm glibc-
common-2.3.2-95.27.i386.rpm glibc-
debug-2.3.2-95.27.i386.rpm glibc-
debuginfo-2.3.2-95.27.i386.rpm glibc-debuginfo-
common-2.3.2-95.27.i386.rpm glibc-
devel-2.3.2-95.27.i386.rpm glibc-
headers-2.3.2-95.27.i386.rpm glibc-
profile-2.3.2-95.27.i386.rpm glibc-
utils-2.3.2-95.27.i386.rpm nscd-2.3.2-95.27.i386.rpm

error: Failed dependencies:
glibc-devel = 2.3.2-95.20 is needed by (installed) nptl-
devel-2.3.2-95.20


How can I install all of them cleanly????

I'm using Redhat AS 3.2.


Thanks a lot!

Is it possible to uninstall all these GLIBC, and then reinstall?

linuxquestion@yahoo.com wrote:
> Dear Experts,
>
>
> To install some software, I need to upgrade the package, glic, to a newer
> version.
>
>
> I downloaded the newer version, and compiled it. Interestingly, it took
> over ONE HOUR to compile.
>
> And, it also produced MANY files.
>
> /usr/src/redhat/RPMS/i386/glibc-2.3.2-95.27.i386.rpm
> /usr/src/redhat/RPMS/i386/glibc-devel-2.3.2-95.27.i386.rpm
> /usr/src/redhat/RPMS/i386/glibc-headers-2.3.2-95.27.i386.rpm
> /usr/src/redhat/RPMS/i386/glibc-profile-2.3.2-95.27.i386.rpm
> /usr/src/redhat/RPMS/i386/glibc-common-2.3.2-95.27.i386.rpm
> /usr/src/redhat/RPMS/i386/nscd-2.3.2-95.27.i386.rpm
> /usr/src/redhat/RPMS/i386/glibc-debug-2.3.2-95.27.i386.rpm
> /usr/src/redhat/RPMS/i386/glibc-utils-2.3.2-95.27.i386.rpm
> /usr/src/redhat/RPMS/i386/glibc-debuginfo-2.3.2-95.27.i386.rpm
> /usr/src/redhat/RPMS/i386/glibc-debuginfo-common-2.3.2-95.27.i386.rpm
>
>
>
> When I test to see if I can install one of them, I get:
>
> rpm -Uvh --test /usr/src/redhat/RPMS/i386/glibc-2.3.2-95.27.i386.rpm

cd /usr/src/redhat/RPMS/i386
rpm -Uvh --test glibc-2.3.2-95.27.i386.rpm glibc-*-2.3.2-95.27.i386.rpm \
nscd-*-2.3.2-95.27-i386.rpm nptl-devel-2.3.2-95.27.i386.rpm

You will have to keep going until you get them all. If you are running RHEL3
already, your subscription entitles you to all updates, so just run up2date.

> error: Failed dependencies: glibc-common = 2.3.2-95.27 is needed by
> glibc-2.3.2-95.27 glibc = 2.3.2-95.20 is needed by (installed) glibc-
> utils-2.3.2-95.20
>
>
>
> When I test to see if I can install all of them, I get Failed
> dependencies again:
>
> rpm -Uvh --test glibc-2.3.2-95.27.i386.rpm glibc-
> common-2.3.2-95.27.i386.rpm glibc- debug-2.3.2-95.27.i386.rpm
> glibc- debuginfo-2.3.2-95.27.i386.rpm glibc-debuginfo-
> common-2.3.2-95.27.i386.rpm glibc- devel-2.3.2-95.27.i386.rpm
> glibc- headers-2.3.2-95.27.i386.rpm glibc-
> profile-2.3.2-95.27.i386.rpm glibc- utils-2.3.2-95.27.i386.rpm
> nscd-2.3.2-95.27.i386.rpm
>
> error: Failed dependencies: glibc-devel = 2.3.2-95.20 is needed by
> (installed) nptl- devel-2.3.2-95.20
>
>
> How can I install all of them cleanly????
>
> I'm using Redhat AS 3.2.
>
Why not just upgrade (with up2date) to RHEL 3.9 we are up to now? They are
up to glibc-*-2.3.2-95.50
>
> Thanks a lot!
>


--
.~. Jean-David Beyer Registered Linux User 85642.
/V\ PGP-Key: 9A2FC99A Registered Machine 241939.
/( )\ Shrewsbury, New Jersey http://counter.li.org
^^-^^ 20:30:01 up 6 days, 1:30, 3 users, load average: 4.63, 4.40, 4.20

linuxquestion@yahoo.com wrote:
> Is it possible to uninstall all these GLIBC, and then reinstall?

No, if you uninstall glibc, you break your system completely.

rpm -Uvh /usr/src/redhat/RPMS/i386/glibc*.rpm /usr/src/redhat/RPMS/i386/nscd*

--

//Aho

In linux.redhat.rpm linuxquestion@yahoo.com wrote:
>
> To install some software, I need to upgrade the package,
> glic, to a newer version.

Upgrading glibc "in blind" has a potential of totally breaking
your system. Quite possibly you have a software which depends
on an older glibc version. It may work as glibc provides
versioned symbols; that depends how other programs will cooperate
with it.

If you are not sure what you are doing you should keep up with
glibc from updates to your distro. Rather recompile that
"some software".

> I downloaded the newer version, and compiled it.
> Interestingly, it took over ONE HOUR to compile.

This is a quite big thing.

> And, it also produced MANY files.

> /usr/src/redhat/RPMS/i386/glibc-2.3.2-95.27.i386.rpm
and so on ....

You should NEVER compile some extra packages as root.
Check in docs how ~/.rpmmacros may help with that.
http://docs.fedoraproject.org/drafts/rpm-guide-en/
You want to change %_topdir.

> When I test to see if I can install one of them,

You cannot.

> I get:
>
> rpm -Uvh --test /usr/src/redhat/RPMS/i386/glibc-2.3.2-95.27.i386.rpm
>
> error: Failed dependencies:

You should be really glad or otherwise you will be restoring
now from backups. All of that has to be done in one transaction.

> error: Failed dependencies:
> glibc-devel = 2.3.2-95.20 is needed by (installed) nptl-
> devel-2.3.2-95.20
>
>
> How can I install all of them cleanly????

You obviously need a newer ntpl too (and possibly other things).

> I'm using Redhat AS 3.2.

Then you have a support contract. If you will replace glibc
by something self-compiled then most likely your contract
will became invalid.

It surely would be healthier to update to a newer RHEL.

Michal

Michal Jaegermann wrote:
> In linux.redhat.rpm linuxquestion@yahoo.com wrote:
>
>> I'm using Redhat AS 3.2.
>
> Then you have a support contract. If you will replace glibc by something
> self-compiled then most likely your contract will became invalid.
>
> It surely would be healthier to update to a newer RHEL.
>
Possibly, but I believe Red Hat will support RHEL3 for another three years
or so. So he should just run up2date to get the newer versions. It may take
some time since they are up to RHEL 3.9 already (although they do not call
these things by dot numbers).


--
.~. Jean-David Beyer Registered Linux User 85642.
/V\ PGP-Key: 9A2FC99A Registered Machine 241939.
/( )\ Shrewsbury, New Jersey http://counter.li.org
^^-^^ 16:35:01 up 6 days, 21:35, 3 users, load average: 4.02, 4.10, 4.16