Kbase 17227: Dynamic Linker Errors and What to Do
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/10/1998 |
|
Dynamic Linker Errors and What to Do
There are a times when installing Progress that we will flag such as
an error as dynamic linker: /usr/dlc/bin/_progres: libnsl.so.1 can't
open:killed. This error typically means that we are trying to find a
particular library on the operating system that we need to run the
installation. We may or may not need this library further on down the
line, but for this knowledgebase article, we'll focus on the
installation.
When this or any error associated with a library not being found is
flagged,we are typically searching the operating system for the
library and are not finding it. In the example, libnsl.so is a shared
object library on NCR 3.0's System V.4 that Progress is not finding.
We are merely reporting that the library is absent on the operating
system. This can often be percieved as a missing Progress library,
which is clearly not the case. It may be that your operating system
was not installed with all the libraries necessary, therefore you
may not always find the library in question.
The easiest way to identify whether or not a library exists on your
operating system is to cd to the /usr/lib directory and look for the
library in question.Often times a libray can be found on a test
machine that is not present on a your machine. You may
have a very similar library in your /usr/lib directory, and choose to
use that one instaed. Another popular approach is to establish a soft
link between the library we're looking for and one in the /usr/lib
directory. This can occur when the library exists in another directory
than /usr/lib. Some articles recommend copying the library into
/usr/lib, and this can be effective. Setting up a soft link between
one in /usr/lib and another directory may or may not get you through
the installation, but is not supported.
Basically Progress is looking for the exact library in the error
string, and any altering or linking of the library may very well work
but is not supported by Technical Support.If a library is not found
on your machine but is on another test machine, then verify the
EXACT version of the operating system. Subtle changes between releases
can result in the removal of libraries, and a Progress utility may
fail due to library's absence. Some os vendors may not recognize a
particular library as their own, but this again is due to their
looking at a different operarting system level.The absence of a c
compiler or a lesser version of the compiler may also be an area to
investigate.
OTHER USEFUL KNOWLEDGEBASE ARTICLES
13857 Dynamic linker error Unisys Unixware running _promtf
15145 Release Notes for Digital Unix - 7.3A
15530 Dynamic linker error libnet.so not found on Unixware
16690 Dynamic Linker: _progres - Can't open libnsl.so.1
15512 Cannot Open /usr/dglib/libstreamsocket.so.1
16128 DGUX 4.11 MU02 libnsl.so
15438 Dynamic Linker Problem on SGI - libnsl.so
NOTE: When verifying the existence of library on a test machine,you
may see a soft link from a similar library to the one we're looking
for, and this could be a potential problem. This means that the
library we're looking for does not really exist on the os and we're
linking it to a similar one, thus have not truly ported to that os
version.
Progress Software Technical Support Note # 17227