Switch a fatal usage to SystemExit ("T" not set)

This failure is one the *user* needs to see, as it may have to do with their
setup, but where they don't need to see a traceback and all, since they're not
developers, so I think SystemExit is appropriate here.

(Bitbake rev: e3cc9bc7b6ef1a2eca78235790a051329bceb9a4)

Signed-off-by: Chris Larson <chris_larson@mentor.com>
Signed-off-by: Richard Purdie <rpurdie@linux.intel.com>

diff --git a/bitbake/lib/bb/build.py b/bitbake/lib/bb/build.py
index c6d406057518bb8f092b2c92550f0665a05eba56..1f4107fb65034a558c0c0e40a59c8f8074a4e5c8 100644 (file)
--- a/bitbake/lib/bb/build.py
+++ b/bitbake/lib/bb/build.py
@@ -125,7 +125,7 @@ def exec_func(func, d, dirs = None):
     # Setup logfiles
     t = data.getVar('T', d, 1)
     if not t:
-        bb.msg.fatal(bb.msg.domain.Build, "T not set")
+        raise SystemExit("T variable not set, unable to build")
     bb.utils.mkdirhier(t)
     logfile = "%s/log.%s.%s" % (t, func, str(os.getpid()))
     runfile = "%s/run.%s.%s" % (t, func, str(os.getpid()))