On Thu, 7 Sep 2017 11:27:03 -0400 Tony Nelson <tonynelson@xxxxxxxxxxxxxxxxx> wrote: > On 17-09-06 14:03:44, Rick Stevens wrote: > > On 09/06/2017 09:40 AM, Ranjan Maitra wrote: > > > Hi, > > > > > > Dillo's ssl support seems to be broken in F26 (and has been since > > the day it was released). Here is what happens: > > > > > > Go to https://www.nytimes.com/ > > > > > > The webpage says that Dillo's prototype plugin for https support is > > disabled. > > > > > > I downloaded the src.rpm to see what the problem was with the .spec > > file and found that nothing has changed. Specifically, the following > > is there (as it was for the F25 spec): > > > > > > %configure --disable-dependency-tracking --enable-ipv6 --enable-ssl > > > > > > So, then I was wondering why this has stopped working with dillo > > with F26. Any ideas for a fix? > > > > It's very odd. I built the source RPM and the configuration failed the > > SSL library test saying it can't find SSL_library_init(), thus it > > isn't > > enabling SSL (below is culled from the config.log file after a > > "rpmbuild > > -bc dillo.spec"): > ... > > | /* Override any GCC internal prototype to avoid an error. > > | Use char because int might match the return type of a GCC > > | builtin and then its argument prototype would still apply. */ > > | #ifdef __cplusplus > > | extern "C" > > | #endif > > | char SSL_library_init (); > > | int > > | main () > > | { > > | return SSL_library_init (); > > | ; > > | return 0; > > | } > > configure:6208: result: no > > configure:6224: WARNING: *** No libssl found. Disabling ssl > > support.*** > ... > > Looks like the same sort of problem as with balsa email client, or > actually libesmtp: not compatible with openssl-1.1 [1]. > > [1]: https://bugzilla.redhat.com/show_bug.cgi?id=1483350 I don't completely understand the solution. Does this mean that the patch should be made against libesmtp? Should I file a bug report for libesmtp? Thanks, Ranjan _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
