>> you need a consistent source tree at the very least.  i've not tried
>> it, but i imagine that the majority of the work would be assembling
>> the major toolchain (eg, cc, ld, as, etc, but also sh, awk, lex, yacc,
>> rpcgen, and so on).  once you've got that in place, the libraries to
>> support the binaries ought to come in short order (with libc instead
>> called libnetbsd?), and then the binaries themselves.  built, that is,
>> not necessarily completely *working*.
>
>Indeed; you would probably also have to assemble some sort of support 
>library -- there are places where even these tools assume the C library 
>and headers are the NetBSD ones.

indeed!  such a chore is not for the timid or inexperienced.

-- 
|-----< "CODE WARRIOR" >-----|
codewarrior@daemon.org             * "ah!  i see you have the internet
twofsonet@graffiti.com (Andrew Brown)                that goes *ping*!"
andrew@crossbar.com       * "information is power -- share the wealth."