Recently, a gcc-4.4.6 has been unmasked in the host, but no effort
has been made to make sure the developers select it with gcc-config.
BUG=chromium-os:19613
TEST=ran the tests below with set -x and observed
1) manually set the MINIMUM version to 4.4.7, see it fail
2) two gccs, current + old, set to old, observed the switch and unmerge
3) above, but set to new, same result
4) only one gcc, the current, observed nothing happening
5) only have old gcc, let the script update&select new one, unmerge old
Change-Id: Id2a285a13f5b27d7531eae4db35e36f6b8cc5f4f
Reviewed-on: http://gerrit.chromium.org/gerrit/6694
Reviewed-by: David James <davidjames@chromium.org>
Tested-by: Zdenek Behan <zbehan@chromium.org>
BUG=chromium-os:19868
TEST=build_image --factory # see output as chromiumos_factory_image.bin
build_image --test # see output as chromiumos_test_image.bin
Change-Id: Ice1aa576cfe297db0900e6c42de8d362aa94729a
Reviewed-on: http://gerrit.chromium.org/gerrit/6993
Tested-by: Hung-Te Lin <hungte@chromium.org>
Reviewed-by: Richard Barnette <jrbarnette@chromium.org>
The current code will silence stderr when operating in non-verbose mode
because it always turns on shell tracing with `set -x`. Unfortunately,
this also ends up killing error messages from a bunch of places in the
script as well:
- look for all the "1>&2" uses in mod_image_for_recovery.sh
- look at missing error() override
- look at duplication of die() just to undo things
A really simple example:
$ ./mod_image_for_recovery.sh
$
Did it work? Or did I do something wrong? Who knows!
So undo the stderr silencing and simply turn on `set -x` only when
requested (verbose mode).
BUG=None
TEST=forced some errors in non-verbose mode and saw no output before change, but saw it after change; made a working recovery image
Change-Id: I31578fba091e390a56a437af97782a621e2137fb
Reviewed-on: http://gerrit.chromium.org/gerrit/6904
Reviewed-by: Richard Barnette <jrbarnette@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
BUG=chromium-os:19854
TEST=Ran it
STATUS=Verified
Change-Id: I2fd7d77145e3607c29cfc64500fca8525e9b5992
Reviewed-on: http://gerrit.chromium.org/gerrit/6939
Reviewed-by: Kris Rambish <krisr@chromium.org>
Tested-by: Kris Rambish <krisr@chromium.org>
Reviewed-by: Stanley Wong <stanleyw@chromium.org>
Tested-by: Stanley Wong <stanleyw@chromium.org>
BUG=None
TEST=run the commands in various combinations.
Change-Id: I94fb167d8312a90818910085adebfb1d0396cdbe
Reviewed-on: http://gerrit.chromium.org/gerrit/6866
Reviewed-by: Chris Sosa <sosa@chromium.org>
Reviewed-by: Vince Laviano <vlaviano@chromium.org>
Tested-by: Richard Barnette <jrbarnette@chromium.org>
The process of updating the Portage package status spreadsheet on
buildbots requires a credentials file at ~/.gdata_cred.txt in the
chroot. All buildbot VMs have this file outside the chroot now,
so this change adds that file to the list of things created in
the user's homedir when entering the chroot.
BUG=None
TEST=Run cros_sdk in these scenarios:
~/.gdata_cred.txt exists -> Same file should be at $HOME in chroot
~/.gdata_cred.txt does not exist -> No file created in chroot
Change-Id: I5c0f333a9308f5efa5324ce2e202a7c9e9fdb48b
Reviewed-on: http://gerrit.chromium.org/gerrit/6911
Reviewed-by: Zdenek Behan <zbehan@chromium.org>
Tested-by: Matt Tennant <mtennant@chromium.org>
This version is only used in certain networking tests, and not in
production images. It is needed for linux-3.0 as it has rewritten
build system which doesn't break on linux3.
It needs to be explicitly unmasked by package.unmask, because our
version of portage snapshot hard masks it.
Compared to upstream, this ebuild is x86, arm, amd64 keyworded.
BUG=chromium-os:18442
TEST=build it on host and board
Change-Id: Ieb4914ae9274be397b1cefa90857eed24c14912f
Reviewed-on: http://gerrit.chromium.org/gerrit/6813
Tested-by: Zdenek Behan <zbehan@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
BUG=none
TEST=./build_packages for x86-generic and arm-generic
Change-Id: I51244c981f4e31d556d30d5cec3e70b05e784b3b
Reviewed-on: http://gerrit.chromium.org/gerrit/6731
Reviewed-by: David James <davidjames@chromium.org>
Tested-by: Diego Elio Pettenò <flameeyes@chromium.org>
Earlier version required a local patch to support devicekit-disks,
and therefore was placed in chromiumos-overlay. This version doesn't
have that problem.
A separate change in chromiumos-overlay/chromeos-base/chromeos-initramfs
is required for initramfs to work.
BUG=none
TEST=made sure that devicekit-disks compiles (previously it required a patch)
Change-Id: Ice521216b2545d11a4380eb074a3eba80fc448a0
Reviewed-on: http://gerrit.chromium.org/gerrit/6679
Reviewed-by: Matt Tennant <mtennant@chromium.org>
Reviewed-by: Mandeep Singh Baines <msb@chromium.org>
Tested-by: Luigi Semenzato <semenzato@chromium.org>
test wi-fi devices.
in http://gerrit.chromium.org/gerrit/6405, we introduced support
for running some WiFi autotests in a VM (running a test image).
for those tests to work, the connection manager must not attempt
to manage the devices used by the APs.
this change adds a mod_for_test script that updates flimflam's
init script, adding command-line arguments that tell flimflam
to ignore the AP devices.
BUG=chromium-os:16348
TEST=manual: built test image, checked flimflam args in /etc/init/flimflam.conf
Change-Id: I7a26d817e78f5743e2922a35c20ad6bee139445d
Reviewed-on: http://gerrit.chromium.org/gerrit/6443
Reviewed-by: Richard Barnette <jrbarnette@chromium.org>
Reviewed-by: mukesh agrawal <quiche@chromium.org>
Tested-by: mukesh agrawal <quiche@chromium.org>
This version is only used in certain networking tests, and not in
production images. It is needed for linux-3.0 as it has rewritten
build system which doesn't break on linux3.
It needs to be explicitly unmasked by package.unmask, because our
version of portage snapshot hard masks it.
Compared to upstream, this ebuild is x86, arm, amd64 keyworded.
BUG=chromium-os:18442
TEST=build it, trybot chromiumos-sdk
Change-Id: I746ceac1cce924c28e55810b83a04e9833f65c8b
Reviewed-on: http://gerrit.chromium.org/gerrit/6806
Tested-by: Zdenek Behan <zbehan@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
This give users the choice to have rootfs formatted with squashfs.
When --squash_image is specified, the rootfs will be formatted to squashfs.
Users can also use --squash_sort_file to specify the file priority when
squashfs is created.
BUG=None
TEST=Manually tested "--squash_image", and the image can be installed
from USB stick. Also tried "--squash_sort_file=sort-prio.list", and files
in squashfs are sorted.
Change-Id: I5fd818ac9d1203598926efa82e94fa105cd86ebc
Reviewed-on: http://gerrit.chromium.org/gerrit/5664
Tested-by: Da Zheng <zhengda@chromium.org>
Reviewed-by: Da Zheng <zhengda@chromium.org>
BUG=None
TEST=updated autoconf, checked `autoconf --version`, rebuilt x86-alex from source, booted it; also ran `cbuildbot chromiumos-sdk`
Change-Id: I99d73aad9f425a1b6431bba3b5696ac673803fd9
Reviewed-on: http://gerrit.chromium.org/gerrit/6742
Tested-by: Mike Frysinger <vapier@chromium.org>
Reviewed-by: David James <davidjames@chromium.org>
BUG=None
TEST=updated m4, checked `m4 --version`, rebuilt x86-alex from source, booted it; also ran `cbuildbot chromiumos-sdk`
Change-Id: I98595893e0dc931afd5a0b9158a0305a13da92d1
Reviewed-on: http://gerrit.chromium.org/gerrit/6741
Tested-by: Mike Frysinger <vapier@chromium.org>
Reviewed-by: David James <davidjames@chromium.org>
No local changes made.
This won't actually get merged until package.keywords gets
updated, and that is being done separately for atomicity.
BUG=chromium-os:11963
TEST=deleted x86-alex build; built from scratch; checked symlink
Change-Id: I578c54c9ce7b9db534b0de6eb4a9fe00a9e47753
Reviewed-on: http://gerrit.chromium.org/gerrit/6644
Reviewed-by: Stéphane Marchesin <marcheu@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
No local changes made. Needed with newer eselect-opengl.
This won't actually get merged until package.keywords gets
updated, and that is being done separately for atomicity.
BUG=chromium-os:11963
TEST=deleted x86-alex build; built from scratch; checked symlink; checked that the system booted
Change-Id: Ie749a222d144478fe6129993365ecddd4c5c637a
Reviewed-on: http://gerrit.chromium.org/gerrit/6643
Reviewed-by: Stéphane Marchesin <marcheu@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
BUG=None
TEST=updated attr, rebuilt x86-alex from source, booted it
Change-Id: I31d1ce836ee29531c2ea0b388fb04be425b59a00
Reviewed-on: http://gerrit.chromium.org/gerrit/6738
Reviewed-by: David James <davidjames@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
BUG=None
TEST=updated pkgconfig, checked `pkg-config --version`, rebuilt x86-alex from source, booted it
Change-Id: Ia56dbd977eac74c2a4c65d51f15d474989d9ff3d
Reviewed-on: http://gerrit.chromium.org/gerrit/6735
Reviewed-by: David James <davidjames@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
BUG=None
TEST=updated acl, rebuilt x86-alex from source, booted it
Change-Id: I5386cdd50c067499fa33a2e75383504681756921
Reviewed-on: http://gerrit.chromium.org/gerrit/6737
Reviewed-by: David James <davidjames@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
BUG=None
TEST=updated bison, checked `bison --version`, rebuilt x86-alex from source, booted it
Change-Id: I6714c92289e060cb7e8531c2b8e3afaf04c14746
Reviewed-on: http://gerrit.chromium.org/gerrit/6743
Reviewed-by: David James <davidjames@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
BUG=none
TEST=./setup_board, ./build_packages and ./build_image
Change-Id: Ic0a69b603371e0e7b1cfd38602b629752330d3c4
Reviewed-on: http://gerrit.chromium.org/gerrit/6122
Reviewed-by: David James <davidjames@chromium.org>
Tested-by: Diego Elio Pettenò <flameeyes@chromium.org>
BUG=none
TEST=try uploading a changeset that contains Gentoo code style
Change-Id: I1752eb95873a6d574008389cbc1a219c152806f0
Reviewed-on: http://gerrit.chromium.org/gerrit/6123
Reviewed-by: Ryan Cui <rcui@chromium.org>
Tested-by: Diego Elio Pettenò <flameeyes@chromium.org>
No local changes made.
BUG=None
TEST=updated nasm, rebuilt syslinux, rebuilt usb, booted it
Change-Id: Ie48b513a0256e2de824566290b7df49d6ea1df81
Reviewed-on: http://gerrit.chromium.org/gerrit/6649
Reviewed-by: David James <davidjames@chromium.org>
Reviewed-by: Zdenek Behan <zbehan@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
This fixes a problem with chroots named other than 'chroot', but only
when running inside the chroot.
BUG=chromium-os:19596
TEST=run it inside the chroot
Change-Id: I9532fe7762e2d7e277305fb948e5cabc242a5213
Reviewed-on: http://gerrit.chromium.org/gerrit/6597
Tested-by: Zdenek Behan <zbehan@chromium.org>
Reviewed-by: Zdenek Behan <zbehan@chromium.org>
BUG=chromium-os:19538
TEST=Run 'powertop' and make sure it reports ver. 1.98 at the top.
Change-Id: Ib88309ff329a0ab892555e1757f84289096a9c5a
Signed-off-by: Simon Que <sque@chromium.org>
Reviewed-on: http://gerrit.chromium.org/gerrit/6563
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Reviewed-by: David James <davidjames@chromium.org>
The functions are shared between build_image and mod_image_for_test.sh.
BUG=None
TEST=build_image
Change-Id: Ib6d860a6818abee380dde97460f57943cc0a070c
Reviewed-on: http://gerrit.chromium.org/gerrit/6444
Reviewed-by: Richard Barnette <jrbarnette@chromium.org>
Tested-by: Richard Barnette <jrbarnette@chromium.org>
BUG=chromium-os:19210
TEST=Run a few dozen cbuildbot runs.
Change-Id: I276f23135bfe1dfc95575ffd15507cce6fb2461c
Reviewed-on: http://gerrit.chromium.org/gerrit/6383
Reviewed-by: Chris Sosa <sosa@chromium.org>
Tested-by: David James <davidjames@chromium.org>
The --hwid and --firmware should be assigned with real files by default.
BUG=chromium-os:16751
TEST=./make_factory_package.sh --release RELEASE --factory FACTORY # see error
./make_factory_package.sh --help # see hints to 'none'
./make_factory_package.sh --release RELEASE --factory FACTORY \
--hwid HWID --firmware FIRMWARE # see mini-omaha configured correctly
Change-Id: Ib797cd66e864bd2105622c989b4b03443f361a69
Reviewed-on: http://gerrit.chromium.org/gerrit/6461
Reviewed-by: Tammo Spalink <tammo@chromium.org>
Tested-by: Hung-Te Lin <hungte@chromium.org>
No local changes made.
BUG=chromium-os:19382
TEST=emerged it, review log for recursive calls, and checked its output with xmlto mans
Change-Id: I110b9d92ec34bdaaf18b31c05f797e979ea5ff18
Reviewed-on: http://gerrit.chromium.org/gerrit/6409
Reviewed-by: Anush Elangovan <anush@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
BUG=None
TEST=run cros_sdk
Change-Id: I39fafd58c7cc9fd536fe9b75f314f9970766a483
Reviewed-on: http://gerrit.chromium.org/gerrit/6414
Tested-by: Richard Barnette <jrbarnette@chromium.org>
Reviewed-by: Chris Sosa <sosa@chromium.org>
Reviewed-by: David James <davidjames@chromium.org>
* This CL deprecates the use of enter_chroot and make_chroot completely,
leaving the functionality exposed only through cros_sdk.
BUG=chromium-os:18750
TEST=run them
Change-Id: I864960b4e25245341431c3a3950638fa569820ed
Reviewed-on: http://gerrit.chromium.org/gerrit/6358
Reviewed-by: Anush Elangovan <anush@chromium.org>
Tested-by: Zdenek Behan <zbehan@chromium.org>
"cros_sdk" is a drop-in replacement of enter_chroot.sh. The only
important difference is in the calling path, specifically that
cros_sdk is in path but has to be called from $(pwd) being inside the
repo checkout, while enter_chroot.sh is called by explicit path.
Invariably, "./enter_chroot.sh" can be replaced, as pwd=src/scripts.
Calling by absolute path can be replaced by first changing directory
anywhere into the repo checkout, and then calling cros_sdk.
BUG=chromium-os:18750
TEST=run them
Change-Id: Ieff91a27bb419e1121361d5b3a11e4c87ff7a087
Reviewed-on: http://gerrit.chromium.org/gerrit/6273
Tested-by: Zdenek Behan <zbehan@chromium.org>
Reviewed-by: Zdenek Behan <zbehan@chromium.org>
The script created etc/enable_chromium_minidumps in the
stateful partition; however that file isn't on the whitelist
of stateful files that chromeos-install will install on dev
and test images.
BUG=None
TEST=install test image from USB with and without the change; observe the file is absent in both cases
Change-Id: I841cf9ed4c819a9f18cbdd11a3d42af196ab87bb
Reviewed-on: http://gerrit.chromium.org/gerrit/6354
Tested-by: Richard Barnette <jrbarnette@chromium.org>
Reviewed-by: Chris Masone <cmasone@chromium.org>
This CL adds a new option to mod_image_for_recovery that allows a dev to pass
in another recovery image as an option and have mod_image_for_recovery use
the kernel provided in that image when building a new recovery image.
BUG=chromium-os:19189
TEST=Built using option on image signed with non-dev keys using appropriate
recovery image as base.
Change-Id: I02a3c3bf458fb3c9fee556364005d7eaff5acccc
Reviewed-on: http://gerrit.chromium.org/gerrit/6031
Tested-by: Chris Sosa <sosa@chromium.org>
Reviewed-by: Gaurav Shah <gauravsh@chromium.org>
