Re: pkgsrc cross-compilation

[Taylor R Campbell <campbell+netbsd-tech-pkg%mumble.net@localhost>]

   Date: Mon, 13 May 2013 20:23:34 +0000
   From: Taylor R Campbell <campbell+netbsd-tech-pkg%mumble.net@localhost>

   I expect to find a lot of issues with pkgsrc's idea of tools (as in
   USE_TOOLS) because it doesn't distinguish host tools from target tools
   very well, but we'll see.

As I feared, this doesn't work too well.  We'll probably need a major
rototill of mk/tools to split everything up into host tools and target
tools.  (Perhaps in the process we could rename the latter to
`utilities' or something so we can consistently use the word `tool' to
mean something that runs on the host, like NetBSD's $TOOLDIR.)

This is something that should happen anyway for various reasons; for
example, when UNPRIVILEGED=yes, USE_TOOLS+= chown:run is broken (see
PR pkg/45717), and there is currently no way for packages to request
the same tool for running at build-time (e.g., from $WKRDIR/.tools)
and for a pathname to bake into the package (for which $WRKDIR/.tools
is wrong).

Thoughts?  I haven't come up with a strategy yet -- perhaps we could
move target stuff to mk/utilities incrementally, and leave everything
that still works for native compilation but is broken for cross-
compilation in mk/tools.