From ea91b1dd878a5c726ee5118b98c4987fa0a994e7 Mon Sep 17 00:00:00 2001
From: Chris Larson <chris_larson@mentor.com>
Date: Tue, 14 Dec 2010 08:10:36 -0700
Subject: Fix PWD issue with new exec_func_shell
The previous attempt was incorrect. The issue isn't that subprocess fails to
set PWD, it's that PWD is in the metadata, inherited from the environment, and
is re-exported, overwriting the actual accurate one in the shell environment
with the old one from the metadata. So, ensure that PWD in the metadata is
not exported.
We can ditch this when the environment handling is reworked (e.g. poky's
commit to do so).
(Bitbake rev: 2c8683234acf514706b2b69f5b29405485e664dd)
Signed-off-by: Chris Larson <chris_larson@mentor.com>
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>
---
bitbake/lib/bb/process.py | 2 --
1 file changed, 2 deletions(-)
diff --git a/bitbake/lib/bb/process.py b/bitbake/lib/bb/process.py
index 1c790658c..f02332df9 100644
--- a/bitbake/lib/bb/process.py
+++ b/bitbake/lib/bb/process.py
@@ -1,4 +1,3 @@
-import os
import logging
import signal
import subprocess
@@ -9,7 +8,6 @@ def subprocess_setup():
# Python installs a SIGPIPE handler by default. This is usually not what
# non-Python subprocesses expect.
signal.signal(signal.SIGPIPE, signal.SIG_DFL)
- os.environ['PWD'] = os.getcwd()
class CmdError(RuntimeError):
def __init__(self, command):
--
cgit v1.2.3