Tool/software:
This is related as it deals with the same SDK and Processor. At some point as I was trying out this updated SDK the bitbake **devshell** stopped functioning correctly.
A command like `bitbake -c devshell u-boot` will complete and open a new terminal/shell but none of the expected environment variables $S, $B, $WORKDIR are set. Therefore none of the build operations work either.
Has anyone seen this?
I have tried sourcing the output of `bitbake -e` that I saved to a file in the resulting shell. But that generates a large number of errors. The environment variables are then set but none of the build operations are understood and the PATH seems incorrect.
This is on a vanilla Debian and also on a vanilla Ubuntu. I am confident it was functional at one point, but perhaps only using the default MACHINE ?= "arago".
