Premise: I have a recipe failing. The cause of the failure seems to be that a patch I made doesn't apply. Triggering action: I think it would be useful to enter devshell and try to diagnose the problem by reproducing what bitbake is doing. (bitbake -c devshell failing_recipe) What happens: However, I cannot do it, because the recipe fails to build. What was expected: I think it would be more useful if I could still be dropped into the devshell, with a big warning that the recipe failed to build. At least, I would have better chances to figure out what is wrong.
There is a mechanism for this, if you check the stock local.conf there's a variable PATCHRESOLVE which is set to "noop". If you set this value to "user" the build system will start a devshell when patch application fails allowing you to resolve the failures. http://www.yoctoproject.org/docs/2.0/ref-manual/ref-manual.html#var-PATCHRESOLVE By default the system will try and determine which terminal type to use, much as with devshell: http://www.yoctoproject.org/docs/2.0/ref-manual/ref-manual.html#var-OE_TERMINAL I use PATCHRESOLVE quite often with screen. I'm marking this issue as RESOLVED→INVALID. Please feel free to reopen if I have misunderstood your request.