>>   > strlcpy/cat is in libc
>>   But the build system's libc might not. Don't know how big problem this
>>   might be for people.
>people build on older solaris systems.  they don't have strl*.

	i don't understand... what is the portability requirement for build
	tools?  i can think of two extreme ends:
	- supply GNU autoconf script (configure) and do a lot of #ifdef dance
	- require build machine to have certain netbsd-friendly library,
	  have no #ifdef, assume that we have same set of functions supplied
	and i think i was trying to pursue the latter.

	i don't think it worthwhile to pursue intermediate goals, like "compile
	strl* locally so that we can build on solaris".
	even if we really need to do this, i'd prefer to pull strl{cpy,cat}.c
	in lib/libc/string, not from other portion (like
	crypto/dist/heimdal/...).  if we use two copies of strl*, we are likely
	to leave behind one of them (bugs will stay longer).

itojun