From 33074475f90d545313a5b48e23f75f58c279f9b2 Mon Sep 17 00:00:00 2001 From: Michael Marineau Date: Wed, 15 Jul 2015 20:31:05 -0700 Subject: [PATCH] profiles: fix path to coreos-overlay Missed this reference to /usr/local/portage in a recent scripts change: https://github.com/marineam/coreos-scripts/commit/174a847e362f8a1d05210750eafb6ccb4735f59c So existing SDKs kept working but newly created SDKs would mysteriously fail to build some things like cmake and vim. :( --- .../coreos-overlay/profiles/coreos/base/profile.bashrc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/sdk_container/src/third_party/coreos-overlay/profiles/coreos/base/profile.bashrc b/sdk_container/src/third_party/coreos-overlay/profiles/coreos/base/profile.bashrc index 89a2bf4d48..3e4b812f6e 100644 --- a/sdk_container/src/third_party/coreos-overlay/profiles/coreos/base/profile.bashrc +++ b/sdk_container/src/third_party/coreos-overlay/profiles/coreos/base/profile.bashrc @@ -3,7 +3,7 @@ CROS_BUILD_BOARD_TREE="${SYSROOT}/build" CROS_BUILD_BOARD_BIN="${CROS_BUILD_BOARD_TREE}/bin" -CROS_ADDONS_TREE="/usr/local/portage/coreos/coreos" +CROS_ADDONS_TREE="/mnt/host/source/src/third_party/coreos-overlay/coreos" # Are we merging for the board sysroot, or for the cros sdk, or for # the target hardware? Returns a string: