bitbake.conf: unexport SHELL

The user's shell shouldn't be allowed to affect the build (and it can break
the flock command and possibly more, if the user's shell isn't POSIX
compliant).

(From OE-Core rev: fc5e1cfcc3ab7acfb6e7e12cb2cf7fa4699ae7b3)

(From OE-Core rev: 43a2baf26dad4b7b2f0e4c6af3ea4a611cee7ad5)

Signed-off-by: Christopher Larson <chris_larson@mentor.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>

1 files changed, 5 insertions, 0 deletions

diff --git a/meta/conf/bitbake.conf b/meta/conf/bitbake.conf
index c382c58b2d..aa785a13f3 100644
--- a/meta/conf/bitbake.conf
+++ b/meta/conf/bitbake.conf
@@ -763,6 +763,11 @@ TARGET_ARCH[unexport] = "1"
 # (breaks sysvinit at least)
 DISTRO[unexport] = "1"
 
+# Make sure SHELL isn't exported
+# (can break any number of things if the user's shell isn't POSIX-compliant,
+# including the flock command). The user's shell shouldn't affect our builds.
+SHELL[unexport] = "1"
+
 # Used by canadian-cross to handle string conversions on TARGET_ARCH where needed
 TRANSLATED_TARGET_ARCH ??= "${@d.getVar('TARGET_ARCH', True).replace("_", "-")}"