sstp-client 1.0.12-r1 is not compliant with EVP and HMAC recent openssl API versions. A quite small patch can solve the issue. Note that trunk seems to have been updated 9 months ago as far as I can see Reproducible: Always Steps to Reproduce: Try to build sstp-client with a recent openssl library installed Actual Results: Build fails while compiling src/sstp-http.c and src/sstp-cmac.c Expected Results: Build to succeed
Created attachment 843367 [details] output from emerge --info =net-misc/sstp-client-1.0.12-r1
Created attachment 843369 [details, diff] Patch proposal for recent openssl API compliance
Which OpenSSL version? I assume 3.x? If so, I'd generally advise to be using ~arch for packages for now, as we only just unmasked 3.x. Is sstp-client-1.0.17 fine? I see: - https://gitlab.com/eivnaes/sstp-client/-/commit/1ba4a45133eb1c8757457c3d7ddf33bda2506ea1 - https://gitlab.com/eivnaes/sstp-client/-/commit/4c56206e1f7d97c254463614f0d14353d90e307e I've filed bug 886617 for stabilisation anyway.
# equery list openssl * Searching for openssl ... [IP-] [ ] dev-libs/openssl-1.1.1q:0/1.1 I can confirm that version 1.0.17 compiles fine. Just checked using ebuild ... clean compile test because I don't want to merge this version for now on this machine which is an hardened net server. I have to admit the patch in the trunk is much better than mine as it checks for openssl version to implement the correct API (3 versions, from what I've seen).
Ah, thanks. It's frustrating there's still packages out there broken with 1.1.x!
Fixed in 1.0.17. Thanks!