This is required for the eventual removal of `$PORTDIR` and
`$PORTDIR_OVERLAY` and ensures toolchain rebuilds/updates with
`./build_packages --nousepkg` don't erroniously try to use ebuilds from
`/usr/portage` inside of the SDK.
In order to fix up the build_toolchains script the crossdev overlay
needs to be setup properly, previously only setup_board did it.
Overall silences a lot of warnings and fixes an issue with crossdev:
/usr/bin/emerge-wrapper: line 48: /eclass/toolchain-funcs.eclass: No such file or directory
/usr/bin/emerge-wrapper: line 49: tc-arch: command not found
The portage CBUILD and HOSTCC variables need to be set to the SDK host to get
a proper cross build when building target binaries.
Change _configure_sysroot to use the CBUILD environment variable to set the
CBUILD and HOSTCC variables of ${ROOT}/etc/portage/make.conf. Also, fix up all
calls to _configure_sysroot to set the CBUILD environment variable.
Fixes setup_board failure when the host and target architectures differ.
Signed-off-by: Geoff Levand <geoff@infradead.org>
[marineam: fixed a copy/paste error]
commit 03e8d451bf7d5dc66994ccdc90af39e6128689e5 (setup_board: setup
gdb wrapper and debug symbol path) added hard coded paths for the
symbol path. Change those to use the BOARD_ROOT variable.
Signed-off-by: Geoff Levand <geoff@infradead.org>
Gentoo has switched to using USE=bindist only for packages with optional
features that cannot be distributed and RESTRICT=bindist otherwise. This
change doesn't impact anything in our tree at the moment but we should
follow along to avoid mistakes in the future.
Also, block packages with mirror restrictions. This is just to call
attention to anything that would otherwise be missing from our distfiles
mirror. Nothing we ship should actually have such a restriction.
This was mistakenly added in the early turmoil of forking ChromiumOS in
commit 86ce9947: "the gentoo mirrors don't have this package, download
from Google code for now." Since then we have started to provide our own
mirror instead of using Gentoo's.
For reference, the better rule to use is `RESTRICT=primaryuri` which
prioritizes downloading from `SRC_URI` over the distfiles mirrors but
does not disallow uploading to a mirror.
The v1 API has been removed, so use v2 instead. The 10-second sleep was
added because the fleet tests were failing without it. My guess is that
etcd needed some time to warm up before we flooded it with requests.
Previously fsck output was suppressed to reduce the amount of noise in
build logs on the assumption that fsck really shouldn't have a reason to
fail. The filesystem is freshly created after all. However some users
have reported that fsck is failing but without error messages we don't
know why.
