I have a (hopefully) quickie. Whenever I attempt to upgrade something using rpm -Uvh <package_name> i'm getting the following message:

Preparing... ########################################### [100%]
cannot handle file 'libc.so.6' with TLS data

Does anyone know how i can resolve this issue? I'm not totally clear on what it exactally means.

Go to FreshMeat and search for 'apt' or 'apt-get' or 'synaptic'. These are debian programs that are now available for Redhat, which go to a source on the Net and download the package and all required libraries etc... It's really easy to use and keeps you from having those problems.

I can get that to prevent future problems, but how do I fix the current issue?

I've found another issue, how do i fix this:

[root@linuxbox etc]# cd /lib
[root@linuxbox lib]# libc.so.6
Incorrectly built binary which accesses errno, h_errno or _res directly. Needs to be fixed.
GNU C Library stable release version 2.3.1, by Roland McGrath et al.
Copyright (C) 2003 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
Compiled by GNU CC version 3.2.1 20021207 (Red Hat Linux 8.0 3.2.1-2).
Compiled on a Linux 2.4.20-0.pp.6 system on 2003-01-03.
Available extensions:
GNU libio by Per Bothner
crypt add-on version 2.1 by Michael Glad and others
linuxthreads-0.10 by Xavier Leroy
BIND-8.2.3-T5B
libthread_db work sponsored by Alpha Processor Inc
NIS(YP)/NIS+ NSS modules 0.19 by Thorsten Kukuk
Thread-local storage support included.
Report bugs using the `glibcbug' script to <bugs@gnu.org>.


I believe they are both related, but if i try to install a new binary for glibc it gives me the original error.

Get a new glibc in tar.gz format not binary and build it again.

crimany, that's not an easy one to compile and install, i think i might just wait for RH8.1

Have you upgraded the libc? The one on the RH80 CD is 2.2.93 and does not show the errno/h_errno twist.

the problem is getting back to it, i've just finished downloading the redhat iso's so i'll burn those and try a reinstall

Hey,

I ran into this problem too when installing glibc from rawhide, I think it's because you don't have the latest version of rpm (also from rawhide).

Of course, since your rpm isn't current working, it's going to be a hassle. Here's how I fixed things up, it worked for me, hopefully it'll work for you. It requires that you have another computer that already has rpm 4.2 (and appropriate underlying packages) installed on it.

1. Copy the following files from the computer with the working rpm into the appropriate locations on your non-working box.

/bin/rpm
/usr/lib/librpm-4.2.so
/usr/lib/librpmdb-4.2.so
/usr/lib/librpmio-4.2.so
/usr/lib/libelf.so.1

Then, run
/sbin/ldconfig

Now, remove the old rpm database files:
rm /var/lib/rpm/__db.00*

And rebuild the database:
rpm --rebuilddb

rpm should now work (mostly) correctly. At least enough so that you can get the new rpm package files installed.

If rebuilding the database yields something like:

root@fermat:/> rpm -rebuilddb
rpmdb: unable to join the environment
error: db4 error(11) from dbenv->open: Resource temporarily unavailable
error: cannot open Packages index

try LD_ASSUME_KERNEL=2.2.5
before running rpm.

BTW, thanks to this thread (and to Tony Perrie) for these tips and to Jeff Johnson ... saved my life :-)