On 01/05/03 18:29, m.w.chang wrote:
you meant when builing those packages (like bind in my example),
I needed to use the --option to force static library build?
Building static binaries should be avoided unless you have a really good
reason. They're an order of magnitude larger, and less efficient. I
wouldn't consider openssl a good reason.
can I make bind to refer to libcrypto.so rather than libcrypto.so.x.y.z
where x.y.z is the version?
I don't know, but i don't see why you'd want to.
in the meantime, I am using symbol link.
dig: error while loading shared libraries: libcrypto.so.0.9.6: cannot
load share d object file: No such file or directory
No, this is the expected result when you rebuild openssl and a few other
libs. The only workaround is to build static binaries.
--
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
L. Friedman [EMAIL PROTECTED]
Linux Step-by-step & TyGeMo: http://netllama.ipfox.com
7:45pm up 22 days, 2:54, 2 users, load average: 1.18, 1.18, 0.93
_______________________________________________
Linux-users mailing list
[EMAIL PROTECTED]
Unsubscribe/Suspend/Etc -> http://www.linux-sxs.org/mailman/listinfo/linux-users
