On Mar 20,  6:58am, "Perry E. Metzger" wrote:
} Chuck Silvers <chuq@chuq.com> writes:
} > it seems like a very good idea to me.  before this change, if I would
} > check out a fresh source tree, cd to .../bin/ls, and type "make",
} > it would always give an error.
} 
} And that's probably the right behavior. If you want it to work with
} the in-system tools, just say make USETOOLS=no and all is well. What's
} wrong with that?

     It makes the process more complex then it needs to be.

} > after this change, the same commands
} > will build "ls".  this seems like a vast improvement to me.
} 
} But it isn't, because it means people will do full builds with
} USETOOLS set to no.

     People doing full builds should be prepared to look up the proper
procedure, or a script should be provided.

} things. In addition, the change wasn't discussed on tech-toolchain,
} and there was a good reason to have it the other way.

     I disagree.  I often build individual items to fix security holes,
make local mods (i.e. hook pppd into my accounting system), etc.
Building individual items should simple.

}-- End of excerpt from "Perry E. Metzger"