> > Subject: Re: Duo 230 and MacBSD, same here
> > Bill Studenmund wrote:
> > DUH!!  I don't know what's the matter with me!  I have a 486 right here
> > on my desk.  How about a cross-compiler for my 486?  That would be the
> > ideal!
> 
> It's not hard to build a cross-compiler on any machine supported by GNU gcc. I
> won't bore all with the description, so drop me a line if you're interested.
I'd prefer to get a complete working setup so that I could have a high
degree of confidence that it was done correctly.  I'd hate to spend a long
time debugging a kernel only to discover that the cross-compiler I spent 60
hours configuring was done incorrectly.

> >     Does NetBSD have a utility for non-destructively splitting a drive?
> 
> Probably not, but I've heard some MacOS disk partitioner can do that job.
Actuall,y I was referring to the 386 where I was thinking about doing the 
cross-compiles.
> 
> >     How much space do I need for minimum NetBSD + cross-compiler?
> 
> Around 19megs for the sources and one kernel, if you remove the stuff for the
> other architectures. 3.5megs for the binaries on a RS6000, for a i386 machine 2
> megs should be sufficient.
> 
> >     Does anyone have an ALREADY working version of this that is know to
> > work for kernels?
> 
> Yes, for RS6000
I have access to an RS6000.  Is there any way that you could package up and
transmit the entire cross-compiler environment ( I would like to avoid the
need to build the cross-compilers for the obvious reasons.)  I would really
appreciate it, and so would many Duo users.  Even if I can't get it working,
MAYBE I can at least identify what the stumbling block is.

Ideally, I would like to have a known-good build tree and header files, but 
if that is a great inconvenienec, I can dowload those myself.  The main
thing is to get a set of tools in binary form.