Re: libelf now depends on openssl

2021-01-15 Thread Robbie Harwood
"Colin Walters" writes: > On Fri, Jan 15, 2021, at 9:47 AM, Simo Sorce wrote: >> >> There is of course no problem to have it in Fedora, but if this is >> something that is going to end up in RHEL one day, it would be better >> to do the work now to make it use OpenSSL rather than scramble later.

Re: libelf now depends on openssl

2021-01-15 Thread Simo Sorce
On Fri, 2021-01-15 at 14:22 -0500, Colin Walters wrote: > > On Fri, Jan 15, 2021, at 9:47 AM, Simo Sorce wrote: > > There is of course no problem to have it in Fedora, but if this is > > something that is going to end up in RHEL one day, it would be better > > to do the work now to make it use Ope

Re: libelf now depends on openssl

2021-01-15 Thread Colin Walters
On Fri, Jan 15, 2021, at 9:47 AM, Simo Sorce wrote: > > There is of course no problem to have it in Fedora, but if this is > something that is going to end up in RHEL one day, it would be better > to do the work now to make it use OpenSSL rather than scramble later. Isn't it at least part of th

Re: libelf now depends on openssl

2021-01-15 Thread Simo Sorce
On Fri, 2021-01-15 at 09:33 -0600, Michael Catanzaro wrote: > On Fri, Jan 15, 2021 at 9:47 am, Simo Sorce wrote: > > Which is one of the reasons we do not admit boringssl in RHEL. > > > > There is of course no problem to have it in Fedora, but if this is > > something that is going to end up in R

Re: libelf now depends on openssl

2021-01-15 Thread Michael Catanzaro
On Fri, Jan 15, 2021 at 9:47 am, Simo Sorce wrote: Which is one of the reasons we do not admit boringssl in RHEL. There is of course no problem to have it in Fedora, but if this is something that is going to end up in RHEL one day, it would be better to do the work now to make it use OpenSSL r

Re: libelf now depends on openssl

2021-01-15 Thread Simo Sorce
On Fri, 2021-01-15 at 10:25 +0100, Florian Weimer wrote: > * Zbigniew Jędrzejewski-Szmek: > > > On Thu, Jan 14, 2021 at 08:24:03AM -0600, Michael Catanzaro wrote: > > > On Thu, Jan 14, 2021 at 12:52 am, Kevin Kofler via devel > > > wrote: > > > > Do the boringssl symbols not have hidden visibilit

Re: libelf now depends on openssl

2021-01-15 Thread Florian Weimer
* Zbigniew Jędrzejewski-Szmek: > On Thu, Jan 14, 2021 at 08:24:03AM -0600, Michael Catanzaro wrote: >> On Thu, Jan 14, 2021 at 12:52 am, Kevin Kofler via devel >> wrote: >> >Do the boringssl symbols not have hidden visibility in libwebrtc? >> >If they >> >do, why are they getting interposed anywa

Re: libelf now depends on openssl

2021-01-15 Thread Zbigniew Jędrzejewski-Szmek
On Thu, Jan 14, 2021 at 08:24:03AM -0600, Michael Catanzaro wrote: > On Thu, Jan 14, 2021 at 12:52 am, Kevin Kofler via devel > wrote: > >Do the boringssl symbols not have hidden visibility in libwebrtc? > >If they > >do, why are they getting interposed anyway? If they don't, why > >not? I assume

Re: libelf now depends on openssl

2021-01-14 Thread Michael Catanzaro
On Thu, Jan 14, 2021 at 12:52 am, Kevin Kofler via devel wrote: Do the boringssl symbols not have hidden visibility in libwebrtc? If they do, why are they getting interposed anyway? If they don't, why not? I assume the library is private to libwebrtc and its symbols should not be exported. l

Re: libelf now depends on openssl

2021-01-13 Thread Kevin Kofler via devel
Michael Catanzaro wrote: > I notice that WebKit, when built with WebRTC enabled, now crashes > during the build: > > https://bugs.webkit.org/show_bug.cgi?id=214812#c7 > > It's a symbol conflict between boringssl (used by libwebrtc) and > openssl. Do the boringssl symbols not have hidden visibili

libelf now depends on openssl

2021-01-13 Thread Michael Catanzaro
Hi, I notice that WebKit, when built with WebRTC enabled, now crashes during the build: https://bugs.webkit.org/show_bug.cgi?id=214812#c7 It's a symbol conflict between boringssl (used by libwebrtc) and openssl. But why is openssl involved at all? It's a dependency of libcurl, which is a de