09-04-2009
How to obtain list of object files in a shared (dynamic) library?
How can I simply obtain a list of the object files in a shared (dynamic) library.
I am looking for the equivalent of "ar -t <lib>" for archived (static) libraries.
Thanks in advance.
---------- Post updated at 01:47 PM ---------- Previous update was at 12:16 PM ----------
The closest I have been able to come is something like:
nm -An <lib> | grep FILE
10 More Discussions You Might Find Interesting
1. Linux
hi
how can i load dynamic or shared library in linux kernel modules .
mtaghiloo@yahoo.com (0 Replies)
Discussion started by: mtaghiloo
0 Replies
2. Linux
Hi All,
I created the share object file using
gcc -shared -fpic mypp.cpp -o myp.so
but, pls tell me how to link this .so file to my client program.
Thanks (0 Replies)
Discussion started by: sarwan
0 Replies
3. AIX
Hi,
When using shared objects on AIX 4.3 i am getting runtime problems.
I have a small sample program which links to a shared object libray, oracle and system related libraries.
At runtime it fails (gives segmentation fault and coredump ) in one proc file when executing login statement.
But... (0 Replies)
Discussion started by: suman_jakkula
0 Replies
4. Shell Programming and Scripting
Hi,
I have created a shared object (abc.so) which has a function sum(int a, int b).
Is there any way to load the "abc.so" and use the sum function using shell script..
thanks in advance (2 Replies)
Discussion started by: yhacks
2 Replies
5. Shell Programming and Scripting
Hi:
I have a library that it only offers Makefile for building static library. It built libxxx.a file. How do I in any way build a shared library? (either changin the Makefile or direct script or command to build shared library)
Thanks. (1 Reply)
Discussion started by: cpthk
1 Replies
6. UNIX for Dummies Questions & Answers
I am having a major problem. Most of the commands that i am running on my centos 5 system is giving the error of type:
<dynamic shared library file>:open failed: No such file or directory
For example:
libgcc_s.so.1: open failed: No such file or directory
How can i solve this? (6 Replies)
Discussion started by: proactiveaditya
6 Replies
7. Red Hat
Hi,
I would like to create a shared object ( .so).
This shared object
1. uses the functions from a library.
2. Also it should be able to use the global variable in an app
To achieve this what should I do ? 1) To use the functions in the library should I give the -ld option while... (1 Reply)
Discussion started by: rvan
1 Replies
8. Programming
Hello,
I am new to programming shared objects and I was hoping someone could tell me if what I want to do is possible, or else lead me in the right direction.
I have a main program that contains an abstract base class. I also have a subclass that I'm compiling as a shared object. The subclass... (13 Replies)
Discussion started by: dorik
13 Replies
9. Programming
Hello.
I am new to this forum and I would like to ask for advice about low level POSIX programming.
I have to implement a POSIX compliant C shared library.
A file will have some variables and the shared library will have some functions which need those variables.
There is one special... (5 Replies)
Discussion started by: iamjag
5 Replies
10. AIX
I'm trying to install libiconv to AIX 7.1 from an rpm off of the perzl site. The rpm appears to install but I get this error message.
add shr4.o shared members from /usr/lib/libiconv.a to /opt/freeware/lib/libiconv.a
add shr.o shared members from /usr/lib/libiconv.a to ... (5 Replies)
Discussion started by: kneemoe
5 Replies
ldd_ia(1) General Commands Manual ldd_ia(1)
NAME
ldd_ia: ldd - list dynamic dependencies of executable files or shared libraries on Integrity systems
SYNOPSIS
filename...
Remarks
This manpage describes on Integrity systems. For on PA-RISC systems, see ldd_pa(1).
DESCRIPTION
is a command that can list the dynamic dependencies of incomplete executable files or shared libraries.
lists verbose information about dynamic dependencies and symbol references. If the object file is an executable file, lists all shared
libraries that would be loaded as a result of executing the file. If it is a shared library, lists all shared libraries that would be
loaded as a result of loading the library.
uses the same algorithm as the dynamic loader and to locate the shared libraries at runtime. See in dld.so(5) for more information.
Options
recognizes the following options:
Check reference to data symbols.
Check reference to data and code symbols.
Display the search path used to locate the shared libraries.
Display all dependency relationships.
EXTERNAL INFLUENCES
Environment Variables
uses the following environment variables to locate shared libraries.
These environment variables can be used to specify the directories to be searched for library files at runtime.
The value is a colon-separated list of paths of such directories. For more information, see in dld.so(5) or the option in
ld(1).
The following internationalization variables affect the execution of
Determines the locale category for native language, local customs and
coded character set in the absence of and other environment variables. If is not specified or is set to the empty string, a
default of (see lang(5)) is used instead of
Determines the values for all locale categories and has precedence over
and other environment variables.
Determines the locale that should be used to affect the format
and contents of diagnostic messages written to standard error.
Determines the locale category for numeric formatting.
Determines the locale category for character handling functions.
Determines the location of message catalogs for the processing
of
If any internationalization variable contains an invalid setting, behaves as if all internationalization variables are set to See envi-
ron(5).
DIAGNOSTICS
prints the record of shared library path names to stdout. The optional list of symbol resolution problems are printed to stderr.
returns zero when the operation is successful. A non-zero return code indicates that an error occurred.
EXAMPLES
By default prints a simple dynamic path information. This consists of the dependencies recorded in the executable (or the shared library)
followed by the physical location where these libraries are found.
The option causes to print dependency relationship along with the dynamic path information.
The option to causes it to analyze all symbol references and print information about unsatisfied code and data symbols.
WARNINGS
does not list shared libraries explicitly loaded using dlopen(3C) or shl_load(3X).
FILES
output file
32-bit Integrity system dynamic loader
64-bit Integrity system dynamic loader
32-bit dummy executable loaded to check the dependencies of shared libraries
64-bit dummy executable loaded to check the dependencies of shared libraries
message catalog
SEE ALSO
System Tools
ld(1) invoke the link editor
Miscellaneous
a.out(4) assembler, compiler, and linker output
dld.so(5) dynamic loader
Texts and Tutorials