We want to use the updated version for all targets and not just x86.
BUG=None
TEST=`emerge-amd64-generic gpsd` works
TEST=`emerge-arm-generic gpsd` works
TEST=`emerge-x86-generic gpsd` works
Change-Id: I5283585452b344bb39ffe3bc614ea5a6369199ac
Reviewed-on: https://gerrit.chromium.org/gerrit/13387
Reviewed-by: Yufeng Shen <miletus@chromium.org>
Tested-by: Yufeng Shen <miletus@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
This includes a few more fixes including the one for parallel building
the pdfmark subdir.
BUG=chromium-os:24481
TEST=`emerge groff` works
Change-Id: I16c110b0421b1ae8889517893495d6cf84cc345b
Reviewed-on: https://gerrit.chromium.org/gerrit/13351
Reviewed-by: David James <davidjames@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
update to valgrind-3.6.1-r1 because the current version doesn't work
with glibc-2.11
BUG=none
TEST=emerge-$board valgrind
Change-Id: I59a0a6c095edd3cdb8efdd4d4988906b80147952
Reviewed-on: https://gerrit.chromium.org/gerrit/13344
Commit-Ready: Jason Glasgow <jglasgow@chromium.org>
Reviewed-by: Jason Glasgow <jglasgow@chromium.org>
Tested-by: Jason Glasgow <jglasgow@chromium.org>
If people have whitespace in their .default_board setting, then the cros
utils will act weirdly. Some work the same as if there was no whitespace
(probably because the variable is used unquoted) while others error out
with weird messages (because the variable is used quoted).
Update the helper function to only allow certain characters in the name.
BUG=None
TEST=`printf 'x86-alex\n' > .default_board; cros_workon list --all` works
TEST=`printf 'x86-alex\t\n' > .default_board; cros_workon list --all` errors out
Change-Id: Id83794c13bfddb7fb56b7f8ed8a375eefe6096e0
Reviewed-on: https://gerrit.chromium.org/gerrit/13151
Reviewed-by: Jason Glasgow <jglasgow@chromium.org>
Reviewed-by: David James <davidjames@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
We don't actually use any cvs packages, but some of the ebuilds/eclasses
(like git) indirectly and optionally depend on cvs, so update them for
the category migration (dev-util -> dev-vcs).
BUG=chromium-os:24360
TEST=`emerge cvs && cvs -d:pserver:anonymous@anoncvs.gentoo.org:/var/cvsroot -q co -R gentoo-projects/portage-utils` works
Change-Id: I642839bb357e836d8be29595349a9d8890a804eb
Reviewed-on: https://gerrit.chromium.org/gerrit/13145
Reviewed-by: Zdenek Behan <zbehan@chromium.org>
Reviewed-by: David James <davidjames@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
The current version of strace we're using doesn't build with newer
kernel headers. So pull down the latest stable from Gentoo for it.
BUG=chromium-os:14334
TEST=`emerge strace` works
TEST=`emerge-amd64-generic strace` works
TEST=`emerge-arm-generic strace` works
TEST=`emerge-x86-generic strace` works
Change-Id: I3d615743f751dc2cb297742dc64670a1cae8967e
Reviewed-on: https://gerrit.chromium.org/gerrit/13125
Reviewed-by: David James <davidjames@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
BUG=chromium-os:14334
TEST=`emerge sys-kernel/linux-headers` now pulls in version 3.1 & works
TEST=`emerge cross-armv7a-cros-linux-gnueabi/linux-headers` now pulls in version 3.1 & works
TEST=`emerge cross-i686-pc-linux-gnu/linux-headers` now pulls in version 3.1 & works
TEST=`emerge cross-x86_64-cros-linux-gnu/linux-headers` now pulls in version 3.1 & works
TEST=`cbuildbot chromiumos-sdk` worked
TEST=`cbuildbot amd64-generic-full` passes
TEST=`cbuildbot arm-generic-full` passes
TEST=`cbuildbot x86-generic-full` passes
TEST=build_packages+build_image for x86-alex boots
CQ-DEPENDS=13082
Change-Id: I20460c174570ff004be14e82863aab316a1fb572
Reviewed-on: https://gerrit.chromium.org/gerrit/13083
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
We need a newer version for newer linux-headers. That is the only
package that uses this eclass, so not much to test here.
BUG=chromium-os:14334
TEST=`emerge sys-kernel/linux-headers` still works
TEST=`emerge cross-armv7a-cros-linux-gnueabi/linux-headers` still works
TEST=`emerge cross-i686-pc-linux-gnu/linux-headers` still works
TEST=`emerge cross-x86_64-cros-linux-gnu/linux-headers` still works
TEST=`cbuildbot chromiumos-sdk` worked
TEST=`cbuildbot amd64-generic-full` passes
TEST=`cbuildbot arm-generic-full` passes
TEST=`cbuildbot x86-generic-full` passes
TEST=build_packages+build_image for x86-alex boots
Change-Id: Ia58fe044f7ed6fff4fa4a0f4d9c40f9b46ee7bb4
Reviewed-on: https://gerrit.chromium.org/gerrit/13081
Reviewed-by: David James <davidjames@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Mostly cosmetic changes here, but kernel_is gets optimized a bit.
Very few packages actually use this eclass. Mostly updating this
so we can pull in a newer kernel-2.eclass.
BUG=chromium-os:14334
TEST=`emerge fuse udev qemu-kvm` still works
TEST=`cbuildbot chromiumos-sdk` worked
TEST=`cbuildbot amd64-generic-full` passes
TEST=`cbuildbot arm-generic-full` passes
TEST=`cbuildbot x86-generic-full` passes
TEST=build_packages+build_image for x86-alex boots
Change-Id: I9e3a1c901f2efaf32caadfd7ed909a339bb8342d
Reviewed-on: https://gerrit.chromium.org/gerrit/13080
Reviewed-by: David James <davidjames@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Upstream has moved from the legacy virtuals file with os-headers to the
new style. We need to migrate as well to use newer packages.
BUG=chromium-os:14334
TEST=`cbuildbot chromiumos-sdk` worked
TEST=`cbuildbot amd64-generic-full` passes
TEST=`cbuildbot arm-generic-full` passes
TEST=`cbuildbot x86-generic-full` passes
TEST=build_packages+build_image for x86-alex boots
Change-Id: I292e34a013f8b12dc52fc83581922c337785b326
Reviewed-on: https://gerrit.chromium.org/gerrit/13076
Reviewed-by: David James <davidjames@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
While we do use sysroot_wrapper bits in the chroot, we do not
use the target of this symlink (nor do we want it in our PATH).
BUG=chromium-os:24111
TEST=cbuildbot x86-alex
Change-Id: I7cf44ac32494dfaac683a4442d30f278bbcfb38c
Reviewed-on: https://gerrit.chromium.org/gerrit/13065
Tested-by: Brian Harring <ferringb@chromium.org>
Reviewed-by: David James <davidjames@chromium.org>
Commit-Ready: Brian Harring <ferringb@chromium.org>
Our local copy of gdbm just disables the compat library install (due to
cross-compiling issues). While the newer version has that issue fixed,
it also has a USE flag to disable the compat library. Since we don't
use it for the target, let's switch to the upstream version and disable
building of th compat code for the target.
BUG=chromium-os:24038
TEST=`emerge gdbm perl ruby` still works
TEST=`emerge grub` still works (only package that uses ruby)
TEST=`emerge $(qlist -I dev-perl)` still works (all the local perl modules)
TEST=`emerge-amd64-generic gdbm` still works
TEST=`emerge-arm-generic gdbm` still works
TEST=`emerge-x86-generic gdbm` still works
CQ-DEPENDS=13007
Change-Id: I04fd2aef943a1c28771973b1a93eb251b69630b5
Reviewed-on: https://gerrit.chromium.org/gerrit/13009
Reviewed-by: David James <davidjames@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
This change makes it possible for partners to access internal prebuilts.
Note that partners will only have access to the actual prebuilts referenced
here if they have access to the right Google Storage key, which are stored
in the overlays themselves.
BUG=chrome-os-partner:7186, chromium-os:17346
TEST=Verify that setup_board now pulls internal prebuilts from chromeos-partner-overlay
instead of chromeos-overlay.
CQ-DEPEND=13071
Change-Id: Ia5220002a18593e614ee67ccad16bb295c8b6d0b
Reviewed-on: https://gerrit.chromium.org/gerrit/13072
Reviewed-by: Ryan Cui <rcui@chromium.org>
Tested-by: David James <davidjames@chromium.org>
Our local copy of gd just contains a cross-compile fix which has been
redone upstream. So import that to drop our local copy.
Note: no board tests have been done as this package doesn't seem to
get used anywhere that I can see.
BUG=chromium-os:24041
TEST=`emerge gd` works
TEST=`emerge-arm-generic gd` works
TEST=`emerge-amd64-generic gd` works
TEST=`emerge-x86-generic gd` works
Change-Id: I59e721717fb477b3adbda255d5cccea38159d333
Reviewed-on: https://gerrit.chromium.org/gerrit/12988
Reviewed-by: David James <davidjames@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Our local copy of socat just contains a cross-compile hack which has been
redone upstream. So import that to drop our local copy.
I don't seem to have any hardware with a modem that socat can talk to,
but basic network transactions work for me.
BUG=chromium-os:24037
TEST=`emerge socat` works
TEST=`emerge-arm-generic socat` works
TEST=`emerge-amd64-generic socat` works
TEST=`emerge-x86-generic socat` works
TEST=`socat stdio tcp-l:12345` on the board connects with `nc <board>:12345` on desktop
Change-Id: I1beb292a1e3aed09b945d187607b4dbe298459ea
Reviewed-on: https://gerrit.chromium.org/gerrit/13001
Reviewed-by: David Rochberg <rochberg@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
The version in the cros overlay was to backport only certain commits
from upstream Gentoo in order to push out a new glibc version asap
while avoiding any possible regressions. Now's a good time to merge
the latest eclass version though and go through the qualification.
BUG=None
TEST=`cbuildbot chromiumos-sdk` worked
TEST=`cbuildbot arm-generic-full` passes
TEST=`cbuildbot x86-generic-full` passes
Change-Id: I6f3598bbc1a202376acd5227abab7d88c4d6b0c4
Reviewed-on: https://gerrit.chromium.org/gerrit/12979
Reviewed-by: David James <davidjames@chromium.org>
Reviewed-by: asharif <asharif@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
We have a local autotools.eclass just to add an additional -I flag when
running aclocal. Upstream Gentoo eclass has added a new variable which
gets us the same functionality. Pull in the new eclass!
Since the new autotools.eclass relies on new functionality from the
libtool.eclass, pull that in too.
BUG=chromium-os:24162
TEST=`cbuildbot arm-generic-full` passes
CQ-DEPENDS=12867
Change-Id: I86e485272c0c03cdcc5cd6cdc9812e517d08e80e
Reviewed-on: https://gerrit.chromium.org/gerrit/12869
Reviewed-by: David James <davidjames@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
My cbuildbot run is creating this file. I don't care about it -> ignore!
BUG=None
TEST=`git status` no longer lists cbuildbot_package.list
Change-Id: I95ac49c84d628fbb52dda8f1df63ab6394e5df8f
Reviewed-on: https://gerrit.chromium.org/gerrit/12957
Reviewed-by: David James <davidjames@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
This eclass wasn't modified when importing, so move it to the
portage-stable overlay.
BUG=None
TEST=`emerge vim` works
TEST=`emerge-amd64-generic vim` works
TEST=`emerge-arm-generic vim` works
TEST=`emerge-x86-generic vim` works
Change-Id: Ia2864b5ac6173734e0e4a32afebd13cf139593a3
Reviewed-on: https://gerrit.chromium.org/gerrit/12918
Reviewed-by: David James <davidjames@chromium.org>
Reviewed-by: Matt Tennant <mtennant@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
The upstream ebuild added a build time patch so it works with newer
versions of curl (due to curl/types.h being removed). Otherwise,
this is the same ebuild as we already have in the portage/ overlay.
This fixes the chromiumos-sdk buildbot which builds everything from
source and so is the only thing to notice this error so far.
BUG=None
TEST=`emerge xmlrpc-c` now works
Change-Id: I5e1b2a05b9491435b1fafe9bf538ef1a6f4228b7
Reviewed-on: https://gerrit.chromium.org/gerrit/12919
Reviewed-by: David James <davidjames@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Looks like there was a desync between adding gdb support and arm-eabi
support. We don't provide gdb for the arm-eabi toolchain, so don't
consider it when looking for updates. Otherwise we end up constantly
re-installing the arm-eabi toolchain because there are "updates".
BUG=None
TEST=setup_board for x86-alex stops re-installing the arm-eabi toolchain everytime
Change-Id: I099bc6a411b6cacdd3d7cdd5e4eb872a937678bd
Reviewed-on: https://gerrit.chromium.org/gerrit/12905
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
The CL upgrades dev-util/cmake to version 2.8.4-r1 on amd64. The
update is necessary because I need to compile a library (OpenCV)
for a factory test. Besides that, the current version (2.6.4) is
more than 2 years old and therefore worthwhile for an upgrade.
A corresponding CL on the keywords file will be carried out before
this one.
BUG=chromium-os:23747
TEST='emerge cmake' still works
Change-Id: I29154af89d373297d692f70c77a35cbdd2da5737
Reviewed-on: https://gerrit.chromium.org/gerrit/12484
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Tested-by: Tai-Hsu Lin <sheckylin@chromium.org>
Commit-Ready: Tai-Hsu Lin <sheckylin@chromium.org>
Due to historical reasons, these scripts have existed at
chromiumos-overlay/chrome/scripts, but have belonged
in src/scripts (previously accessed by symlinks here
pointing to their locations).
Transfer them in, rather than relying on symlinks; this
gets us atomic commits w/in crosutils in the process.
Scripts were imported as of 604e3722af59164bc97aa5dcd1407e36495c96d7
BUG=chromium-os:24111
TEST=cbuildbot x86-generic-full
Change-Id: I689f7e05a25d427e24372f206bdb0779bf857820
Reviewed-on: https://gerrit.chromium.org/gerrit/12893
Reviewed-by: David James <davidjames@chromium.org>
Commit-Ready: Brian Harring <ferringb@chromium.org>
Tested-by: Brian Harring <ferringb@chromium.org>
The masters ordering specified here doesn't actually work, nor
reflect reality (portage always uses the local eclasses over
any masters if there is a conflict).
As such, remove the pointless entry. Portage trunk has a fix
for this, but we should enforce what we use /now/ so that a
later portage upgrade doesn't accidentaly flip the behaviour
around on us; changing the ordering should be an explicit
decision/change rather than portage upgrade.
For testing, check the before/after; note that portage-stable
eclasses still are rightmost in either, thus are what's used.
BUG=None
TEST=python -c $'if True:
import portage
r=portage.settings.repositories;r=r.get_repo_for_location(r.treemap[u"portage-stable"])
print r.eclass_locations'
Change-Id: I18c5e7e647557da1030094668502467427e56fae
Reviewed-on: https://gerrit.chromium.org/gerrit/12866
Reviewed-by: David James <davidjames@chromium.org>
Commit-Ready: Brian Harring <ferringb@chromium.org>
Tested-by: Brian Harring <ferringb@chromium.org>
Grab the latest stable version from upstream. Current stable likes to
reject certain patches, so just update and be done with it.
BUG=chromium-os:24046
TEST=`emerge patch` works
TEST=`cbuildbot x86-generic-full` works
TEST=build_packages+build_image for alex boots
Change-Id: I3011e78e7ebb273e7641a3023fe5d8ffb26e04bf
Reviewed-on: https://gerrit.chromium.org/gerrit/12786
Reviewed-by: David James <davidjames@chromium.org>
Reviewed-by: Matt Tennant <mtennant@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Grab the latest stable version from upstream.
BUG=chromium-os:24046
TEST=`emerge net-tools` works
TEST=`emerge-amd64-generic net-tools` works
TEST=`emerge-arm-generic net-tools` works
TEST=`emerge-x86-generic net-tools` works
TEST=build_packages+build_image for alex boots and can get online
Change-Id: I57947af920dd93c5c9b09d98acb0d6272bf87f48
Reviewed-on: https://gerrit.chromium.org/gerrit/12769
Reviewed-by: David James <davidjames@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
On long running systems, the ssh-agent dir might go stale. This should
not prevent entering the cros chroot though, so skip it if it's invalid.
BUG=None
TEST=`cros_sdk` enters with ssh-agent dir bind mounted
TEST=`rm -rf /tmp/ssh-*/; cros_sdk` enters with ssh-agent dir skipped
Change-Id: I923b031612c0d37a896437c7355cac6c448eef82
Reviewed-on: https://gerrit.chromium.org/gerrit/12758
Reviewed-by: David James <davidjames@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
BUG=chromium-os:23903
TEST=full build of x86-zgb, mod_for_test, boot; run dbus-monitor
on tty2 as root, log in, switch back and observe all the dbus
traffic.
Change-Id: Iccdb47bec97260108c73cf346c91c2d9e8c2bc18
Reviewed-on: https://gerrit.chromium.org/gerrit/12593
Commit-Ready: Jim Hebert <jimhebert@chromium.org>
Reviewed-by: Jim Hebert <jimhebert@chromium.org>
Tested-by: Jim Hebert <jimhebert@chromium.org>
This solves two problems (and half):
a) messing with user's preference file is a no-no, if we want a
hardcoded behaviour like this, profile.d is the way to go
b) .bashrc settings are overridden when doing env-update; source
/etc/profile
c) profile.d will also apply to root (although not with sudo su)
BUG=none
TEST=below
1) ./run_chroot_version_hooks --version 21
2) see all fixed, source /etc/profile, and still see my prompt unchanged
Change-Id: I25b4602f4951b17815bcd312a8249320784c67e1
Reviewed-on: https://gerrit.chromium.org/gerrit/12539
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Tested-by: Zdenek Behan <zbehan@chromium.org>
Commit-Ready: Zdenek Behan <zbehan@chromium.org>
* Since dm-verity arguments are now read from the install image upon
recovery, we need not use them in build_kernel_image.
* Also, don't expect or remove /tmp/rootfs.hash, which will not be
generated by build_kernel_image.
* Cleanup of dead code following the elimination of use of root_dev.
* Updated ASCII art for success/failure condition.
* See corresponding changes to initramfs script (extract verity args
from install kernel) and chromeos-initramfs ebuild (pull
dump_kernel_config).
BUG=chromium-os:22530
TEST=Built and successfully installed recovery image on CR-48
Change-Id: I3536c88537bbce277f79f17b676231b67337a0d1
Reviewed-on: https://gerrit.chromium.org/gerrit/12646
Reviewed-by: Gilad Arnold <garnold@chromium.org>
Tested-by: Gilad Arnold <garnold@chromium.org>
Commit-Ready: Gilad Arnold <garnold@chromium.org>
This reverts commit 99182997f90041870db9038837c04be973999800
CL was committed unintentionally; it depends on two other CLs that were not committed yet.
Change-Id: Ica5820b31d7f6857c0553cedb642ee17f5109da9
Reviewed-on: https://gerrit.chromium.org/gerrit/12587
Commit-Ready: Gilad Arnold <garnold@chromium.org>
Reviewed-by: Gilad Arnold <garnold@chromium.org>
Tested-by: Gilad Arnold <garnold@chromium.org>
* Since dm-verity arguments are now read from the install image upon
recovery, we need not use them in build_kernel_image.
* Also, don't expect or remove /tmp/rootfs.hash, which will not be
generated by build_kernel_image.
* Cleanup of dead code following the elimination of use of root_dev.
* Updated ASCII art for success/failure condition.
* See corresponding changes to initramfs script (extract verity args
from install kernel) and chromeos-initramfs ebuild (pull
dump_kernel_config).
BUG=chromium-os:22530
TEST=Built and successfully installed recovery image on CR-48
Change-Id: I146b6ad707d96c9fbc8731a73ae079e80902a565
Reviewed-on: https://gerrit.chromium.org/gerrit/12335
Reviewed-by: Richard Barnette <jrbarnette@chromium.org>
Tested-by: Gilad Arnold <garnold@chromium.org>
Gpsd can use TCP socket to communicate with client applications,
which poses security risks. When configured for ChromeOS, the
socket export should be disabled and shared memory export should
be used to communicate with Chrome. See the TEST section for
example configuration.
BUG=None
TEST=$ emerge-x86-generic gpsd
TEST=$ USE="$USE -sockets" emerge-x86-alex gpsd
and make sure gpsd-3.3 is emerged
on the device, run
$ gpsd -D 1 /dev/ttyUSB2
and make sure gpsd is running as daemon
$ netstat | grep gpsd
and make sure gpsd can't be found (so that gpsd is not
listening on any TCP socket port)
Change-Id: I8d9d98aa62cf5fc605f79b28467b8c37178bc298
Reviewed-on: https://gerrit.chromium.org/gerrit/12567
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Yufeng Shen <miletus@chromium.org>
Tested-by: Yufeng Shen <miletus@chromium.org>
Since we no longer need the local build hacks, we can move to the
upstream Gentoo ebuilds.
BUG=chromium-os:23786
TEST=`emerge-amd64-generic iproute2` works
TEST=`emerge-arm-generic iproute2` works
TEST=`emerge-x86-generic iproute2` works
Change-Id: I1c03eb9b36dc1b1f3d94a2e0e33cac498e29e3eb
Reviewed-on: https://gerrit.chromium.org/gerrit/12465
Reviewed-by: Daniel Kurtz <djkurtz@chromium.org>
Reviewed-by: David James <davidjames@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
The only reason we have bash in the cros overlay is so that we have it
not install a /bin/sh symlink pointing to bash in the board root. Once
we move that handling to chromeos-base, we can drop all the bash ebuild
customizations.
BUG=chromium-os:21901
TEST=`emerge chromeos-base bash` and see /bin/sh -> bash
TEST=`emerge-amd64-generic chromeos-base dash` and see /bin/sh -> dash
TEST=`emerge-arm-generic chromeos-base dash` and see /bin/sh -> dash
TEST=`emerge-x86-generic chromeos-base dash` and see /bin/sh -> dash
Change-Id: I1df4a75ac314ed308817b4cdf61564ac0174ad63
Reviewed-on: https://gerrit.chromium.org/gerrit/11409
Reviewed-by: David James <davidjames@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
The only reason we have dash in the cros overlay is so that we can install
a /bin/sh symlink pointing to dash in the board root. Once we move that
symlink to chromeos-base, we can drop all the dash customizations.
BUG=chromium-os:21901
TEST=`emerge chromeos-base bash` and see /bin/sh -> bash
TEST=`emerge-amd64-generic chromeos-base dash` and see /bin/sh -> dash
TEST=`emerge-arm-generic chromeos-base dash` and see /bin/sh -> dash
TEST=`emerge-x86-generic chromeos-base dash` and see /bin/sh -> dash
Change-Id: Iaec86219ad64d086e261187e6f7c3436eb7890cd
Reviewed-on: https://gerrit.chromium.org/gerrit/11408
Reviewed-by: David James <davidjames@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
The newer ncurses includes fun pkg-config files which other packages
can now use instead of the crappy ncurses5-config scripts.
For example, newer gpsd ebuilds will utilize these .pc files.
BUG=chromium-os:467
TEST=`emerge ncurses` works
TEST=`emerge-amd64-generic ncurses` works
TEST=`emerge-arm-generic ncurses` works
TEST=`emerge-x86-generic ncurses` works
TEST=build_packages+build_image for x86-alex boots up
Change-Id: Ib084c0e219be14622b5e38c6c2ae552368273bb5
Reviewed-on: https://gerrit.chromium.org/gerrit/12393
Reviewed-by: David James <davidjames@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Some core eclasses were updated recently (notably eutils), so regenerate
the cache manually to take that into account.
BUG=None
TEST=build_packages works for x86-alex
Change-Id: Ia06d9697d29b185d2bb859049dba73df3010276f
Reviewed-on: https://gerrit.chromium.org/gerrit/12390
Reviewed-by: David James <davidjames@chromium.org>
Reviewed-by: Brian Harring <ferringb@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
This reverts commit 84b6463197a21a16cf1f3ce70cafaed32a979057.
BUG=chromium-os:21244
TEST=build grub and see new grub installed (after related unmasking in chromiumos-overlay)
Change-Id: I57f1a63baee9667cb4907975abef736c1dfb4622
Reviewed-on: https://gerrit.chromium.org/gerrit/12255
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Reviewed-by: David James <davidjames@chromium.org>
Tested-by: Anush Elangovan <anush@chromium.org>
Commit-Ready: Anush Elangovan <anush@chromium.org>
I got antsy and merged gtest into the portage-stable repo before I
should have, so now upgrading gmock/glog fails because the config
wrapper from gtest doesn't get wrapped with existing installs.
(See commit 2cfb1bfb4742e917d4d7e629 in the chromiumos overlay).
Force everyone to upgrade so the hook fires and wraps the script.
BUG=chromium-os:21276
TEST=`emerge gtest gmock glog` still works
Change-Id: I9137b3e9367040fe6a078499ddedcfe41a34df69
Reviewed-on: https://gerrit.chromium.org/gerrit/12333
Reviewed-by: David James <davidjames@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
The upstream Gentoo version of the glog ebuild should cover all our
existing needs.
BUG=chromium-os:21276
TEST=`emerge-arm-generic glog` works w/out -I/-L hacks
TEST=`emerge-x86-generic glog` still works
TEST=`emerge glog` still works
Change-Id: I4af4ab4f2e8319a97f9315d4b3dc6dff857fdeee
Reviewed-on: https://gerrit.chromium.org/gerrit/11579
Reviewed-by: David James <davidjames@chromium.org>
Reviewed-by: Raymes Khoury <raymes@chromium.org>
Reviewed-by: Matt Tennant <mtennant@chromium.org>
Reviewed-by: Chris Wolfe <cwolfe@chromium.org>
Reviewed-by: Vince Laviano <vlaviano@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
The upstream Gentoo version of the gmock ebuild should cover all our
existing needs, but it also includes some build fixes which make cross
compiling work nicely (running elibtoolize).
BUG=chromium-os:21276
TEST=`emerge-arm-generic gmock` works w/out -I/-L hacks
TEST=`emerge-x86-generic gmock` still works
TEST=`emerge gmock` still works
Change-Id: I10176d5eff98b7dfb4e0294409969ad36f90715d
Reviewed-on: https://gerrit.chromium.org/gerrit/11578
Reviewed-by: David James <davidjames@chromium.org>
Reviewed-by: Raymes Khoury <raymes@chromium.org>
Reviewed-by: Chris Wolfe <cwolfe@chromium.org>
Reviewed-by: Vince Laviano <vlaviano@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Newer versions of util-linux's mount utility will not show:
/dev/loop0 on /some/path type ext3 (mount,opts)
Instead, it finds out the file backing /dev/loop0 and outputs:
/some/file on /some/path type ext3 (mount,opts)
This breaks the make_image_bootable helper that attempts to look up the
loop device that mount_gpt_image.sh happened to pick.
Let's scuttle the idea of parsing `mount` and move directly to what the
kernel has to say via /proc/mounts. Hopefully the ABI there should be
quite a bit more stable.
BUG=None
TEST=build_image works with mount from util-linux-2.16
TEST=build_image (before change) fails with mount from util-linux-2.19
TEST=build_image works with mount from util-linux-2.19
Change-Id: I66908800e82ff2e106face9d57773721e400dc2a
Reviewed-on: https://gerrit.chromium.org/gerrit/11869
Commit-Ready: Mike Frysinger <vapier@chromium.org>
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
This is final step in ext4 conversion. We have been running with
the ext4 file system but ext3 format for several weeks. This changes
uses the ext4 format for the stateful partition.
Removed make_developer_script_runner.sh as per review.
BUG=chromium-os:20012
TEST=Ran ext4 on all platforms
Change-Id: I8e1564bfa576e9a0ad810879c18223a6c68b18e1
Reviewed-on: https://gerrit.chromium.org/gerrit/11220
Commit-Ready: Paul Taysom <taysom@google.com>
Reviewed-by: Paul Taysom <taysom@google.com>
Tested-by: Paul Taysom <taysom@google.com>
Upgraded net-dns/c-ares to version 1.7.5 on arm, x86.
This is step 1. Step 2 will be to enable 1.7.5 for arm, amd64, and x86,
in chromiumos-overlay/profiles/targets/chromeos/package.keywords.
BUG=chromium-os:22470
TEST=built x86-alex and arm-generic
Change-Id: I91c64972c8ac107cec75530e09ef977fc549db69
Reviewed-on: https://gerrit.chromium.org/gerrit/12315
Reviewed-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Jason Glasgow <jglasgow@chromium.org>
Reviewed-by: Jason Glasgow <jglasgow@chromium.org>
Tested-by: Jason Glasgow <jglasgow@chromium.org>
We're seeing some HZ warnings on ARM platforms due to a bug in the
internal procps init sequence. This has already been fixed in the
upstream Gentoo ebuild, so pull down the latest stable from there.
BUG=chromium-os:20777
TEST=`emerge procps` works
TEST=`emerge-amd64-generic procps` works
TEST=`emerge-arm-generic procps` works
TEST=`emerge-x86-generic procps` works
TEST=`cbuildbot arm-generic-full` works
TEST=`cbuildbot x86-generic-full` works
Change-Id: If635416e7e28ede1b60cf8067aa4f77aabb4a4d8
Reviewed-on: https://gerrit.chromium.org/gerrit/12000
Reviewed-by: David James <davidjames@chromium.org>
Tested-by: Mike Frysinger <vapier@chromium.org>
Commit-Ready: Mike Frysinger <vapier@chromium.org>
