04-09-2008
if this sheds any more light??
bash-3.00$ ldd mkv.so
linux-gate.so.1 => (0xffffe000)
libc.so.6 => /lib/tls/libc.so.6 (0xf7c39000)
/lib/ld-linux.so.2 (0x56555000)
10 More Discussions You Might Find Interesting
1. Programming
Hello,
when i compile with xlc on aix i got the error message "ld: 0711-317 ERROR: Undefined symbol: .hello"
dummy.pc:
#include <stdio.h>
#include <stdlib.h>
#include <string.h>
#include "dummy.h"
int main ( )
{
printf("\nbefore Hello");
hello();
printf("\npast Hello"); ... (2 Replies)
Discussion started by: stockdan
2 Replies
2. Programming
Iam attempting a script to return the current cursor position using the getyc macro
I have #included the curses.h
however on compilation (with gcc) it errors with
Undefined symbol .getcury
Undefined symbol .gercurx
Any ideas where I can find a solution or what I've missed (7 Replies)
Discussion started by: gefa
7 Replies
3. Programming
Didn't have this problem in AIX, but ported to Linux with GCC compiler and am now getting a runtime error:
tssutil: symbol lookup error: /work/agility/devel/bin/libagam.so: undefined symbol: fstat
I'm sure most of you know that fstat is an intrinsic function just like printf, memcpy, etc. When I... (5 Replies)
Discussion started by: marcus121
5 Replies
4. AIX
Hi,
I am using xlC compiler. The compilation goes fine but at the time of linking it gives the following error
ld: 0711-345 Use the -bloadmap or -bnoquiet option to obtain more information.
ld: 0711-317 ERROR: Undefined symbol: .u_strlen_2_6
ld: 0711-317 ERROR: Undefined symbol:... (0 Replies)
Discussion started by: nachiketv
0 Replies
5. AIX
Hi All,
When I am compiling expect 5.40 library in AIX 5.3, I am getting the following error while generating expect5.40.so file.
ld: 0711-317 ERROR: Undefined symbol: .log
ld: 0711-317 ERROR: Undefined symbol: .pow
ld: 0711-345 Use the -bloadmap or... (0 Replies)
Discussion started by: ravindra_maddal
0 Replies
6. Programming
Hi,
I am working with Solaris 5.9 and I am newbie in Socket programming and I stated working with socket programming and I copyed a simple client & server program from a website which I am attaching with this and when I am compiling these files.I am getting the error--
Please Help me to... (1 Reply)
Discussion started by: smartgupta
1 Replies
7. Programming
I am trying to compile pro*c program on aix 5.3. The program compiled fine when I was using curses library. After switching to ncurses, I have started getting compilation errors. After installing ncurses on the box, I changed the -lcurses flag to -lncurses. I have also updated the path to the... (13 Replies)
Discussion started by: wvuguy
13 Replies
8. Programming
I have a C code which i am trying to compile using gcc. When i am trying to compile it i get the error undefined symbol error though i am providing the -l*** option where *** refers to the module where the object files for those symbols are present.
Can someone help me on the same. (4 Replies)
Discussion started by: manaankit
4 Replies
9. Programming
When I try to link a .so file I get the undefined symbol error. Though I have the library file in my system. The compile and linking commands used are as follows
g++ -m64 -g -Wall -I./include -c dxl_sample.c
g++ -o firstprogram -m64 -g -Wall -I./include -Bdynamic... (1 Reply)
Discussion started by: Ranadeep Ghosal
1 Replies
10. UNIX for Advanced & Expert Users
When I try to link a .so file I get the undefined symbol error. Though I have the library file in my system. The compile and linking commands used are as follows
g++ -m64 -g -Wall -I./include -c dxl_sample.c
g++ -o firstprogram -m64 -g -Wall -I./include -Bdynamic... (1 Reply)
Discussion started by: Ranadeep Ghosal
1 Replies
LDD(1) Linux Programmer's Manual LDD(1)
NAME
ldd - print shared object dependencies
SYNOPSIS
ldd [option]... file...
DESCRIPTION
ldd prints the shared objects (shared libraries) required by each program or shared object specified on the command line. An example of
its use and output is the following:
$ ldd /bin/ls
linux-vdso.so.1 (0x00007ffcc3563000)
libselinux.so.1 => /lib64/libselinux.so.1 (0x00007f87e5459000)
libcap.so.2 => /lib64/libcap.so.2 (0x00007f87e5254000)
libc.so.6 => /lib64/libc.so.6 (0x00007f87e4e92000)
libpcre.so.1 => /lib64/libpcre.so.1 (0x00007f87e4c22000)
libdl.so.2 => /lib64/libdl.so.2 (0x00007f87e4a1e000)
/lib64/ld-linux-x86-64.so.2 (0x00005574bf12e000)
libattr.so.1 => /lib64/libattr.so.1 (0x00007f87e4817000)
libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f87e45fa000)
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.
This causes the dynamic linker to inspect the program's dynamic dependencies, and find (according to the rules described in ld.so(8)) and
load the objects that satisfy those dependencies. For each dependency, ldd displays the location of the matching object and the (hexadeci-
mal) address at which it is loaded. (The linux-vdso and ld-linux shared dependencies are special; see vdso(7) and ld.so(8).)
Security
Be aware that in some circumstances (e.g., where the program specifies an ELF interpreter other than ld-linux.so), some versions of ldd may
attempt to obtain the dependency information by attempting to directly execute the program, which may lead to the execution of whatever
code is defined in the program's ELF interpreter, and perhaps to execution of the program itself. (In glibc versions before 2.27, the
upstream ldd implementation did this for example, although most distributions provided a modified version that did not.)
Thus, you should never employ ldd on an untrusted executable, since this may result in the execution of arbitrary code. A safer alterna-
tive when dealing with untrusted executables is:
$ objdump -p /path/to/program | grep NEEDED
Note, however, that this alternative shows only the direct dependencies of the executable, while ldd shows the entire dependency tree of
the executable.
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.
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
pldd(1), sprof(1), ld.so(8), ldconfig(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/.
2017-09-15 LDD(1)