On Thu, 3 Dec 2009, Dmitry Pryanishnikov wrote:
Hello!
While unfortunate, I understand why. I think FreeBSD should encourage
people who use OpenSSL for anything (ssh, etc) that they install OpenSSL
via ports, set WITH_OPENSSL_PORT=YES and recompile apps/ports that use
it.
I agree, it's much simpler (IMHO) to upgrade OpenSSL installed from port
than to patch one in base. Just be aware that bugs can be met with on this
path - just like ports/138466 (affects www/apache22 built
WITH_OPENSSL_PORT=yes). It is critical to make sure that right runtime
libraries (those from /usr/local/lib, not from the base) are used by _every_
application built WITH_OPENSSL_PORT=YES - and it's not always true ;(
Agreed. I ran into this problem, I had an old ENV var LD_LIBRARY_PATH in
one of my .tcshrc scripts that caused lighttpd to compile with the libssl
from base but the libcrypto from the port. Running make, then confirming
your binary/binaries are linked correctly to the right libraries using
'ldd' is recommended to confirm what you expect.
Beckman
---------------------------------------------------------------------------
Peter Beckman Internet Guy
beck...@angryox.com http://www.angryox.com/
---------------------------------------------------------------------------
_______________________________________________
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
