Recent Changes to DevShell

Chris,

In your recent changes to devshell, you seem to have broken the default behavior of setting TERMCMD / TERMCMDRUN.

When I set them up for scree as follows:

TERMCMD = "${SCREEN_TERMCMD}"
TERMCMDRUN = "${SCREEN_TERMCMDRUN}"

I get a DEBUG message claing to be starting konsole, not screen, also there seems to be a problem with the environment being passed as the arg3 is related to env:

ERROR: Logfile of failure stored in: /vol/1/sgw/autobuilder/yab/yocto-slave/oe-core/build/build/tmp/work/armv5te-poky-linux-gnueabi/lttng-ust-0.15-r2/temp/log.do_devshell.31726 Log data follows:

| DEBUG: Attempting to spawn terminal "konsole"
| ERROR: Error executing a python function in /vol/1/sgw/autobuilder/yab/yocto-slave/oe-core/build/meta/recipes-kernel/lttng/lttng-ust_0.15.bb:
| TypeError: execve() arg 3 contains a non-string value
|
| ERROR: The stack trace of python calls that resulted in this exception/failure was:
| ERROR:   File "do_devshell", line 6, in <module>

Did you check that this worked correctly with screen?

Thanks
Sau!

Saul Wold
Yocto Component Wrangler @ Intel
Yocto Project / Poky Build System

First, this isn't how you configure devshell now. This is a big part of why I reworked it to begin with, so we'd have better usability. See the commit messages for details, or just set OE_TERMINAL = 'screen' (or 'xterm' or 'noop' or 'auto' or..).

This error is just a general bug in the reworked env var exporting I did per Richard's request, I have a local patch here and will send it shortly. Sorry about that. No idea why I didn't hit that when doing the original testing. If you want a temporary local fix, edit terminal.bbclass, see the env var export bits, and make it check to see if the value it retrieves is None before adding it to the env for the terminal. Expect the patch to the list within the hour.

Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics