Using config/k8 as default config path in the taget_arch other than ia32.

It seemed that linux_chromeos_arm bot still use openssl,
Changed the linux logic to be same as one before issue 7920010.
Committed: http://src.chromium.org/viewvc/chrome?view=rev&revision=101988

[michaelbai, 2011-09-19 23:20:49]

The previous cl failed on linux_chromeos_arm bot which seems still use openssl.

[michaelbai, 2011-09-19 23:21:25]

On 2011/09/19 23:20:49, michaelbai wrote:
> The previous cl failed on linux_chromeos_arm bot which seems still use
openssl.

This CL was verified on linux_chromeos_arm bot.

[agl, 2011-09-20 17:33:08]

NACK.

We need to find out why ChromeOS is using OpenSSL first. The ARM clobber builder
doesn't list it compiling any OpenSSL files. Can you point me to the build break
log?

[michaelbai, 2011-09-20 18:25:53]

Here it is

http://build.chromium.org/p/chromium/builders/Arm/builds/17555/steps/update/l...


On 2011/09/20 17:33:08, agl wrote:
> NACK.
> 
> We need to find out why ChromeOS is using OpenSSL first. The ARM clobber
builder
> doesn't list it compiling any OpenSSL files. Can you point me to the build
break
> log?

[agl, 2011-09-20 18:33:35]

On Tue, Sep 20, 2011 at 2:25 PM,  <michaelbai@chromium.org> wrote:
> Here it is
>
>
http://build.chromium.org/p/chromium/builders/Arm/builds/17555/steps/update/l...

Ah, ok, it's just a GYP error. It's probably pulling in openssl due to
flip_in_mem_edsm_server.

Change LGTM then, although I'm not sure why k8 was made the default.
As a 64-bit platform, it would seem that piii would make a better
default, no?


Cheers

AGL