aboutsummaryrefslogtreecommitdiffstats
path: root/oe-init-build-env
diff options
context:
space:
mode:
authorMing Liu <liu.ming50@gmail.com>2017-11-20 10:35:57 -0800
committerArmin Kuster <akuster808@gmail.com>2018-02-23 08:06:47 -0800
commit4c36c5110b822eeac06b2b336917ba4d8b54a247 (patch)
tree4a3a838d88da864a21220fc5c3e927aa1cbeaec5 /oe-init-build-env
parente2561de16c19e862b825d5a2feb3c6781b0869c5 (diff)
downloadopenembedded-core-contrib-stable/morty-next.tar.gz
lib/oe/terminal.py: use an absolute path to execute oe-gnome-terminal-phonehomestable/morty-next
A flaw was found on my Ubuntu 14.04.5 LTS, on which that gnome-terminal is the default terminal, when I run any of the tasks: bitbake busybox -c menuconfig/devshell/devpyshell bitbake virtual/kernel -c menuconfig/devshell/devpyshell I got a error as follows: "Failed to execute child process "oe-gnome-terminal-phonehome" (No such file or directory)" Seems the environment of the process calling Popen is not passed to the child process, this behaviour is a known issue in Python bug tracker: http://bugs.python.org/issue8557 It could be fixed by using an absolute path instead per test. Signed-off-by: Ming Liu <liu.ming50@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> (cherry picked from commit 2117c148ef07d84bc605768e3b3671b0126b9337) Signed-off-by: Andre McCurdy <armccurdy@gmail.com> Signed-off-by: Armin Kuster <akuster808@gmail.com>
Diffstat (limited to 'oe-init-build-env')
0 files changed, 0 insertions, 0 deletions