-
Notifications
You must be signed in to change notification settings - Fork 10.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adding a check to find NPN-capable OpenSSL. #2174
Conversation
|
||
int main() { | ||
SSL_get0_next_proto_negotiated(NULL, NULL, NULL); | ||
return OPENSSL_NPN_UNSUPPORTED; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is slightly confusing but if you have a good rationale for it, that's fine. Maybe a comment...
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Updated.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't see it. Did you push?
8b4c6ce
to
4cc8c8a
Compare
Just to make sure. Do you want me to add it to #2176? |
travis is red for a makefile generation issue. I'll merge when it's green. |
Conflicts: Makefile templates/Makefile.template
Crap, I didn't realize this still wasn't merged. And here I was, telling people around me this was done. I'm a bad person. PR has been updated. |
Also, @murgatroid99, have a quick look at the Makefile changes ? |
happy to merge but travis python is red. @nathanielmanistaatgoogle do you think it's a flake? |
Travis is all green now btw :-P |
Adding a check to find NPN-capable OpenSSL.
Several comments:
-) We're always going to try building the embedded OpenSSL if we have it and if the system one isn't ALPN-capable.
-) I've removed the hardcoded test for the version number: this seems irrelevant now, especially since we have another check elsewhere that ensures the version of the submodule (which was the reason for that test to begin with).