Running tru64 unix applications under alpha linux

From: Edward J. Brash <brash_at_uregina.ca>
Date: Fri, 28 Sep 2001 11:56:18 -0600

Hi,

I have an application which has been compiled on an alpha running Tru64 unix,
and of course uses shared libraries. Here is a list of the libraries that I
believe that it needs:

regie5:$ odump -Dl ./hdgeant++


                        ***LIBRARY LIST SECTION***
        Name Time-Stamp CheckSum Flags Version
./hdgeant++:
        libXm.so May 27 10:30:24 1999 0xa55f6d32 0 motif1.2
        libSM.so Apr 2 00:55:43 1999 0xb64c7082 0
        libICE.so Apr 2 00:55:34 1999 0x1199be32 0
        libXt.so Nov 3 16:24:49 1999 0x4efbddbb 0
        libX11.so Apr 2 00:46:46 1999 0xf86afbad 0
        libm.so Apr 12 10:14:17 1999 0xf29b0962 0 osf.1
        libdnet_stub.so Apr 12 10:18:15 1999 0x9408a36b 0 osf.1
        libXmu.so Apr 2 00:58:34 1999 0x3bf3a33d 0
        libshpf.so Nov 3 08:10:53 1998 0x6f383991 0 t009
        libUfor.so Mar 29 20:35:16 2000 0xdf165667 0
        libfor.so Mar 29 20:35:16 2000 0xcfae3688 0
        libFutil.so Mar 29 20:35:16 2000 0xa19d96f9 0
        libots.so Apr 12 10:16:38 1999 0x0876eb23 0
        libm_c32.so Nov 15 08:45:32 1999 0xd20bc368 0 osf.1
        libc.so Nov 1 15:54:34 1999 0xb1d8d691 0 osf.1

All of these libraries are either located in /usr/shlib, or are softlinked from
/usr/shlib

I would like to be able to run this application on an alpha running RH6.2. Of
course, if I do nothing, and try to run it, it responds with

[brash_at_space36 HDGeant]$ ./hdgeant++
bash: ./hdgeant++: No such file or directory

and I presume it can't find one or more of these libraries, since /usr/shlib
does not exist.

So, I made a directory on the AlphaLinux machine called /usr/shlib, and then
copied every library from /usr/shlib on the Tru64 machine into it. Of course,
any libraries which were actually softlinks are no longer so on the AlphaLinux
machine, rather they are just the actual *.so file itself.

Then, I added /usr/shlib to /etc/ld.so.conf, and did /sbin/ldconfig as root. I
thought that this should be enough to tell the system to go look in /usr/shlib
if it needs shared libraries.

However, I still get the above message and the executable will not run. I know
that I can compile the original application statically, but I would rather not
do that in this case for other technical reasons. I thought that this should
work. What am I missing?

Cheers,
Ed.


Received on Fri Sep 28 2001 - 17:57:00 NZST

This archive was generated by hypermail 2.4.0 : Wed Nov 08 2023 - 11:53:42 NZDT