04-15-2018
libhello.so has to be in the LD_LIBIRARY_PATH variable for ldd to find it. You should NOT put personal directories in the path.
This User Gave Thanks to jim mcnamara For This Post:
10 More Discussions You Might Find Interesting
1. Programming
Hello everybody,
I am having major problems at the moment with shared libraries and I have to little knowledge of them to solve them. So please, please help me :)
Ok this is the problem:
I have a library A, which uses B and C, and C uses again D.
If I try to run A as plugin in apache,... (0 Replies)
Discussion started by: Micky
0 Replies
2. Programming
I am compiling code which produces .a and .la libraries. How can I produce .so libraries? I know that gcc -shared does but how? (2 Replies)
Discussion started by: thalex
2 Replies
3. UNIX for Dummies Questions & Answers
I have a doubt about the shared libraries. Where do you set the path for the shared libaries, for the dynamic loader to locate. Any suggestion would be of great help. thanks (3 Replies)
Discussion started by: ramkumar_gr
3 Replies
4. Linux
How do i make a library shared
say i have a library a.so which i have just compiled.
I want to make it shared how do i make it
Next Queation is what is the difference between a.so.0 a.so.1 a.so.2 & a.so :rolleyes: (1 Reply)
Discussion started by: wojtyla
1 Replies
5. Programming
anybody knows how to view loaded shared libraries by running processes in linux enviornment? any command or tool ?
thanks a lot (3 Replies)
Discussion started by: princelinux
3 Replies
6. UNIX for Advanced & Expert Users
Hi,
I am trying to create a shared library from a .c file using
gcc -c -fpic -I/usr/local/include Chksum.C -o Chksum.o
gcc -shared -o libtclcksum.so Chksum.o
when i try to load this shared library libtclcksum.so in tclsh
% load libtclcksum.so
I get the following error:
couldn't load... (1 Reply)
Discussion started by: archana485
1 Replies
7. UNIX for Advanced & Expert Users
Hello,
I'm wondering what is the naming conventions for *.so shared libraries in linux. For example, a library in /lib, say libcrypt-2.7.so has a symbolic link called libcrypt.so.1 pointing to it, yet libncursesw.so.5.6 has a symbolic link called libncursesw.so.5 pointing to it. What is the... (2 Replies)
Discussion started by: neked
2 Replies
8. AIX
Hi,
I have a problem about loaded shared libraries. I'm issuing ‘procldd' for a process and AIX shows me the loaded shared libraries. I'm collecting these libraries and counting their size. They were 350MB. After this, I'm issuing ‘ps vx' and I'm seeing that the process takes 130MB from AIX's... (1 Reply)
Discussion started by: jhatzics
1 Replies
9. Red Hat
hi,
while running the below query it gives the shared libraries prmblem,
$ cd /oracle/app/product/fmw/asinst_1/bin/
$ ./opmnctl status
/oracle/app/product/fmw/Oracle_IDM1/opmn/bin/opmn: error while loading shared libraries: libgcc_s.so.1: cannot open shared object file: Permission... (0 Replies)
Discussion started by: rahulsword
0 Replies
10. Solaris
Does anyone know whether it is possible to make self contained shared libraries ? (.so files). If so, what is the way to do it ?
---------- Post updated at 08:03 AM ---------- Previous update was at 07:56 AM ----------
On Solaris that is. (6 Replies)
Discussion started by: lkb
6 Replies
LDD(1) Linux Programmer's Manual LDD(1)
NAME
ldd - print shared library dependencies
SYNOPSIS
ldd [OPTION]... FILE...
DESCRIPTION
ldd prints the shared libraries required by each program or shared library specified on the command line.
Security
In the usual case, ldd invokes the standard dynamic linker (see ld.so(8)) with the LD_TRACE_LOADED_OBJECTS environment variable set to 1,
which causes the linker to display the library dependencies. Be aware, however, that in some circumstances, some versions of ldd may
attempt to obtain the dependency information by directly executing the program. Thus, you should never employ ldd on an untrusted exe-
cutable, since this may result in the execution of arbitrary code. A safer alternative when dealing with untrusted executables is:
$ objdump -p /path/to/program | grep NEEDED
OPTIONS
--version
Print the version number of ldd.
-v --verbose
Print all information, including, for example, symbol versioning information.
-u --unused
Print unused direct dependencies. (Since glibc 2.3.4.)
-d --data-relocs
Perform relocations and report any missing objects (ELF only).
-r --function-relocs
Perform relocations for both data objects and functions, and report any missing objects or functions (ELF only).
--help Usage information.
NOTES
The standard version of ldd comes with glibc2. Libc5 came with an older version, still present on some systems. The long options are not
supported by the libc5 version. On the other hand, the glibc2 version does not support -V and only has the equivalent --version.
The libc5 version of this program will use the name of a library given on the command line as-is when it contains a '/'; otherwise it
searches for the library in the standard locations. To run it on a shared library in the current directory, prefix the name with "./".
BUGS
ldd does not work on a.out shared libraries.
ldd does not work with some extremely old a.out programs which were built before ldd support was added to the compiler releases. If you
use ldd on one of these programs, the program will attempt to run with argc = 0 and the results will be unpredictable.
SEE ALSO
ld.so(8), ldconfig(8)
COLOPHON
This page is part of release 3.53 of the Linux man-pages project. A description of the project, and information about reporting bugs, can
be found at http://www.kernel.org/doc/man-pages/.
2012-07-16 LDD(1)