Switch Linux and CrOS to BoringSSL.

Switch Linux and CrOS to BoringSSL.

If this causes problems, please revert first and ask questions
later.

BUG=462040
Committed: https://crrev.com/df391ba1d19134bb0a6e895a4a33f1af4932545d
Cr-Commit-Position: refs/heads/master@{#338713}

[davidben, 2015-07-09 22:42:34]

davidben@chromium.org changed reviewers:
+ rsleevi@chromium.org, thakis@chromium.org

[davidben, 2015-07-09 22:42:34]

Okay, I believe this is finally ready.

I will not land this until after branch point. (Hoping to land it as soon as
possible after it to maximize bake time over the 46 cycle.)

[Nico, 2015-07-09 22:44:02]

android too, right?

[davidben, 2015-07-09 22:45:28]

On 2015/07/09 22:44:02, Nico wrote:
> android too, right?

Android's been on BoringSSL/OpenSSL since it began. Although, that's
interesting. Android must have been setting it elsewhere.

I'll go refactor build/common.gypi a little so that's less weird...

[davidben, 2015-07-09 22:50:50]

On 2015/07/09 22:45:28, David Benjamin wrote:
> On 2015/07/09 22:44:02, Nico wrote:
> > android too, right?
> 
> Android's been on BoringSSL/OpenSSL since it began. Although, that's
> interesting. Android must have been setting it elsewhere.
> 
> I'll go refactor build/common.gypi a little so that's less weird...

Alright, how's this?

[Nico, 2015-07-09 22:57:06]

LGTM ONLY VALID UNTIL 2015-07-12

[davidben, 2015-07-10 16:33:19]

(cast_shell_linux is red on PS7. I reran them on PS8, but it should still be
red. That will be resolved when https://codereview.chromium.org/1235653002/
lands.)

[davidben, 2015-07-13 17:43:48]

I believe we've now branched? chrome/VERSION says MAJOR=46, so it should be okay
to land this. Ryan? (I'll notify a few teams specifically to be sure, and send a
PSA when it lands.)

Removed the "NOT TO LAND UNTIL 2015-07-13" note from the commit message.

(Nico, I'm assuming your "ONLY VALID UNTIL" was a joke on that. You should make
noise at me if you intended otherwise. ;-) )

[Ryan Sleevi, 2015-07-13 17:48:44]

lgtm

[Nico, 2015-07-13 17:55:58]

lgtm

[Nico, 2015-07-13 17:56:57]

(but i haven't received the ""m45 branch is here" mail yet, so maybe wait until
that's out. or they used a different subject this time round?)

[davidben, 2015-07-13 18:13:16]

On 2015/07/13 17:56:57, Nico wrote:
> (but i haven't received the ""m45 branch is here" mail yet, so maybe wait
until
> that's out. or they used a different subject this time round?)

Oh, good point. I don't think I've gotten it either. I'll wait for that and/or
ask the TPMs before landing. (I usually sync with a TPM first anyway.)

[davidben, 2015-07-14 16:12:42]

The CQ bit was checked by davidben@chromium.org

[commit-bot: I haz the power, 2015-07-14 16:13:15]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/1210073014/130001

[commit-bot: I haz the power, 2015-07-14 17:57:39]

Committed patchset #8 (id:130001)

[commit-bot: I haz the power, 2015-07-14 17:58:39]

Patchset 8 (id:??) landed as
https://crrev.com/df391ba1d19134bb0a6e895a4a33f1af4932545d
Cr-Commit-Position: refs/heads/master@{#338713}

[hongchan, 2015-07-14 20:01:15]

A revert of this CL (patchset #8 id:130001) has been created in
https://codereview.chromium.org/1235673005/ by hongchan@chromium.org.

The reason for reverting is: This CL seems to cause the issue in Chromium build
system.

https://build.chromium.org/p/chromium.chrome/builders/Google%20Chrome%20Linux....