-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Sebastian,
My problem was just Pound - I'm just a user when it comes to these tools. I do not know how widespread this problem is or how common it is for projects to use openssl dhparam -C during their build process (as opposed to running it once and including the output in their a source distribution). I performed a few quick searches and found some examples - but not many. The more I think about it, the more disappointed I am that OpenSSL upstream don't feel it's worth their while to simply make their code generator backwards compatible. But it's not my call. I don't know how much effort is justified here, I just wanted to be sure it was on your radar. Thank you for considering my report. Cheers, - Bjarni Sebastian Andrzej Siewior <sebast...@breakpoint.cc> wrote: > On 2017-02-18 15:23:02 [+0000], Bjarni R. Einarsson wrote: > > When trying to build Pound against libssl1.0, the build fails because > > Pound uses the openssl tool to generate C code containing DH parameters > > (openssl dhparam -C ...). > > > > The system-wide openssl on Debian testing is from OpenSSL 1.1, and > > generates C code which is incompatible with OpenSSL 1.0. As a result it > > is impossible to build some software (Pound) against OpenSSL 1.0 in > > spite of having installed libssl1.0-dev. > > Is you problem just pound? If so I'm not going to introduce > openssl for 1.0.2 just for that. pound is on my list of things > to do so it will be fixed shortly. I am not yet sure what I > will do but something will be done⦠> > Sebastian -----BEGIN PGP SIGNATURE----- Version: GnuPG v1 iQEcBAEBAgAGBQJYqMgHAAoJEI4ANxYAz5SRv6wH/RZt6UJsqw+N9JYuYRBdI6qq 7c/VBUKkcBoF+WTjZbG4GCl9+pBye52YbWMhpNp2mA0C+rs4wZ/aFgEIuMBzPplf QVIH25AXh873lv+1sI0Yju7XGaTuNkntbYRfx5DgxUUkxBZzydZC2c2DbUoj0Wdi vK2J4DULYgfD19g0F2rRdgpHCh+ufDntwq7y3evKtWSJoQpyatV3froGWYOA7tG3 BsnDySPQanxz3X0FkDEAyP53ZKh2bosHgTJ3xe9aJECZlhUWEzgKc5bqLHSwOwf6 kXqyw4JXugieREdUtRr8A0RNhaoPUTlU77ccSdFzHEQRBedza/UH/Nw3AA7f+jQ= =mxao -----END PGP SIGNATURE-----