Fix MACHINE setting in start script

The current MACHINE setting could be different than when bitbake was
originally run, thus causing an error when the start scripts are run.
Set the MACHINE in each bitbake command call to get around this.

Change-Id: I778b58d751ea0ddbcac6d73f347e6861edcf1ecf
Signed-off-by: Jon Mason <jon.mason@arm.com>
This commit is contained in:
Jon Mason authored and Jon Mason committed 2020-03-08 22:53:59 -04:00
1 parent 11233ba158
commit ae19998d27
2 files changed
+2 -2

No files matched your search

@@ -5,7 +5,7 @@ set -u
set -e
# Get parameters from bitbake configuration
source <(bitbake -e foundation-armv8-native | grep \
source <(MACHINE=foundation-armv8 bitbake -e foundation-armv8-native | grep \
-e "^STAGING_.*_NATIVE=" \
-e "^DEPLOY_DIR.*=")
@@ -5,7 +5,7 @@ set -u
set -e
# Get parameters from bitbake configuration
source <(bitbake -e fvp-base-native | grep \
source <(MACHINE=fvp-base bitbake -e fvp-base-native | grep \
-e "^STAGING_.*_NATIVE=" \
-e "^DEPLOY_DIR.*=")