04-04-2008
thanks for your replay,
yes you are right the the ldd tool lists the dependent shared libraries that the executable requires, along with their paths if found.
But i want to write an application which shoud do the same functionality.
Please suggest me how to interprete the ELF file to collect the information.
i need exactly as LDD tool.
10 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hi all,
I'm looking to write a script that is dependent upon the existence of 2 files each in separate directories. My thought was to do:
**psuedo code **
execute script
check directory 1 for file1
if file exists then
execute script 2 ( checking directory 2 for file 2)
else... (3 Replies)
Discussion started by: keladar
3 Replies
2. Linux
Hello,
This is not exactly relevant to Linux kernel but I'm gonna ask any way.
Is there any way I can modify a 64-bit ELF object file to make it look like 32-bit ELF object file and link it (using `ld`) with 32-bit ELF file?
I tried libelf but was unsuccessful. I had this pretty link... (1 Reply)
Discussion started by: tejuwala
1 Replies
3. UNIX for Advanced & Expert Users
The binary file is
ELF-64 executable object file - IA64.
How i know that the source is
Is there any comamnd in unix i can read these kind of files or use a thirty party software?
Thanks for your help (8 Replies)
Discussion started by: alexcol
8 Replies
4. Shell Programming and Scripting
I had to whip this up, and it seems useful enough to post here. Say you have been cleaning up your filesystem, and you removed a bunch of libraries, or you shuffled around some library directories, and aren't sure if ld.so.conf is correctly setup. You want to sweep through your file system looking... (0 Replies)
Discussion started by: otheus
0 Replies
5. Linux
Folks,
I have some program(Test.cpp) as follows,
#include<iostream>
class Abc
{
private:
int _theVar;
public :
int printVar();
};
int Abc :: printVar()
{
_theVar=10;
}
main()
{
Abc _t; (0 Replies)
Discussion started by: vinod_chitrali
0 Replies
6. Programming
Folks,
I have some program(Test.cpp) as follows,
#include<iostream>
class Abc
{
private:
int _theVar;
public :
int printVar();
};
int Abc :: printVar()
{
_theVar=10;
}
main()
{
Abc _t; (2 Replies)
Discussion started by: vinod_chitrali
2 Replies
7. Solaris
Hi Anyone,
I have two disks , one is primary and anothe is mirror.
I checked my mirror disk , It was fine.
After that i booted from my primary disk, did some installations regarding kernel patches.
It did not get booted properly. It says
====================
Not a valid... (2 Replies)
Discussion started by: jegaraman
2 Replies
8. Shell Programming and Scripting
xxxxx (2 Replies)
Discussion started by: vinayrao
2 Replies
9. Programming
Hi!!! How do I create a file .ELF? What code should I use, could help me with a simple code or example? I know programming to Windows by important languages but this seems to be more sistematical, and I really don't know how to. (2 Replies)
Discussion started by: linecoder
2 Replies
10. Solaris
I have given the relevant details below. Why are the libraries in
/export/home/builds/pc9x_root/960/build/powrmart/pmbuild/bin/SunOS.64.r are invisible to ldd?
%setenv
... (3 Replies)
Discussion started by: old_as_a_fossil
3 Replies
LEARN ABOUT MOJAVE
ldconfig
LDCONFIG(8) Linux Programmer's Manual LDCONFIG(8)
NAME
ldconfig - configure dynamic linker run-time bindings
SYNOPSIS
/sbin/ldconfig [-nNvXV] [-f conf] [-C cache] [-r root] directory...
/sbin/ldconfig -l [-v] library...
/sbin/ldconfig -p
DESCRIPTION
ldconfig creates the necessary links and cache to the most recent shared libraries found in the directories specified on the command line,
in the file /etc/ld.so.conf, and in the trusted directories, /lib and /usr/lib (on some 64-bit architectures such as x86-64, lib and
/usr/lib are the trusted directories for 32-bit libraries, while /lib64 and /usr/lib64 are used for 64-bit libraries).
The cache is used by the run-time linker, ld.so or ld-linux.so. ldconfig checks the header and filenames of the libraries it encounters
when determining which versions should have their links updated.
ldconfig will attempt to deduce the type of ELF libraries (i.e., libc5 or libc6/glibc) based on what C libraries, if any, the library was
linked against.
Some existing libraries do not contain enough information to allow the deduction of their type. Therefore, the /etc/ld.so.conf file format
allows the specification of an expected type. This is used only for those ELF libraries which we can not work out. The format is
"dirname=TYPE", where TYPE can be libc4, libc5, or libc6. (This syntax also works on the command line.) Spaces are not allowed. Also see
the -p option. ldconfig should normally be run by the superuser as it may require write permission on some root owned directories and
files.
OPTIONS
-c fmt, --format=fmt
(Since glibc 2.2) Cache format to use: old, new, or compat (default).
-C cache
Use cache instead of /etc/ld.so.cache.
-f conf
Use conf instead of /etc/ld.so.conf.
-i, --ignore-aux-cache
(Since glibc 2.7) Ignore auxiliary cache file.
-l (Since glibc 2.2) Library mode. Manually link individual libraries. Intended for use by experts only.
-n Process only the directories specified on the command line. Don't process the trusted directories, nor those specified in
/etc/ld.so.conf. Implies -N.
-N Don't rebuild the cache. Unless -X is also specified, links are still updated.
-p, --print-cache
Print the lists of directories and candidate libraries stored in the current cache.
-r root
Change to and use root as the root directory.
-v, --verbose
Verbose mode. Print current version number, the name of each directory as it is scanned, and any links that are created. Overrides
quiet mode.
-V, --version
Print program version.
-X Don't update links. Unless -N is also specified, the cache is still rebuilt.
FILES
/lib/ld.so
Run-time linker/loader.
/etc/ld.so.conf
File containing a list of directories, one per line, in which to search for libraries.
/etc/ld.so.cache
File containing an ordered list of libraries found in the directories specified in /etc/ld.so.conf, as well as those found in the
trusted directories.
SEE ALSO
ldd(1), ld.so(8)
COLOPHON
This page is part of release 4.15 of the Linux man-pages project. A description of the project, information about reporting bugs, and the
latest version of this page, can be found at https://www.kernel.org/doc/man-pages/.
GNU 2017-09-15 LDCONFIG(8)