Skip to content
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.

Sign up for GitHub

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

Jump to bottom

libpq requires HAVE_CRYPTO_LOCK for thread safety with openssl <1.1.0 #8076

Merged
merged 1 commit into from
Sep 6, 2019
Merged

libpq requires HAVE_CRYPTO_LOCK for thread safety with openssl <1.1.0 #8076

merged 1 commit into from
Sep 6, 2019

Conversation

ian-p-cooke
Copy link
Contributor

resolves #8075

@grdowns
Copy link
Contributor

grdowns commented Sep 6, 2019

Thanks for the fix, @ian-p-cooke!

@grdowns grdowns merged commit 5a476f9 into microsoft:master Sep 6, 2019
@ian-p-cooke
Copy link
Contributor Author

Hey, I realized when pulling and upgrading that I didn't bump the version number in ports/libpq/CONTROL. Should we do that?

@grdowns grdowns mentioned this pull request Sep 7, 2019
Merged
@grdowns
Copy link
Contributor

grdowns commented Sep 7, 2019

Good catch. Thanks 😄

@ian-p-cooke ian-p-cooke mentioned this pull request Sep 13, 2019
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees

@grdowns grdowns

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

[libpq] define HAVE_CRYPTO_LOCK
2 participants
@ian-p-cooke @grdowns