[Solved] rtld(rtld(GNU_HASH) dependency problem

[willyk]

New to this forum, have used linux ~40 years but have not progress far from newbie status, especially when it come to resolving dependency issues. I am currently runing a 64bit slackware 14.2 distribution. It only has the 64 bit libraries installed. At the top of dmsg I see:
Linux version 4.4.14 (root@hive64) (gcc version 5.3.0 (GCC) ) #2 SMP Fri Jun 24 13:38:27 CDT 2016

to check out glibc I ran the following:
bash-4.3# /lib64/libc.so.6
GNU C Library (GNU libc) stable release version 2.23, by Roland McGrath et al.
Copyright (C) 2016 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 5.3.0.
Available extensions:
crypt add-on version 2.1 by Michael Glad and others
GNU Libidn by Simon Josefsson
Native POSIX Threads Library by Ulrich Drepper et al
BIND-8.2.3-T5B
libc ABIs: UNIQUE IFUNC
For bug reporting instructions, please see:
<http://www.gnu.org/software/libc/bugs.html>.

I think the 'crypt add-on version 2.1' above means I have that add-on installed and from what I have read on-line this means I should have rtld(GNU_HASH) installed. However I downloaded the current RPM release of AOO 4.1.7
as a tar.gz, expand to a temp directory, cd into its RPMS directory and run install command:
bash-4.3# rpm -Uvih *.rpm
error: Failed dependencies:
rtld(GNU_HASH) is needed by openoffice-core04-4.1.7-9800.x86_64

so I am clearly doing something wrong. Suggestions?

[robleyd]

have used linux ~40 years

Perhaps you mean Unix/Xenix - Linus released Linux in 1991.

On Slack 14.2 64 bit you'll probably have better results using Slackware native installer pkgtool. RPM is dependency hell
Download the required language RPM tarball and extract it into a suitable directory. cd into that directory and you'll see the following directory structure:

Code: Select all

drwxr-xr-x 3 huntsman users 4096 Sep 16 06:59 RPMS
drwxr-xr-x 2 huntsman users 4096 Sep 16 06:59 licenses
drwxr-xr-x 2 huntsman users 4096 Sep 16 06:59 readmes

Then

Code: Select all

$ cd RPMS

You'll find (nearly) all the installation RPMs there, and a sub-directory desktop-integration that contains the desktop integration packages for various environments

Code: Select all

$ ls -l desktop-integration
total 4436
-rw-r--r-- 1 huntsman users 1093087 Aug 21 00:07 openoffice4.1.7-freedesktop-menus-4.1.7-9800.noarch.rpm
-rw-r--r-- 1 huntsman users 1109222 Aug 21 00:08 openoffice4.1.7-mandriva-menus-4.1.7-9800.noarch.rpm
-rw-r--r-- 1 huntsman users 1164709 Aug 21 00:07 openoffice4.1.7-redhat-menus-4.1.7-9800.noarch.rpm
-rw-r--r-- 1 huntsman users 1168622 Aug 21 00:08 openoffice4.1.7-suse-menus-4.1.7-9800.noarch.rpm

You'll probably want the freedesktop version, so still from the directory where all the RPMs are

Code: Select all

$ cp desktop-integration/openoffice4.1.7-freedesktop-menus-4.1.7-9800.noarch.rpm .

Note the trailing period. Now you have all the needed RPMs in one directory. Next convert the RPMs to a format pkgtool can work with. This will take a few minutes.

Code: Select all

$ rpm2tgz *.rpm

You can now remove all the RPM files

Code: Select all

$ rm *.rpm

And finally as root do the actual install via pkgtool - you may invoke it via sudo, or use su or log in as root, whichever you normally do.

pkgtool is just a front end to installpkg, upgradepkg, removepkg and a couple of other tools; you can also use those tools from the command line. There are man pages for all.

[willyk]

thank you robleyd

Your instructions worked fine and I have OpenOffice 4.1.7 installed on my Slackware 14.2 system.
I don't know how to do it, but this should be marked as solved.

Per your comment about my experience, I did say ~40 years, but it appears 25 would be more accurate.
I still have CD distributions of Slackware 3.6 and Redhat 5.2 which ran nicely on an Intel 386 system.
In the 1980s I would have been using CPM on a DEC Robin system.

[robleyd]

Hagar has done it - but for future reference...

How to tag a topic as solved.

In your first post, click the Edit button. Go to the subject line and add [Solved] at the beginning of the subject.

Then select the green tick as the Post icon (just below the subject line). Preview if you wish to see how it looks.
Finally, hit Submit - done!