Re: ssl=base
25.11.2018 18:57, Franco Fichtner wrote: >> Why can't you use LibreSSL port for some ports and base libssl for other >> ports? >> That is, net/mpd5 links with base system libfetch that depends on base >> libssl, >> so it is example of port that cannot be built with LibreSSL. > > FWIW, since 2015 we've had no build or operational issue with mpd5 for > LibreSSL > from ports. Fixed in r485853. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: ssl=base
I had this problem in the past, the solution I found was to build a "port" of libfetch using /usr/src/lib/libfetch link libfetchagainst security/openssl and than net/mpd5 against the libfetch in /usr/local/lib It was some time ago.. ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: ssl=base
> On 25. Nov 2018, at 12:51 PM, Eugene Grosbein wrote: > > Why can't you use LibreSSL port for some ports and base libssl for other > ports? > That is, net/mpd5 links with base system libfetch that depends on base libssl, > so it is example of port that cannot be built with LibreSSL. FWIW, since 2015 we've had no build or operational issue with mpd5 for LibreSSL from ports. If the issue is mixed linkling between base and ports, it's not that LibreSSL fails but rather any combination of base and ports, on FreeBSD 12 even between 1.1.1 and 1.0.2. On 11 that wasn't really an issue because base OpenSSL and ports OpenSSL were the same so I can understand where the the idea of "breakage" for LibreSSL specifically comes from. Cheers, Franco ___ freebsd-ports@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: ssl=base
25.11.2018 18:46, Mathieu Arnold wrote:
>> As maintainer of the net/mpd5 port, I wonder why our ports/Mk/Uses/ssl.mk
>> prevents building this port using FreeBSD 12 and base system libssl
>> when libressl is installed?
>>
>> While building with ssl=base, the port itself does not include headers
>> from ${LOCALBASE}/include and it does not include ${LOCALBASE}/lib to search
>> path for linking stage.
>>
>> I see no way to override noted (wrong) check-depends restriction, and that's
>> not good.
>
> Because you either use OpenSSL from the base system, or you install an
> *SSL variant from ports and use it. You cannot mix half of the stuff
> from the base system and half of the stuff from a port version of *SSL.
Why can't you use LibreSSL port for some ports and base libssl for other ports?
That is, net/mpd5 links with base system libfetch that depends on base libssl,
so it is example of port that cannot be built with LibreSSL.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
Re: ssl=base
On Sun, Nov 25, 2018 at 03:12:43PM +0700, Eugene Grosbein wrote:
> Hi!
>
> As maintainer of the net/mpd5 port, I wonder why our ports/Mk/Uses/ssl.mk
> prevents building this port using FreeBSD 12 and base system libssl
> when libressl is installed?
>
> While building with ssl=base, the port itself does not include headers
> from ${LOCALBASE}/include and it does not include ${LOCALBASE}/lib to search
> path for linking stage.
>
> I see no way to override noted (wrong) check-depends restriction, and that's
> not good.
Because you either use OpenSSL from the base system, or you install an
*SSL variant from ports and use it. You cannot mix half of the stuff
from the base system and half of the stuff from a port version of *SSL.
--
Mathieu Arnold
signature.asc
Description: PGP signature
ssl=base
Hi!
As maintainer of the net/mpd5 port, I wonder why our ports/Mk/Uses/ssl.mk
prevents building this port using FreeBSD 12 and base system libssl
when libressl is installed?
While building with ssl=base, the port itself does not include headers
from ${LOCALBASE}/include and it does not include ${LOCALBASE}/lib to search
path for linking stage.
I see no way to override noted (wrong) check-depends restriction, and that's
not good.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"
