Source-Changes archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: CVS commit: sharesrc/share/mk
Chuck Silvers <chuq%chuq.com@localhost> 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?
> 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.
> what policy would you prefer? why do you assume that without setting
> TOOLDIR that the new toolchain won't be used?
The question is one of the mechanism -- we want people exercising the
full "cross build even on the same architecture" way of doing
things. In addition, the change wasn't discussed on tech-toolchain,
and there was a good reason to have it the other way.
--
Perry E. Metzger perry%wasabisystems.com@localhost
--
NetBSD Development, Support & CDs. http://www.wasabisystems.com/
Home |
Main Index |
Thread Index |
Old Index