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