Bug#828360: jabberd2: FTBFS with openssl 1.1.0
forwarded -1 https://github.com/jabberd2/jabberd2/issues/125 tags -1 + upstream thanks Den Sun, 25 Sep 2016 21:13:47 +0200 skrev Re: jabberd2: FTBFS with openssl 1.1.0: > On Sun, Sep 25, 2016 at 06:54:41PM +0200, Simon Josefsson wrote: > > Thanks for the report. As far as I can see, jabberd2 tries to test > > for the library symbol CRYPTO_lock in libcrypto.so from OpenSSL. > > Has this symbol been (re)moved? You could try rebuilding the > > latest jabberd2 2.4.0 also. > > Yes, CRYPTO_lock has been removed. Thanks -- I'll file this upstream. It uses CRYPTO_lock in configure.ac, not in actual code. So it might be easy to fix. > I'll see about testing that some time, but it's very low on my > priority queue. Don't worry -- I read code and it won't help to test a later version. /Simon pgpI7Qw3Pokws.pgp Description: OpenPGP digital signatur
Bug#828360: jabberd2: FTBFS with openssl 1.1.0
On Sun, Sep 25, 2016 at 06:54:41PM +0200, Simon Josefsson wrote: > Thanks for the report. As far as I can see, jabberd2 tries to test for > the library symbol CRYPTO_lock in libcrypto.so from OpenSSL. Has this > symbol been (re)moved? You could try rebuilding the latest jabberd2 > 2.4.0 also. Yes, CRYPTO_lock has been removed. I'll see about testing that some time, but it's very low on my priority queue. Kurt
Bug#828360: jabberd2: FTBFS with openssl 1.1.0
Thanks for the report. As far as I can see, jabberd2 tries to test for the library symbol CRYPTO_lock in libcrypto.so from OpenSSL. Has this symbol been (re)moved? You could try rebuilding the latest jabberd2 2.4.0 also. Thanks, Simon pgpS8AclWDmn2.pgp Description: OpenPGP digital signatur
Bug#828360: jabberd2: FTBFS with openssl 1.1.0
Source: jabberd2 Version: 2.3.4-1 Severity: important Control: block 827061 by -1 Hi, OpenSSL 1.1.0 is about to released. During a rebuild of all packages using OpenSSL this package fail to build. A log of that build can be found at: https://breakpoint.cc/openssl-1.1-rebuild-2016-05-29/Attempted/jabberd2_2.3.4-1_amd64-20160529-1432 On https://wiki.openssl.org/index.php/1.1_API_Changes you can see various of the reasons why it might fail. There are also updated man pages at https://www.openssl.org/docs/manmaster/ that should contain useful information. There is a libssl-dev package available in experimental that contains a recent snapshot, I suggest you try building against that to see if everything works. If you have problems making things work, feel free to contact us. Kurt