net/mpd5: - Unmark BROKEN_SSL, LDFLAGS fixes it - Re-arrange variables, none-OPTION relatated variables doesn't go after Adding LDFLAGS= -L${LOCALBASE}/lib fixed "BROKEN" ssl
Created attachment 197389 [details] Unmark BROKEN_SSL net/mpd5: - Unmark BROKEN_SSL, LDFLAGS fixes it - Re-arrange variables, none-OPTION relatated variables doesn't go after PR: 231622 Submitted by: Nathan <ndowens@yahoo.com>
Created attachment 197390 [details] Unmark BROKEN_SSL Fix typo in patch desc
Created attachment 197391 [details] Unmark BROKEN_SSL
mpd5 successfully compiles with openssl-devel or openssl111 but cannot be linked because it links with base system libfetch(3) that currently links with /usr/lib/libssl.so.8 (openssl 1.0.2p-freebsd). So, one should not attempt to build mpd5 with newer openssl version until it's imported to base system so mpd5 won't link with two distinct openssl versions.
Comment on attachment 197391 [details] Unmark BROKEN_SSL Also, since the USES=ssl provider (port) can be overridden by the user or the framework in various scenarios, one should always use the OPENSSL* variables from Uses/ssl.mk, who's values change based on the selection, and not use direct paths @Eugen, in the absence of this or anything else (in the immediate term) as a fix/workaround, is this issue a closed/WONTFIX?
In fact, this is basically same as PR 231599. This PR contains non-working patch, though: it does eliminate build errors but produces wrongly linked binary. *** This bug has been marked as a duplicate of bug 231599 ***
(In reply to Eugene Grosbein from comment #6) How does it produce wrong linked binary? I tested overriding default version inside poudriere jail.
(In reply to Nathan from comment #7) Nevermind, just seen a reply that I didn't see before posting comment