On Sun, 23 Apr 2000, Erik E. Fair wrote:

> In looking over suspended PRs, I found this one. It's about our build 
> system not updating the local environment to have all the tools 
> needed to do the build. I agree that the build system should not do 
> that (think "cross-compiles"), but we could go half-way: *check* the 
> local environment to see if all the tools are there at the outset 
> (e.g. make_cmds & compile_et for Kerberos) so that you don't waste 
> half a day on an old m68k machine doing a build that fails.
> 
> The information is already in the build scripts (don't we have a 
> variable for each command executed, e.g. YACC, CC, LD, STRIP, etc), 
> so it shouldn't be too difficult to construct a check.

I'd like to see a "toolchain" target, that could be used to update an
older system from source. Of course you would never call it on a
cross-compile run. You could set DESTDIR, though, and adjust your
paths to get the behaviour desired by the filer of the PR.