[Bug 710] ReliantUnix: -ldl missing when libcrypto is a shared object

[bugzilla-daemon at mindrot.org]

http://bugzilla.mindrot.org/show_bug.cgi?id=710





------- Additional Comments From Robert.Dahlem at siemens.com  2003-09-25 08:05 -------
Define "harm" :-)

I tried the famous "Hello World!\n" program:

$ cc hello.c -o hello
$ ldd hello
/usr/lib/libc.so
$ cc hello.c -o hello -ld
$ ldd hello
/usr/lib/libdl.so
/usr/lib/libc.so

What you can see is that the dynamic linker honors -ldl by searching libdl.so
for any unresolved externals each time one invokes the program. It might even
map it into the processes memory. If you consider this "harm" then yes, there is
harm in using -ldl when building with a static libcrypto.

Personally I consider it harm increasing overall system load by building OpenSSH
with a static libcrypto, that's why I built libcrypto as shared object. Name it
attitude. :-)

I didn't want to call it nonsense to use my trivial patch and always build with
-ldl under ReliantUnix (I need it anyway). I just wanted to say I would consider
it clever to avoid a superfluous -ldl when it's just that: superfluous.




------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.