| commit | 5d0071fb1fcff1b3d8254e5bcb068a08bd23df29 | [log] [tgz] |
|---|---|---|
| author | pthatcher@webrtc.org <pthatcher@webrtc.org> | Fri Sep 26 18:53:40 2014 |
| committer | pthatcher@webrtc.org <pthatcher@webrtc.org> | Fri Sep 26 18:53:40 2014 |
| tree | 1ae002c3e41c232681827f8c2cb8cdc0b0cc6969 | |
| parent | a21d07160700d50514f16683a45d138d005c67c8 [diff] |
Build one of NSS or BoringSSL but not both. The libraries have some common symbols. When both are linked I observed NSS SHA1_Update called followed by BoringSSL SHA1_Final, which results in a segfault. We should only link one of these. Based off of https://review.webrtc.org/25689004/ BUG=3855 R=pthatcher@webrtc.org Review URL: https://webrtc-codereview.appspot.com/31469004 git-svn-id: http://webrtc.googlecode.com/svn/trunk@7310 4adac7df-926f-26a2-2b94-8c16560cd09d