| commit | 3218c1db82718a54e4d41de493d006eaa3ba445c | [log] [tgz] |
|---|---|---|
| author | William D. Irons <wdirons@us.ibm.com> | Sat Jul 14 19:20:47 2018 +0000 |
| committer | Adam Langley <agl@google.com> | Mon Jul 16 17:48:12 2018 +0000 |
| tree | 737f6dd154e6190965b4c278d9e5bf1c5fc4a3e0 | |
| parent | 35b4a1255c301a3931d301cfa17c17d2fef0c1ba [diff] |
Add support for building ppc64le with bazel This commit is to allow Tensorflow to build with boringssl on ppc64le and RHEL7.5/gcc 4.8.5. All the instructions used by linux_x86_64 also need to bet set for linux_ppc64le Change-Id: I4ccf8a61fe3bdd0a49944b48ce7863b97f957a85 Reviewed-on: https://boringssl-review.googlesource.com/29784 Reviewed-by: Adam Langley <agl@google.com>
BoringSSL is a fork of OpenSSL that is designed to meet Google's needs.
Although BoringSSL is an open source project, it is not intended for general use, as OpenSSL is. We don't recommend that third parties depend upon it. Doing so is likely to be frustrating because there are no guarantees of API or ABI stability.
Programs ship their own copies of BoringSSL when they use it and we update everything as needed when deciding to make API changes. This allows us to mostly avoid compromises in the name of compatibility. It works for us, but it may not work for you.
BoringSSL arose because Google used OpenSSL for many years in various ways and, over time, built up a large number of patches that were maintained while tracking upstream OpenSSL. As Google's product portfolio became more complex, more copies of OpenSSL sprung up and the effort involved in maintaining all these patches in multiple places was growing steadily.
Currently BoringSSL is the SSL library in Chrome/Chromium, Android (but it's not part of the NDK) and a number of other apps/programs.
There are other files in this directory which might be helpful: