01-23-2008
Thanks for your reply. When i did a ldd on the executable it pointed to informix 9.3 libraries which are available in my machine.
I dont find fglsys.h in my informix directory. Let me know where i can find it or do i need to install some patch to get the same.
Thanks
10 More Discussions You Might Find Interesting
1. Programming
I have this problem:
# make
gcc -g -D_REENTRANT -DDISABLE_MJPEG=1 -I. -o encmain.o -c encmain.cc
ld: 0711-317 ERROR: Undefined symbol: std::string::_Rep::_S_max_size
collect2: ld returned 8 exit status
but
from /usr/local/include/g++v3/bits/basic_string.h :
namespace... (0 Replies)
Discussion started by: thalex
0 Replies
2. Programming
Hi everyone,
I have a problem.
I do not succeed to linking the oracle7's library for my .so and a Unresolved Symbol :sqlcxt error returns me when I call program.
this is my makefile.
cc -Ae -I/usr/include/curses_colr -L/usr/lib -DUSE_TERMIOS -D_FILE64 -DDYNAMIC_LIBRARIES_SUPPORTED... (2 Replies)
Discussion started by: luckycs
2 Replies
3. Programming
1 . I use Digital Unix V4.0F
2 . I compile a programe which use a shared library . But when I run it( prog.out) , the shell told me that "Fatal Error : /sbin/loader : unresolved symbol in lib3cZap.so"
But When I compile proj.out and lib3cZap.so , the compiler said nothing . And I ls -l... (1 Reply)
Discussion started by: chenhao_no1
1 Replies
4. UNIX for Dummies Questions & Answers
when I make ncftp 111.111.1.2
I just get problems like ...
/usr/lib/dld.sl unresolved symbol:inet_ntop (code)
does anybody know what is the problem and how to solve this?
thx.. (2 Replies)
Discussion started by: svennie
2 Replies
5. Programming
I use a standard C source to access large files in a 32 bit environment.
I've replaced fopen, fwrite and fread by fopen64, fwrite64 and fread64.
First I did a test only replacing fopen by fopen64, it compiled without any other changes to my compilation options.
The program crashed on a write, as... (3 Replies)
Discussion started by: Isax50
3 Replies
6. Programming
Hi,
want to port an executable from AIX 5.3 to AIX 5.2.
This seems to be no problem, when i build one executable.
But in another case i have to link one library statically and
the rest is loaded at runtime. This works for AIX 5.3 but
on AIX 5.2 i get the following error
... (2 Replies)
Discussion started by: pm_user
2 Replies
7. UNIX for Dummies Questions & Answers
Hello I am new to this forum and have been perplexed by this issue for the last hour of my life, I've tried to search everywhere for a solution to my syntax error, but here is my code.
grep -wvnf 'noise.dat' sample.out | sort
output:
4:Java Swing
5:Swing Java
6:Software Requirements... (2 Replies)
Discussion started by: Gvsumrb
2 Replies
8. Shell Programming and Scripting
Hi Gurus,
I had a problem writing a pipe file.
Previously i used this code to generate a tab seperated file
ABCEF := ABCEF || 'to_char('|| abc_tab(col_num).col_name || ') chr(9) || ';
Now i want the o/p as pipe seperated file.I changed the line as below
ABCEF := ABCEF ||... (0 Replies)
Discussion started by: pssandeep
0 Replies
9. AIX
Hello experts ,
i have some strange problem,
i wanted to create a shared object in AIX 5.3 for which i have compiled all my .cxx to .o which worked fine and then i created the .so from them , but when i do
nm -Bo sample.so ,
i have many unresolved symbol, including printf... (0 Replies)
Discussion started by: vin_pll
0 Replies
10. Solaris
deleteing post (0 Replies)
Discussion started by: dshakey
0 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)