> : Would this bmake happen to be my autoconf'd version of our make?
> 
> Nope, just a "${HOST_CC} ${HOST_CFLAGS} -DMAKE_BOOTSTRAP -o
> ${TOOLDIR}/bin/bmake usr.bin/make/*.c usr.bin/make/lst.lib/*.c"....

Ok, thought since you mentioned being able to build the tree on
anything...  in that case would it make sense to use a different name?
[not that I have one to recommend].

> The build harness's bmake does not have a compile-time MACHINE or
> MACHINE_ARCH.  They only need to be set once in the environment (via the
> generated wrapper, which also sets CC and whatnot), and will be inherited
> from there.

Which is the case anyway, the compiled in defaults for MACHINE* are
only used if getenv() finds nothing.

--sjg