Update boringssl submodule version#13105
Conversation
b4ecb7c to
5dfefb6
Compare
|
Thank you for your pull request. Before we can look at your contribution, we need to ensure all contributors are covered by a Contributor License Agreement. After the following items are addressed, please respond with a new comment here, and the automated system will re-verify.
Regards, |
5dfefb6 to
c90bde4
Compare
|
Signed linuxfoundation CLA and rebased. Please can someone take a look? Thanks! |
|
Is there anything I can do to get this going? Or any problems blocking it that aren't in a place I can see? @ctiller @nicolasnoble |
c90bde4 to
8da7707
Compare
|
Pushed a rebase. |
8da7707 to
b253de9
Compare
b253de9 to
4eaec35
Compare
|
Rebased again... |
This includes several fixes for compiling with old versions of gcc, and one for building with clang on OSX.
This is the output of running tools/buildgen/generate_projects.sh
4eaec35 to
47476ab
Compare
|
Rebased, included a handful more boringssl commits to pull in another compile fix. |
|
Hi @illicitonion, I'm sorry this pull request didn't get any attention. We appreciate the pull request and should've given it attention when you created it. I tried to update BoringSSL back in September with #12700, but at that time, there were some conflicts that stopped us from proceding, which we brought up with BoringSSL. I just recently was able to update BoringSSL with #13948 and #14256, so I hope this resolves any issue you may have had. |
This includes several fixes for compiling with old versions of gcc, and
one for building with clang on OSX.
With this change, I was able to successfully run
make grpc_cli.