ldd: Lists dynamic dependencies

[Jose Luis]

Hi,

Given the code below:

<<<<snip>>>>


$ uname -a
AIX cobrosr 3 5 00C7A4B24C00
$ cat foo.c
#include <stdio.h>


int main()
{
}
$ gcc foo.c
$ ldd a.out
a.out needs:
/usr/ccs/lib/libc.a(shr.o)
/unix
/usr/lib/libcrypt.a(shr.o)


<<snip>>

Why does ldd show "static" dependencies?

What is the meaning of "(shr.o)" after libc.a?

Thanks in advance,
Jose Luis.

 

[Keith Thompson]

Given the code below:

<<<<snip>>>>

What was snipped here?

$ uname -a
AIX cobrosr 3 5 00C7A4B24C00
$ cat foo.c
#include <stdio.h>


int main()
{
}
$ gcc foo.c
$ ldd a.out
a.out needs:
/usr/ccs/lib/libc.a(shr.o)
/unix
/usr/lib/libcrypt.a(shr.o)


<<snip>>

Why does ldd show "static" dependencies?

What is the meaning of "(shr.o)" after libc.a?

Your question really isn't about C, it's about your operating system.

There are two AIX-specific newsgroups I know of, comp.sys.aix and
comp.unix.aix; whichever one is currently active would probably be
a good place to ask. Or perhaps comp.unix.programmer; I'm not sure
whether your question is AIX-specific.

 

[Chris H]

In message <[email protected]

$ gcc foo.c
$ ldd a.out

Well I did some googling...
LDD == Legion of Dynamic Discord
which seems appropreate (even if it is the wrong answer

a.out needs:
/usr/ccs/lib/libc.a(shr.o)
/unix
/usr/lib/libcrypt.a(shr.o)

This suggests your library paths are not correct.

Why does ldd show "static" dependencies?

Because these dependencies are always needed at compile time. They are
not dynamically linked libraries.

What is the meaning of "(shr.o)" after libc.a?

Try Google or man