Do not raise safe level in tainted procs if original level was zero
By definition safe level zero should not (ever) check taintedness
suppress "toplevel constant x referenced by ..." warning unless verbose warnings enabled
Make attempting to redefine a constant a RuntimeError instead of a warning
remove root owned files that buildUtils generates