Some developers expect that once in a devshell they can call commands as if in a normal shell, whereas the reality is that the devshell is a mechanism to get into the bitbake task execution environment and commands must be called in the same manner as bitbake calls them i.e. with appropriate options for cross-compilation, etc. We should update the "Using the development shell" section of the developer manual to make this clearer. Furthermore we could point out that a user can use the run.do_* files in temp to a) look at how the tasks are run by bitbake and b) run the commands exactly as bitbake does. i.e. if I'm in a devshell for connman in a build directory where connman has already built I can re-run the compilation steps by calling ../temp/run.do_compile
Turns out a remarkably similar bug was filed a couple of days before this. *** This bug has been marked as a duplicate of bug 9114 ***
I set the doc flag to "No" here since it is a duplicate.
verified