We use python to build, so make sure we depend on it.
BUG=chromium-os:25254
TEST=`emerge seabios` still works
Change-Id: Ie88ca955a3ad315572f5b21fb1e39a65620c5550
Reviewed-on: https://gerrit.chromium.org/gerrit/14671
Reviewed-by: David James <davidjames@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
This reverts commit c770fd9ac4c35af21df7e9837cf7d5f1a306ad1b. We
were getting unit test failures
(http://build.chromium.org/p/chromiumos/builders/x86%20generic%20full/
builds/1483/steps/UnitTest/logs/stdio), and this CL was identified as the
culprit.
BUG=chromium-os:25355
TEST=None
Change-Id: I66a42ef80e4c7d66021bb59d01cb894d5cd2c1a5
Reviewed-on: https://gerrit.chromium.org/gerrit/14629
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Tested-by: Sean Paul <seanpaul@chromium.org>
We have updated the toolchain in the chroot to use a newer version of
libstdc++ than what is installed on our workstations. This means
this additional library is required to generate deltas outside of the
chroot.
BUG=chromium-os:25277
TEST=Generated zip file, and ran contents outside of chroot on my workstation.
Change-Id: I5a90ee355aabd4849a9186a9a66e3dc9b1c51d52
Reviewed-on: https://gerrit.chromium.org/gerrit/14597
Reviewed-by: Eric M. Blake <eblake@google.com>
Reviewed-by: Eric Blake <eblake@chromium.org>
Tested-by: Don Garrett <dgarrett@chromium.org>
Commit-Ready: Don Garrett <dgarrett@chromium.org>
The factory test image was created by using rsync from build artifacts
in chroot, which has some concerns:
- Runtime dependencies of autotest-factory won't be picked into image.
- If a developer skips build_package and builds image by using only pre-built
binary packages, he will get nothing in factory test image.
- It's hard for developers to figure out how and when his changes will be
merged to next build_image (cros_workon does not really work).
- Output image will be definitely different for every developers, also the
official build bots.
- If developers never wipes his chroot (setup_board), the factory test image
will grow until out of space. (For example, my environment outputs a 825M
image while the official buildbot generates only 563M for same ToT source).
This CL changes image build command to using portage emerge, so that output
image can be prepared faster and smaller, and easier for maintenance.
BUG=chromium-os:3335
TEST=./build_packages; ./build_image --factory # Image starts factory UI successfully
# Also tried tests in test_list.all, seems fine.
time ./mod_image_for_test.sh --factory --force_copy --no_inplace
# time: 3m2s => 1m55s, factory test image data: 825/563M => 378M
./build_image --factory_install # factory install shim is also fine
Change-Id: I82b4505c74cd31e718aaff4a319d50b69b2c852c
Reviewed-on: https://gerrit.chromium.org/gerrit/14473
Tested-by: Hung-Te Lin <hungte@chromium.org>
Reviewed-by: Richard Barnette <jrbarnette@chromium.org>
Commit-Ready: Hung-Te Lin <hungte@chromium.org>
Not all 64-bit platforms have names starting with amd64-, so we should
use portageq to get the board architecture name.
BUG=chromium-os:25228
TEST=./cros_generate_breakpad_symbols --board=x86-alex, amd64-corei7, link
Change-Id: I83769575dbd19112b929724995d0c97ed4df2b02
Reviewed-on: https://gerrit.chromium.org/gerrit/14444
Commit-Ready: Vincent Palatin <vpalatin@chromium.org>
Tested-by: Vincent Palatin <vpalatin@chromium.org>
Reviewed-by: David James <davidjames@chromium.org>
Buildbots are periodically failing to build images; the evidence
points to failures in mount_gpt_image.sh, but it's inconclusive.
Add detailed error messages to mount failures so as to be able
to debug more the next time it happens.
BUG=chromium-os:24975
TEST=build_image, to see that successful cases still work
TEST=repeatedly mount new images with mount_gpt_image until it fails
Change-Id: I711fb0dec62dbab3817a62895b53e14376702544
Reviewed-on: https://gerrit.chromium.org/gerrit/14410
Commit-Ready: Richard Barnette <jrbarnette@chromium.org>
Tested-by: Richard Barnette <jrbarnette@chromium.org>
Reviewed-by: David James <davidjames@chromium.org>
The variable setup is "FLAGS_force_non_usb", not "FLAGS_force_non".
Trying to run this currently results in:
./image_to_usb.sh: line 189: [: -ne: unary operator expected
Copying USB image .../chromiumos_image.bin to device /dev/sdb...
This should have instead errored out:
Error: Device /dev/sdb does not appear to be a USB or MMC disk!
Without this fix, image_to_usb.sh proceeds to corrupt the non-usb
disk (which in my case happened to be a backing store for lvm where
all my source was stored and ext4 not surprisingly barfed).
BUG=None
TEST=`./image_to_usb.sh --board=x86-alex -y --to=/dev/sdb` (where /dev/sdb is a disk) now errors out instead of clobbering data
TEST=`./image_to_usb.sh --board=x86-alex -y --to=/dev/sdc` (where /dev/sdc is USB) still works
Change-Id: Id691846393c02cf199309495ae2080b15626e684
Reviewed-on: https://gerrit.chromium.org/gerrit/14334
Reviewed-by: Zdenek Behan <zbehan@chromium.org>
Reviewed-by: Chris Wolfe <cwolfe@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
This reverts commit 726b06283a5a3e58cee4d048d113c28b12002460.
We will move it to the chromiumos-overlay for further modification.
BUG=chrome-os-partner:6497
TEST='equery-x86-alex depends libv4l' shows nothing at this point.
Change-Id: Ic593d2372ee047663e53207ae3b84fe3eafb08dd
Reviewed-on: https://gerrit.chromium.org/gerrit/14280
Reviewed-by: Hung-Te Lin <hungte@chromium.org>
Tested-by: Tai-Hsu Lin <sheckylin@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Tai-Hsu Lin <sheckylin@chromium.org>
This reverts commit 2e35eea1bd1de5d3b9ea582f36db04afc239885b
Change-Id: I4fddcf056f9bc77d6a40e4a203ba2e575fe7b5b1
Reviewed-on: https://gerrit.chromium.org/gerrit/14225
Commit-Ready: Tai-Hsu Lin <sheckylin@chromium.org>
Tested-by: Tai-Hsu Lin <sheckylin@chromium.org>
Reviewed-by: Rong Chang <rongchang@chromium.org>
The CL adds media-libs/libv4l version 0.8.5. It will be used by
OpenCV to capture images from webcam in factory tests.
BUG=chrome-os-partner:6497
TEST='emerge-x86-alex libv4l' works
TEST='emerge-x86-zgb libv4l' works
TEST='emerge-amd64-generic libv4l' works
TEST='emerge-tegra2_kaen libv4l' works
Change-Id: Icf97c0cc9fde1c3310f9214e9c633e3bc98e7811
Reviewed-on: https://gerrit.chromium.org/gerrit/14146
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Tai-Hsu Lin <sheckylin@chromium.org>
Tested-by: Tai-Hsu Lin <sheckylin@chromium.org>
Right now, the buildbot won't symbolize any crash that occurs in autotest
because all symbols in /usr/local/autotest are skipped by breakpad. Tweak
cros_generate_breakpad_symbols to not skip over these symbols so that
browser test crashes can be symbolized.
BUG=chromium-os:25061
TEST=Run cros_generate_breakpad_symbols and verify it still completes
successfully, and generates working symbols for autotest that can
be used to symbolize browser test crashes.
Change-Id: I072498060e78b373bd12c94ff95465878301cbce
Reviewed-on: https://gerrit.chromium.org/gerrit/14155
Commit-Ready: David James <davidjames@chromium.org>
Reviewed-by: David James <davidjames@chromium.org>
Tested-by: David James <davidjames@chromium.org>
Upgraded app-text/openjade to version 1.3.2-r3 on amd64
(note: not a version change, just a change to the build patches, to
successfully compile under gcc 4.6)
BUG=chromium-os:24927
TEST=emerge openjade (as a dependancy of gtk-doc)
Change-Id: Ia78294688a005c6618ff5d35b3a115a58120f7c1
Reviewed-on: https://gerrit.chromium.org/gerrit/14104
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Nathan J. Williams <njw@chromium.org>
Tested-by: Nathan J. Williams <njw@chromium.org>
Upgraded dev-util/gtk-doc to version 1.18 on amd64
BUG=chromium-os:24927
TEST=Run gtkdocize
Change-Id: I0889bbc429d43e3d1ebbbf5f3f48bc626f7b31b4
Reviewed-on: https://gerrit.chromium.org/gerrit/14103
Commit-Ready: Nathan J. Williams <njw@chromium.org>
Tested-by: Nathan J. Williams <njw@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Upgraded dev-util/gtk-doc-am to version 1.18 on amd64
BUG=chromium-os:24927
TEST=Install gtk-doc 1.18
Change-Id: I6d5bcf8ff3bcceb7adc05dab88eee9a2cb705a9b
Reviewed-on: https://gerrit.chromium.org/gerrit/14102
Commit-Ready: Nathan J. Williams <njw@chromium.org>
Tested-by: Nathan J. Williams <njw@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
This reverts commit 6fa1e14c59e541780e49a48f83683db079614d8f
We reverted the glibc-2.11.1-r4 ebuild (it no longer exists), so we have to revert this too since there is no 2.11.1-r4 to use.
Change-Id: Ie8d71eeaf436b348a695d55376e269557ced3b15
Reviewed-on: https://gerrit.chromium.org/gerrit/14061
Reviewed-by: Yunlian Jiang <yunlian@chromium.org>
Tested-by: Yunlian Jiang <yunlian@chromium.org>
Reviewed-by: asharif <asharif@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
(pulled in the gnome.org eclass ass a necessary dependancy)
Upgraded dev-util/gdbus-codegen to version 2.30.2 on x86
BUG=chromium-os:24927
TEST=emerge gdbus-codegen. emerge various gnome2 packages we build and
confirm that the same files are installed.
Change-Id: Ic499a75eb55d8bec3e3ea0f1dcf68512c7b41220
Reviewed-on: https://gerrit.chromium.org/gerrit/14063
Commit-Ready: Nathan J. Williams <njw@chromium.org>
Tested-by: Nathan J. Williams <njw@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
If we're generating new breakpad symbols, we don't need to keep the
old ones around. Keeping the old ones forever means the debug tarballs
get really large (e.g. >10GB).
This problem makes incremental bots get slower and slower over time. The
chromium.chromiumos bot spends over an hour archiving the debug symbols,
for example.
BUG=chromium-os:24994
TEST=Trybot run of archive stage, generating and uploading debug
symbols.
Change-Id: Ibf57db2561d29085434439ecd4f23e5cec1f598a
Reviewed-on: https://gerrit.chromium.org/gerrit/14040
Commit-Ready: David James <davidjames@chromium.org>
Reviewed-by: David James <davidjames@chromium.org>
Tested-by: David James <davidjames@chromium.org>
BUG=None
TEST=emerge-arm-generic glib
Change-Id: Id66273090e80d254961d90c354d567d84d40dc24
Reviewed-on: https://gerrit.chromium.org/gerrit/14000
Tested-by: Nathan J. Williams <njw@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Nathan J. Williams <njw@chromium.org>
Upgraded dev-libs/glib to version 2.30.2-r1 on x86
BUG=chromium-os:24927
TEST=Build; compile modemmanager-next
Change-Id: I45112c988302a7d055d520d1a3bb07cbaa716293
Reviewed-on: https://gerrit.chromium.org/gerrit/13981
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Nathan J. Williams <njw@chromium.org>
Tested-by: Nathan J. Williams <njw@chromium.org>
There was no reason for it to be platform-specific. Original CL
that added it to ARM (it was already there for x86) is:
<http://gerrit.chromium.org/gerrit/1467>
This change is in preparation for moving platform-specific bits
into ebuilds.
BUG=chromium-os:24808
TEST=Validated that kern_guid gets set properly.
Change-Id: I5544ad3730e05128c0a9b0a4a3a8aee80ef31df5
Reviewed-on: https://gerrit.chromium.org/gerrit/13821
Tested-by: Doug Anderson <dianders@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Reviewed-by: Mandeep Singh Baines <msb@chromium.org>
Commit-Ready: Doug Anderson <dianders@chromium.org>
BUG=chromium-os:24763
TEST=emerge bluez-hcidump
CQ-DEPEND=Ie656a16f6f6bafc134910a59db4ff203f39766b1
Change-Id: Ia59645a86d1d7bb77ff8003c40fa4a6f0101033f
Reviewed-on: https://gerrit.chromium.org/gerrit/13737
Reviewed-by: Scott James Remnant <keybuk@chromium.org>
Tested-by: Scott James Remnant <keybuk@chromium.org>
Commit-Ready: Scott James Remnant <keybuk@chromium.org>
Minor bit of code cleanup, switch to gpl-v3.
BUG=chromium-os:24202
TEST=`emerge gperf` # host only
Change-Id: Icd1c5af0ae8b2f8dcbde426c7e7367c0c1ebcc19
Reviewed-on: https://gerrit.chromium.org/gerrit/13404
Tested-by: Brian Harring <ferringb@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Brian Harring <ferringb@chromium.org>
Upgraded dev-db/freetds to version 0.91 on x86
BUG=chrome-os-partner:7426
TEST=emerge-stumpy freetds; emerge-stumpy pymssql
Change-Id: I6d4df4eea5b147e24d3656471ffec3c9ef9687d8
Reviewed-on: https://gerrit.chromium.org/gerrit/13793
Tested-by: Hung-Te Lin <hungte@chromium.org>
Reviewed-by: Jay Kim <yongjaek@chromium.org>
Tested-by: Jay Kim <yongjaek@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Tested-by: <jongpil19.jung@samsung.com>
Commit-Ready: Hung-Te Lin <hungte@chromium.org>
Main fix is argument parsing issues, and fixing a staleness issue
in -prune's usage of stat()
Note this version is enabled via I745f8c82f4062aa1f46fe697a1b2c917ec9f5cc4
BUG=chromium-os:24206
TEST=`emerge findutils` # host only...
Change-Id: I8196ba2d848fea311dacdf958da3a7735ed3fe75
Reviewed-on: https://gerrit.chromium.org/gerrit/13406
Tested-by: Brian Harring <ferringb@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Brian Harring <ferringb@chromium.org>
Specifically, this gets us onto the gentoo fork getting us fixes
and general sanity.
BUG=chromium-os:24193
TEST=`emerge -1 rpm2targz` # host only package.
Change-Id: Ide76f57c42c06e4afb785ac29641b1ee8d9d9a78
Reviewed-on: https://gerrit.chromium.org/gerrit/13405
Tested-by: Brian Harring <ferringb@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Primary change is a switch to EAPI4, largefile support, and
decompression related fixes.
BUG=chromium-os:24191
TEST=`emerge cabextract` # it's a host package only
Change-Id: I7d33f76fa2e321fee29ad6363704325ce23ec983
Reviewed-on: https://gerrit.chromium.org/gerrit/13399
Tested-by: Brian Harring <ferringb@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
pulls in contrib scripts, fixed buffer overflow, better hardlink handling.
BUG=chromium-os:24203
TEST=`emerge rsync` # required by portage, used only in host.
Change-Id: Idb46f02c7e316dc10b8ad67f2b5d9dde28115bf2
Reviewed-on: https://gerrit.chromium.org/gerrit/13398
Tested-by: Brian Harring <ferringb@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Brian Harring <ferringb@chromium.org>
Now that emerge supports the flags needed to build packages, we don't
need to special-case it anymore.
BUG=chromium-os:24497
TEST=Trybot run.
Change-Id: I4ca1cd22c309f97fc14f1d7b9eede9128b7f0be1
Reviewed-on: https://gerrit.chromium.org/gerrit/13389
Reviewed-by: Brian Harring <ferringb@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Tested-by: David James <davidjames@chromium.org>
Commit-Ready: David James <davidjames@chromium.org>
BUG=chromium-os:24198
TEST=`emerge -1 gentoo-bashcomp` # host only
TEST=tool around the terminal in it.
Change-Id: If61cb76921eb314ac165da2b483b771c18a864e2
Reviewed-on: https://gerrit.chromium.org/gerrit/13407
Tested-by: Brian Harring <ferringb@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Brian Harring <ferringb@chromium.org>
Support for VPATH builds, and general unittext improvements
BUG=chromium-os:24199
TEST=`emerge -1 popt` # host only pkg
Change-Id: Ibebe2b2c2e1c167a651da6fb099275c2f7fc0c14
Reviewed-on: https://gerrit.chromium.org/gerrit/13403
Tested-by: Brian Harring <ferringb@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Brian Harring <ferringb@chromium.org>
This primarily pulls in a security fix in that landed in 2.11.
BUG=chromium-os:24192
TEST=`emerge cpio` # host only package.
Change-Id: Iad6102e80ababd5bce2ecae0da3f48f5daf949e2
Reviewed-on: https://gerrit.chromium.org/gerrit/13401
Tested-by: Brian Harring <ferringb@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Brian Harring <ferringb@chromium.org>
No real change; gets us a static-lib use flag primarily.
BUG=chromium-os:24190
TEST=`emerge bzip` # it's a host package only.
TEST=`build_packages x86-alex`
Change-Id: Ibd5c9e90e177f4198ae00c38266c5325503c9246
Reviewed-on: https://gerrit.chromium.org/gerrit/13400
Tested-by: Brian Harring <ferringb@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Brian Harring <ferringb@chromium.org>
Not everyone got a smooth migration for git/subversion from dev-util
to dev-vcs, so add a hook to manually unmerge the old versions. The
newer packages should recover gracefully after that.
BUG=chromium-os:24360
TEST=build_packages ran ver 23 upgrade and continued on
Change-Id: I0b56f0f0a8b8a7ebd64a4a664e5524f0b7828791
Reviewed-on: https://gerrit.chromium.org/gerrit/13663
Reviewed-by: Doug Anderson <dianders@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Doug Anderson <dianders@chromium.org>
This comes from not correctly negating all FLAGS and also the weird
way we set PRISTINE_IMAGE_NAME. Addressed in both cases and
simplified FLAGS_* logic in build_image_util.sh
BUG=chromium-os:24627
TEST=build_image base so far.
Change-Id: I92e8550db3ea713cda1f997b702777035145d8d5
Reviewed-on: https://gerrit.chromium.org/gerrit/13636
Tested-by: Chris Sosa <sosa@chromium.org>
Reviewed-by: Mandeep Singh Baines <msb@chromium.org>
Commit-Ready: Chris Sosa <sosa@chromium.org>
3.2.2 -> 3.4.4; support for dpkg format version 3.9.1, XZ compression,
BUG=chromium-os:24205
TEST=`emerge debianutils` # host only package
Change-Id: If83ac3ee08559a1874ecf903ec35ea101cd8c843
Reviewed-on: https://gerrit.chromium.org/gerrit/13408
Tested-by: Brian Harring <ferringb@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
"-fstack-protector-all".
Rollout gcc-4.6.0 ebuild r12 that support a new stack protection
option "-fstack-protector-strong".
BUG=None
TEST=manually - build amd64-generic and x86-zgb from scratch.
Change-Id: I35dc315ef376467256266a62cf9e584b8bb3c8e5
Reviewed-on: https://gerrit.chromium.org/gerrit/13546
Tested-by: Han Shen <shenhan@google.com>
Reviewed-by: Han Shen <shenhan@chromium.org>
Reviewed-by: asharif <asharif@chromium.org>
Commit-Ready: Han Shen <shenhan@chromium.org>
This CL addes media-libs/opencv 2.3.0 to x86. It will be used in various
factory tests for computer vision related tasks.
BUG=chrome-os-partner:6497
TEST='emerge-x86-alex opencv' works
Change-Id: Icb7b8592c448ad14df470d1ab1138adc896230ed
Reviewed-on: https://gerrit.chromium.org/gerrit/13529
Reviewed-by: Hung-Te Lin <hungte@chromium.org>
Tested-by: Tai-Hsu Lin <sheckylin@chromium.org>
Commit-Ready: Tai-Hsu Lin <sheckylin@chromium.org>
