https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=210820
Rudolf Čejka <cej...@fit.vutbr.cz> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |cej...@fit.vutbr.cz
--- Comment #12 from Rudolf Čejka <cej...@fit.vutbr.cz> ---
Just a small reminder and more description for those, who want to reproduce
this problem (as I came across it yesterday too): The problem is still here and
not fixed.
How to reproduce it (as of ports revision r419436, Aug 1 2016):
- Install 11-STABLE/HEAD, where SSLv2 is removed from /usr/lib/libssl.so.8
- Install security/openssl with default options, where SSLv2 in
/usr/local/lib/libssl.so.8 is still included
- DO NOT Install or Uninstall port devel/ncurses - then base ncurses are used
and -rpath /usr/lib:${LOCALBASE}/lib is added
- Then try to upgrade lang/python27. There is USES=... ncurses ... ssl ...,
which implies that cumulative -rpath "/usr/lib:/usr/local/lib:/usr/local/lib"
is used, which breaks python's runtime with openssl from ports. More
technically, make framework sets LDFLAGS to ... -Wl,-rpath=${NCURSESRPATH} ...
${OPENSSL_LDFLAGS}, where NCURSESRPATH is /usr/lib:${LOCALBASE}/lib and
OPENSSL_LDFLAGS is -Wl,-rpath,${OPENSSLRPATH}.
Ultra-fast but Dirty workaround: Swap ncurses and ssl in USES from
USES=... ncurses ... ssl ...
to
USES=... ssl ... ncurses ...
;o)
SSLv2 mismatch (in base it is not, in ports it is) is not needed - but it
beautifully reveals, that runtime library used is other than linking library.
--
You are receiving this mail because:
You are the assignee for the bug.
_______________________________________________
freebsd-python@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-python
To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"
