Huh! That's surprising - I'm curious if there's something different about your setup than our CI... do you know if there's anything obviously different?

I suppose that the difference is that those instances are relying on the system openssl dev package which installs headers in /usr/include? I'm running cmake with a flag to get it to find my own openssl that I built elsewhere. I'm just guessing.

I suppose that the difference is that those instances are relying on the system openssl dev package which installs headers in /usr/include? I'm running cmake with a flag to get it to find my own openssl that I built elsewhere. I'm just guessing.

Nice, thanks for the info. I wonder if I'll need to do a similar thing for mbedTLS or something. I'll play around a bit.

Nice, thanks for the info. I wonder if I'll need to do a similar thing for mbedTLS or something. I'll play around a bit.

Yes, definitely, this will fail whenever the SSL implementation headers are in a location that is not part of the standard include search path. So the fix looks good to me and should be applied, probably with additional fixes for the other libraries. Happy to merge this single fix as a standalone, though.

Yes, definitely, this will fail whenever the SSL implementation headers are in a location that is not part of the standard include search path. So the fix looks good to me and should be applied, probably with additional fixes for the other libraries. Happy to merge this single fix as a standalone, though.

Yeah, I haven't played around a bit yet. I'll merge as-is and revisit other implementations when I have some time.