On 9/25/06, davidmott davidmott.com <davidmott davidmott.com> wrote:
>
> rpm -ivh package.rpm --force --nodeps
>
> The following error shows:
>
> cannot handle file 'libc.so.6' with TLS data
>
> I've tried a couple of suggestions on the net to
export
> LD_ASSUME_KERNEL=2.4.1 and 2.6.1 to no avail.
>
> Can someone please point me in the right direction?
Prebuilt binaries blowwwww! Seems it wants a libc without
threading
(TLS is thread local storage, which is nptl in LFS). The big
distros
usually install multiple versions of libc with different
threading
implementations (or none in this case). We only install one
libc with
nptl threading since we build all the packages ourselves.
Maybe it
just wants linuxthreads instead of nptl (which we also
don't do). The
suggestion found on the net can achieve this by telling the
dynamic
linker that you're using an older kernel than the minimum
necessary
for nptl.
Possibly I'm interpreting this wrong, but that seems to be
the case.
Do they distribute an SRPM (doubtful)?
If the error is coming from rpm, you can work around this
because you
don't actually need rpm to do what you want. Read on...
Let's trying working around rpm for a minute by just
extracting the
rpm contents and having a look at what it's trying to do.
Grab this
script:
http://w
ww.rpm.org/tools/scripts/rpm2cpio.sh
Install it in /usr/bin:
install -v -m755 rpm2cpio.sh /usr/bin/rpm2cpio
Install cpio from BLFS if you haven't already.
http://www.linuxfromscratch.org/blfs/view/svn/gen
eral/cpio.html
Make a scratch directory to unpack the rpm archive (which is
just a
cpio archive).
mkdir foo
cd foo
rpm2cpio package.rpm | cpio -idv
Now you can see all the binaries. If there's a .spec file,
read
through it. Maybe it'll have some information about
threaded binaries.
If this is a publically available rpm, could you place a
link to it?
--
Dan
--
http://linuxfromscratch.org/mailman/listinfo/blfs-suppo
rt
FAQ: http://
www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
|