Fix for cross compiling 32bit linux on 64bit host machine

Fix for cross compiling 32bit linux on 64bit host machine

Right now when custom sysroot is provided as gn parameter (target_sysroot)
only 32 bit custom sysroot will be used. 64 bit sysroot (which is also needed
by 32 bit build by - for example - protobuf) is expected to be found in default
location. This change adds possibility to provide path to directory containing
both sysroots for linux (32 bit and 64 bit).

BUG=622616
Committed: https://crrev.com/16c1060131d3e94aa57a241f3ed33afbdf2f2263
Cr-Commit-Position: refs/heads/master@{#402742}

[ckulakowski, 2016-06-27 08:08:44]

Description was changed from

==========
Fix for cross compiling 32bit linux on 64bit host machine

Right now when custom sysroot is provided as gn parameter (target_sysroot)
only 32 bit custom sysroot will be used. 64 bit sysroot (which is also needed
by 32 bit build by - for example - protobuf) is expected to be found in default
location. This change adds possibility to provide path to directory containing
both sysroots for linux (32 bit and 64 bit).

BUG=622616
==========

to

==========
Fix for cross compiling 32bit linux on 64bit host machine

Right now when custom sysroot is provided as gn parameter (target_sysroot)
only 32 bit custom sysroot will be used. 64 bit sysroot (which is also needed
by 32 bit build by - for example - protobuf) is expected to be found in default
location. This change adds possibility to provide path to directory containing
both sysroots for linux (32 bit and 64 bit).

BUG=622616
==========

[ckulakowski, 2016-06-27 08:08:45]

ckulakowski@opera.com changed reviewers:
+ dpranke@chromium.org

[ckulakowski, 2016-06-28 15:19:08]

ckulakowski@opera.com changed reviewers:
+ scottmg@chromium.org

[Dirk Pranke, 2016-06-29 01:24:50]

I guess that's as good as anything I can come up with offhand, and it's at least
simple.

I'm not sure that that's the right long-term option but until someone else has
another use for this, lgtm :).

[ckulakowski, 2016-06-29 05:59:11]

The CQ bit was checked by ckulakowski@opera.com

[commit-bot: I haz the power, 2016-06-29 05:59:24]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-06-29 07:08:12]

Description was changed from

==========
Fix for cross compiling 32bit linux on 64bit host machine

Right now when custom sysroot is provided as gn parameter (target_sysroot)
only 32 bit custom sysroot will be used. 64 bit sysroot (which is also needed
by 32 bit build by - for example - protobuf) is expected to be found in default
location. This change adds possibility to provide path to directory containing
both sysroots for linux (32 bit and 64 bit).

BUG=622616
==========

to

==========
Fix for cross compiling 32bit linux on 64bit host machine

Right now when custom sysroot is provided as gn parameter (target_sysroot)
only 32 bit custom sysroot will be used. 64 bit sysroot (which is also needed
by 32 bit build by - for example - protobuf) is expected to be found in default
location. This change adds possibility to provide path to directory containing
both sysroots for linux (32 bit and 64 bit).

BUG=622616
==========

[commit-bot: I haz the power, 2016-06-29 07:08:13]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2016-06-29 07:10:57]

Description was changed from

==========
Fix for cross compiling 32bit linux on 64bit host machine

Right now when custom sysroot is provided as gn parameter (target_sysroot)
only 32 bit custom sysroot will be used. 64 bit sysroot (which is also needed
by 32 bit build by - for example - protobuf) is expected to be found in default
location. This change adds possibility to provide path to directory containing
both sysroots for linux (32 bit and 64 bit).

BUG=622616
==========

to

==========
Fix for cross compiling 32bit linux on 64bit host machine

Right now when custom sysroot is provided as gn parameter (target_sysroot)
only 32 bit custom sysroot will be used. 64 bit sysroot (which is also needed
by 32 bit build by - for example - protobuf) is expected to be found in default
location. This change adds possibility to provide path to directory containing
both sysroots for linux (32 bit and 64 bit).

BUG=622616

Committed: https://crrev.com/16c1060131d3e94aa57a241f3ed33afbdf2f2263
Cr-Commit-Position: refs/heads/master@{#402742}
==========

[commit-bot: I haz the power, 2016-06-29 07:10:58]

Patchset 1 (id:??) landed as
https://crrev.com/16c1060131d3e94aa57a241f3ed33afbdf2f2263
Cr-Commit-Position: refs/heads/master@{#402742}

[odinho, 2016-06-29 08:21:25]

On 2016/06/29 at 01:24:50, dpranke wrote:
> I guess that's as good as anything I can come up with offhand, and it's at
least simple.
> 
> I'm not sure that that's the right long-term option but until someone else has
another use for this, lgtm :).

But does the wheezy-x64 and wheezy-ia32 actually exist anywhere in Chromium? 
The normal sysroots are called "debian_wheezy_amd64-sysroot" for the ones
downloaded from Google Cloud Storage.  Will this actually work at all?

[Dirk Pranke, 2016-06-29 16:02:02]

On 2016/06/29 08:21:25, odinho wrote:
> On 2016/06/29 at 01:24:50, dpranke wrote:
> > I guess that's as good as anything I can come up with offhand, and it's at
> least simple.
> > 
> > I'm not sure that that's the right long-term option but until someone else
has
> another use for this, lgtm :).
> 
> But does the wheezy-x64 and wheezy-ia32 actually exist anywhere in Chromium? 
> The normal sysroots are called "debian_wheezy_amd64-sysroot" for the ones
> downloaded from Google Cloud Storage.  Will this actually work at all?

This doesn't affect the default builds, since target_sysroot_dir won't be set.