GauthamBanasandra opened a new pull request #3617:
URL: https://github.com/apache/hadoop/pull/3617
<!--
Thanks for sending a pull request!
1. If this is your first time, please read our contributor guidelines:
https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute
2. Make sure your PR title starts with JIRA issue id, e.g.,
'HADOOP-17799. Your PR title ...'.
-->
### Description of PR
Currently, eay32 is the library that's used in libhdfspp for Windows.
Whereas, we use libcrypto for the rest of the platforms. As per the following
mail thread, the OpenSSL library was renamed from eay32 to libcrypto from
OpenSSL version 1.1.0 onwards -
https://mta.openssl.org/pipermail/openssl-dev/2016-August/008351.html.
Thus, we need to use libcrypto on Windows as well to ensure that we
standardize the version of the OpenSSL libraries used across platforms.
### How was this patch tested?
Build passed on Windows (using stubs for those parts that don't compile yet)
-
https://issues.apache.org/jira/secure/attachment/13035697/build-log-hdfs-nacl-windows-10.log
### For code changes:
- [x] Does the title or this PR starts with the corresponding JIRA issue id
(e.g. 'HADOOP-17799. Your PR title ...')?
- [ ] Object storage: have the integration tests been executed and the
endpoint declared according to the connector-specific documentation?
- [ ] If adding new dependencies to the code, are these dependencies
licensed in a way that is compatible for inclusion under [ASF
2.0](http://www.apache.org/legal/resolved.html#category-a)?
- [ ] If applicable, have you updated the `LICENSE`, `LICENSE-binary`,
`NOTICE-binary` files?
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
