In both cases move making contact with the remote board to
an earlier step and default the "board" option to whatever
is reported by the remote.
BUG=n0ne
TEST=Run without board flag or .default_board
Change-Id: I53330ce5ab05b4cff92ac3a384ae0202fc156953
Reviewed-on: http://gerrit.chromium.org/gerrit/433
Reviewed-by: Sam Leffler <sleffler@chromium.org>
Tested-by: Paul Stewart <pstew@chromium.org>
This version does not fail to build if .la files are removed.
R=davidjames,raymes
BUG=none
TEST=emerge on chroot system itself.
Change-Id: Id2086a62ddf05c4e5331ba91f817ebd335b84abb
This version does not fail to link the tests when building with gold
and no .la files around. It requires the introspection USE changes
from http://codereview.chromium.org/6298002/
R=davidjames,raymes
BUG=none
TEST=./build_packages && ./build_image
Change-Id: I17d9fe4cf163a3b54306217c9e27390c51af7654
Review URL: http://codereview.chromium.org/6905158
There were two bugs:
1) The test [ ${ARCH} -eq "arm" ] was wrong because -eq is a
numeric comparison operator, not legal on strings.
2) Variable ${ARCH} was used before set.
The code change includes comment changes to clarify the reasons for
the code, and a future-proofing logic change.
Change-Id: I63f502cc33cf8a9a441b4b305fc49ed57d0a55b1
BUG=None
TEST=build_image --factory_install, and boot the resulting image
Review URL: http://codereview.chromium.org/6905119
It seems like we are seeing whacky errors with sys.stderr
dying when trying to print out a process and its exception.
I think controlling how the output is printed in RunCommand
is better than passing it with the exception.
Change-Id: I3711575e5d9e710c3aea6ff19d43d149fd83f44c
BUG=chromium-os:14398
TEST=Ran it with au_test_harness
Review URL: http://codereview.chromium.org/6902129
On x86, booting factory install shim on SD card needs to have the kernel
initrmafs enabled. But on ARM, booting factory install image on network does
not needs initramfs.
TEST=build_image --factory_install
BUG=chromium-os:13211
Change-Id: Id008a3bfaf4f17772e04f02d18844dd09b33fbe1
R=rongchang@chromium.org
Review URL: http://codereview.chromium.org/6901047
verity_depth must be 0. No other values are supported. So changing the
default to 0.
Needs to go in before:
http://codereview.chromium.org/6901005
BUG=chromium-os:14357
TEST=Ran build_image, mod_image_for_test.sh, mod_image_for_recovery.sh
chromeos-install, and image_to_live.sh.
Change-Id: I6208327d9ce68c9ba56d78e99bc145e34bee9d1d
R=wad@chromium.org,scottz@chromium.org,gauravsh@chromium.org
Review URL: http://codereview.chromium.org/6902061
these are original ebuilds file, all ebuild are currently masked. The plan is to enable this on ARM first.
Change-Id: Ia23b731b90870d3d7712c302d71460a258a3c420
BUG=None
TEST=Unmask the it in package.keywords and build on arm successfully.
Review URL: http://codereview.chromium.org/6902042
This CL depends on http://codereview.chromium.org/6765018 which adds fbconsole
USE flag.
Change-Id: I159680e2cd53b6493545f6c0b1caaa8a7e833cb3
BUG=chromium-os:13607
TEST=run mod_image_for_recovery.sh and boot to recovery image to see messages
showed on framebuffer console.
Review URL: http://codereview.chromium.org/6814041
This version includes the boexec patch that was present in
chromiumos-overlay.
Change-Id: I9b0aa22f2f2615a3c03986d865df6a531271448b
R=marcheu@chromium.org
BUG=none
TEST=./setup_board && ./build_packages --nousepkg for x86-generic and arm-generic
Review URL: http://codereview.chromium.org/6778012
Update the eselect-vi package to the latest version, which should also
fix the vim symlinks under /usr/bin to use relative paths.
BUG=chromium-os:14291
TEST=emerge vim and verify that /usr/bin/vi is a symlink to vim, not //usr/bin/vim (or any other rooted path)
Change-Id: Ie1e180d62f7f78e098e449d8762c74f196ef26f9
Review URL: http://codereview.chromium.org/6879117
Auto-detect use of verity, and if verity is not used, copy over modules and firmware.
Also, while I was at it, I added a --noreboot argument.
And also copy over vmlinux.uimg on ARM if on non-verity.
Change-Id: Ida9d3fbf4f342db65ebd0002a8b1a528440ea7fe
BUG=chromium-os:13321
TEST=Build kernel, try updating on x86 and ARM, both with and without verity
Review URL: http://codereview.chromium.org/6881029
Verity only supports a depth of 0. Passing anything other than 0 will
cause a verity failure.
BUG=14314
TEST=Verified that verity does not fail when do depth is passed.
Before this change, verity would fail with the error message
reported in the bug.
Change-Id: I68495c4486284744ee0779b6c9cdc0ef214519c7
R=gauravsh@google.com,scottz@google.com,drewry@google.com
Review URL: http://codereview.chromium.org/6873134
BUG=chrome-os-partner:3118
TEST=emerge and make sure xset-1.2.1-r1 is built. Do 'ldd xset' on the
built executable and make sure it does not have dependency on fontcache.
Change-Id: Ic486863eed0523de009dc2546f33338d655da8b6
Signed-off-by: Simon Que <sque@chromium.org>
Review URL: http://codereview.chromium.org/6879044
Change-Id: If46fd1558a00498ce4721dd756532e916f49bc19
BUG=chromium-os:12950
TEST=Ran with autestharness and ran unittests.
Review URL: http://codereview.chromium.org/6877015
BUG=chromium-os:4760
TEST=below
- build_packages on x86-generic, install, boot, run BVT's
- NOTE: the ebuild is ~keyword, so this will require further commit to cros-overlay
Change-Id: I3ec642332822cb753391b33a734828928dfd7284
R=flameyes@chromium.org,jimhebert@chromium.org,anush@chromium.org
Review URL: http://codereview.chromium.org/6870011
Also includes a style nit fix: don't quote arguments to numeric
comparison test operators.
BUG=chromium-os:13582
TEST=setup_board --force && build_packages && build_image; boot the result
Review URL: http://codereview.chromium.org/6801027
Change-Id: I689ca9697a05cf93a789fde1242fb2fa50f21612
This version includes fixes for building the Perl extension (unneeded) but
also to use the proper CFLAGS during build (most likely desired).
R=yusukes@chromium.org
BUG=none
TEST=emerge-{arm,x86}-generic and build log check
Change-Id: Ie8769b67a2b5bc2845264627ab0fc44312c29954
Review URL: http://codereview.chromium.org/6814030
It makes debugging system boot issues harder, so let's re-enable console
output for a while. It will be quieted down again later.
Change-Id: I7c543c09818c0152470c9f5e54d36c614d05bf3a
BUG=chrome-os-partner:3199
TEST=Boot a system, check for console output before login screen
Review URL: http://codereview.chromium.org/6801045
Plan is to eventually deprecate depth as a configurable parameter.
depth=0 means compute the depth based on a regular trie with a
single block of hashes at the root node.
BUG=chromium-os:9752
TEST=platform_DMVerity
Change-Id: I5c5f1b1f2c2079d7e1ef6c7a55c859b463a59aee
R=wad@chromium.org,taysom@chromium.org,ups@chromium.org,gauravsh@chromium.org,jimherbert@chromium.org
Review URL: http://codereview.chromium.org/6810006
This version includes the fix for building from a host running a stable
kernel like 2.6.38.1 without having kernel sources available.
Change-Id: Ie32a2faae9a8d2567d21711eef79ebfaad6e204c
BUG=chromium-os:13616
TEST=./setup_board and ./build-packages --nousepkg for arm-generic and x86-generic
Review URL: http://codereview.chromium.org/6792005
Currently used for resolv.conf and hosts, because these files can
change during the lifetime of a chroot, for example on computers
with more dynamic network (laptops).
While this creates a persistent process in the background for the
sole purpose of syncing files, the performance impact is negligible.
BUG=12316
TEST=below
1) enter_chroot once+quit, many times + quit, verify correct exit
behaviour
2) enter_chroot, modify host resolv.conf, see chroot being updated
Change-Id: I26573570c027acc2c214a00838a6f982a7585b13
R=robotboy@chromium.org,dparker@chromium.org,sosa@chromium.org
Review URL: http://codereview.chromium.org/6720005
This fixes an issue where passing USE= to build_packages would always
cause build_image to fail.
BUG=none
TEST=create a USE-inconsistent package, run build_image, observe it working
Change-Id: Id9eb3891d9c292423c837a0d097a33155f03b794
R=davidjames@chromium.org,kliegs@chromium.org
Review URL: http://codereview.chromium.org/6677163
This version has the libtool dependency fixed.
R=petkov
BUG=none
TEST=./build_packages on {x86,arm}-generic and check on version built.
Change-Id: I0d90089dc75d91b327558ace89e16cdbc61ddea5
Review URL: http://codereview.chromium.org/6693059
These versions include all (or better) changes that were applied on
ChromiumOS:
- the X USE flag for m17n-lib controls GUI without the "false" warning
about --without-gui;
- m17n-lib also builds in parallel;
- m17n-contrib no longer depends on m17n-db at build-time and also skips
the check for m17n-db;
- m17n-db includes the patch missing upstream.
R=penghuang@chromium.org
BUG=none
TEST=./build_packages and checked content on {x86,arm}-generic, and
upstream Gentoo tests.
Change-Id: I3ab34ee58e5453c93b11e79fbfd2b84fde33f399
Review URL: http://codereview.chromium.org/6717026
This version applies the gold patch directly, without ChromiumOS-specific
patching, and also fixes the automagic dependency problem on OpenCryptoki.
BUG=chromium-os:13728
TEST=emerge-{x86,arm}-generic (and misc test in Gentoo upstream)
Change-Id: I2fbec3fc722f9f307721d481db8873d2b3b62e93
Review URL: http://codereview.chromium.org/6792011
The layout.conf fails declares portage, this overlay and chromiumos as the
reverse-ordered list of overlays to search for eclasses.
Change-Id: I5506c0ca03e9e7d0891f7c08f5463ba9512f74f7
BUG=none
TEST=./setup_board && ./build_packags for {x86,arm}-generic
Review URL: http://codereview.chromium.org/6758048
we don't want any possibility for firmware to be changed in factory setup
BUG=none
TEST=build_image; image_to_usb --factory
Change-Id: Ibef767ea621193afb7fbca5ea96120a506891dcb
R=nsanders@chromium.org
Review URL: http://codereview.chromium.org/6764010
Upgrade dev-libs/libxml2-2.7.3-r2 to dev-libs/libxml2-2.7.8
Upgrade app-admin/eselect-python-20091230 to app-admin/eselect-python-20100321
Upgrade sys-libs/readline-6.0_p4 to sys-libs/readline-6.1_p2
Upgrade sys-libs/zlib-1.2.3-r1 to sys-libs/zlib-1.2.5-r2
BUG=chromium-os:10373
TEST=x86 and arm: build_packages, build_image, ran suite_Smoke for x86
Change-Id: Ic36959dbd40fc4aed23dfc4c2072402617976638
Review URL: http://codereview.chromium.org/6776028
To get best factory test image performance, we should disable update engine.
BUG=chromium-os:13613
TEST=image_to_usb --factory --to=FACTORY
then verified /etc/init/update-engine.conf is disabled.
Change-Id: Ifb7b6c821f434ee68625ffea0eb7907c38d77315
R=nsanders@chromium.org
Review URL: http://codereview.chromium.org/6759023
