summaryrefslogtreecommitdiffstats
path: root/meta/files
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2015-09-29 13:43:45 +0100
committerRichard Purdie <richard.purdie@linuxfoundation.org>2015-10-01 07:43:32 +0100
commitffd4bd674477e096c66ebbcb504c7ce7c33b166d (patch)
treeb866b8b89b24f3aff6c66f7b70a349681809628d /meta/files
parent249b810501f69390e8074368009a1114dbfcfaff (diff)
downloadpoky-ffd4bd674477e096c66ebbcb504c7ce7c33b166d.tar.gz
toolchain-shar-extract: Correct environment-setup script names for multilib
Currently a lib32-core-image-* SDK prints an incorrect environment-setup-* file name when installing the SDK. Instead of printing the wrong thing, list the environment setup files present in the SDK. As it happens this fixes the message printed with buildtools-tarball too which someone reported to me about the same time as I finished this patch! (From OE-Core rev: c2fa59f46bbc86985e6c8e4d5d514a07a9ade884) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/files')
-rw-r--r--meta/files/toolchain-shar-extract.sh4
1 files changed, 3 insertions, 1 deletions
diff --git a/meta/files/toolchain-shar-extract.sh b/meta/files/toolchain-shar-extract.sh
index dd92d0eb7f..2ffc2d1c07 100644
--- a/meta/files/toolchain-shar-extract.sh
+++ b/meta/files/toolchain-shar-extract.sh
@@ -182,7 +182,9 @@ fi
182 182
183echo "SDK has been successfully set up and is ready to be used." 183echo "SDK has been successfully set up and is ready to be used."
184echo "Each time you wish to use the SDK in a new shell session, you need to source the environment setup script e.g." 184echo "Each time you wish to use the SDK in a new shell session, you need to source the environment setup script e.g."
185echo " \$ . $target_sdk_dir/environment-setup-@REAL_MULTIMACH_TARGET_SYS@" 185for env_setup_script in `ls $target_sdk_dir/environment-setup-*`; do
186 echo " \$ . $target_sdk_dir/$env_setup_script"
187done
186 188
187exit 0 189exit 0
188 190