ke4nt1
Group: Members
Posts: 2329
Joined: Oct. 2003 |
 |
Posted: Jan. 07 2005,00:59 |
 |
Could those be only symlinks in your /opt/screen/lib dir?
Frequently, libs ending in .so.0 are only symlinks, pointing
to some other location..
All your other listed libs have numbers greater than zero,
and they are all found, which is why I thought to ask..
I usually see these files/symlinks grouped.
libelf.so.0 => libelf.so.0.6.4
libutempter.so.0 => libutempter.so.0.5
And yes.., you are correct..
Depending on how an application was compiled,
or even if the author went to the effort of allowing alt paths,
some apps simply will not run without seeing files in certain places.
This is no fault of the extension, the OS, or the libs,
and can often be worked around by setting a more proper
path for your design in the configure file before compile-time.
Here is some more data, from a "sun" perspective,
on how it can work for you, against you, not at all,
or even as a necessity to an app even running..
http://www.visi.com/~barr/ldpath.html
Again, if you recompile, you can usually set the lib path to your wishes..
I've also seen where a path statement is forced by editing the global path to include checking the LD_LIBRARY_PATH first,
like PATH=$LD_LIBRARY_PATH,$PATH
Which forces a search for libs to check thru your LD_LIBRARY_PATH variable BEFORE your usual path,
which may prevent the error - that it did not find it in the
suggested or usual compiled-in path location.
73
ke4nt
|
.
DSL Market ,
Great VPS hosting provided by Tektonic
