Try to run `export FOO='${}' && bitbake -c menuconfig busybox;` in the dizzy branch of openembedded-core (bitbake 1.24). Assuming tmux is installed and selected by OE/bitbake, you should see several messages like this before bitbake bails out: Trying to run: tmux att -t devshell-31784 session not found: devshell-31784 The tmux window tries to run a generated shell script `run.do_terminal.##` under tmp-glibc which contains a malformed line `export FOO="${}"`. /bin/sh (dash in my case) immediately fails to parse it with a "Bad substitution" error. As a result, the tmux session ends before bitbake can attach.
Can you be more clear what your use case is for this? We know that there are some issues with dash, so if you are setting an export with a bad substitution for DASH, that does not make sense and will fail, if you can use bash does it work correctly?
(In reply to comment #1) > Can you be more clear what your use case is for this? Our build system is orchestrated by GNU Make, which sets up the bitbake environment to build OE, run menuconfig, etc. That process (and I don't know the exact details atm) sets MAKEOVERRIDES to something resembling a shell substitution, which gets incorrectly translated into the aforementioned run.do_terminal.## script. > so if you are setting an export with a bad substitution for DASH, > that does not make sense and will fail `export FOO='${}'` is not a substitution because it's a single-quoted string. The problem I described happens when a single-quoted string resembling a substitution is translated into a double-quoted string (in run.do_terminal.##) and the shell tries to expand it. > if you can use bash does it work correctly? Unfortunately no. Bash fails to parse the malformed substitution as well. Additionally, run.do_terminal.## tries to set BASHOPTS, which is read-only in bash.
It appears the question has been answered. If this still needs info, please put the bug back into the needinfo status.
This is fixed in master here: http://git.yoctoproject.org/cgit/cgit.cgi/poky/commit/?id=0a791e91e55d30b328ddbd90fdb0d5911c388b96 Although as Martin Jansa stated on the list, it can't be integrated on the current Dizzy branch because it breaks something else, if you need it, hopefully you can still use that patch to fix your problem.