[oe] bitbake goes crazy when ...

[Yury Bushmelev]

Hello!

Bitbake fails without any end-user readable diagnosting (just a lot of
strange errors and tracebacks) when:
1) specifying non-existent DISTRO (I've mistyped and specified
'angsrom-2008.1' instead of 'angstrom')
2) specifying non-absolute path to TMPDIR (i.e. you can't use './tmp' as TMPDIR)

I've found this when playing with my testbuilder script.

Can/should we catch that errors and produce user-readable messages about this?

-- 
Yury Bushmelev