10-18-2007
So the question is which set of libc/libpthread is
(a) the pair that your application is balking over
(b) the pair that you should actually be using.
You may have to start doing the folllowing....
1. check the dates of the various libraries
2. use "elfdump" to try and find the signature your program is needing.
So you do need to find the offending program that is failing, then keep on trying by changing LD_LIBRARY_PATH and testing with ldd until the program happily loads.
10 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
I made the fatal mistake of rename the usr directory.
I cannot run any commands due to the fact that ld.so.1 is in usr/lib/--and it doesn't exist
How can I recover my system? (1 Reply)
Discussion started by: SmartJuniorUnix
1 Replies
2. Shell Programming and Scripting
hello all
im trying to use in sun Solaris the information received from the top command
now i several machines that dont have install the top program so when im running the script im geting error
saying after im running this code :
set MemoryInfo = `top | grep Memory`
if (... (2 Replies)
Discussion started by: umen
2 Replies
3. Solaris
I have found this error when i logged in as root: su -
Any body have any idea where this error coming from or what is not working?
-Adeel (1 Reply)
Discussion started by: deal732
1 Replies
4. Solaris
I am trying to build a product which is depend on system library and getting below error. How to resolve below Error:-
ldd /finder3/baseline/95/ed/src/lib/libcartoGraphCPP.so
libsunmath.so.1 => /opt/SUNWspro/SC4.2/lib/libsunmath.so.1
libm.so.1 => /usr/lib/libm.so.1... (1 Reply)
Discussion started by: shafi2all
1 Replies
5. UNIX for Dummies Questions & Answers
Hi All,
when i ran a shell script ,its showing "^M: not found" errore
i used the the code
dos2unix sunshine.sh sunshine1.sh
and then again i ran the scriptand then its still showing the errore
please help me in the matter.
thanks... (3 Replies)
Discussion started by: manit
3 Replies
6. UNIX and Linux Applications
hi:
I had an existing script in production and I commented some lines and implemented the same. The scripts fails with a cc of 127 and I get the msg:
^M: not found
I checked the file format and it is a PC file format. Does this cause the script to fail with cc= 127.
Can somebody... (4 Replies)
Discussion started by: Meghna
4 Replies
7. Shell Programming and Scripting
Hey
I have a weird "problem" here It's more out of curiosity, my script is working fine, but giving me a "pidt.sh: 7: Rather: not found" error...
#!/bin/sh
log="log/`date +%F_pidt.log`"
echo "---n`date`n---n" >> $log
for i in `cat pidt.conf`
do
|| $( /etc/init.d/$i start &&... (3 Replies)
Discussion started by: al0x
3 Replies
8. Programming
i have downloaded <libncurses5-dev_5.7+20101128-1_i386.deb> and <ndk++-0.0.1alpha4.tar.bz2> which contains the header files curses.h and gtk/gtk.h ..
i have also included them using ..
#include "/home/ball/Desktop/Sudoku/project/libncurses5-dev_5.7+20101128-1_i386/usr/include/curses.h"
... (2 Replies)
Discussion started by: upvan111
2 Replies
9. UNIX for Advanced & Expert Users
What package would I need to get this file? SUNW_1.22.7. Please help. thank you. :) (5 Replies)
Discussion started by: SystemAddict
5 Replies
10. Shell Programming and Scripting
I had a spot of trouble coming up with a title, hopefully you'll understand once you read my problem... :)
I have the output of an ldapsearch that looks like this:
dn: cn=sam,ou=company,o=com
uidNumber: 7174
gidNumber: 49563
homeDirectory: /home/sam
loginshell: /bin/bash
uid: sam... (2 Replies)
Discussion started by: samgoober
2 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)