HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Hours:
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
cancel
Showing results for 
Search instead for 
Did you mean: 

link lib issues

 
Michael Murphy_2
Frequent Advisor

link lib issues

I am running an old proprietary app and getting and error during runtime: /usr/lib/dld.sl: Can't open shared library: ../../libtddd.sl
/usr/lib/dld.sl: No such file or directory

A couple questions:
- this has many libs associated with it - is there a way to find which exec/lib references this?
- is there a way to FORCE this to look for this lib in a different place?

I get the error above when trying to run an executable - i don't see any reference to this lib in the makefile for the exec so I assume one of the libs it links in has a reference - i tried using chatr on the exec but do not see any reference. Thanks
2 REPLIES
Rita C Workman
Honored Contributor

Re: link lib issues

If you know where that file is....maybe you could reference the path in the /etc/SHLIB_PATH file.

Just a quick thought,
Rita

Re: link lib issues

Where did that shlib go?

>this has many libs associated with it - is there a way to find which exec/lib references this?

(What is "this" and "it", the app or the shlib? It is better to repeat the name.)

If you want to see what shlibs the application uses, use "chatr app". You may have to use chatr(1) on all of your apps to find them all.

>is there a way to FORCE this to look for this lib in a different place?

If the application is linked correctly, you can export SHLIB_PATH to point to the proper directories.

>I don't see any reference to this lib in the makefile for the exec so I assume one of the libs it links in has a reference

You can also use chatr(1) on shlibs.
Or you can use ldd(1) on your executable and it will list all shlibs, until it finds one missing.

>Rita: maybe you could reference the path in the /etc/SHLIB_PATH file.

It is probably easier to export SHLIB_PATH in an appropriate script, than to try to figure out which application rates high enough to be put into SHLIB_PATH.