On Sat, 30 Apr 2005 10:37:46 -0400
Michael <macallan18@earthlink.net> wrote:

> 
> S900, 300MHz G3, 1MB L2, 400MB RAM, 3.99.3 kernel, 2.0 userland. Took
> a couple of hours, not sure how many exactly. 

I don't understand the disparity in time.  I'm using a dual 180MHz 604e
7300.  This was a full build and not an update?

>Seems to work fine, if you want the binaries I'll put them somewhere
>for download.

No, I need the source to build.  Besides the obvious issue that this
should build on everyone's macppc hardware, I also need to be able to
compile the binaries for install kernel MDs.

> > cvs up from yesterday. build command is
> > ./build.sh -j 8 -O /usr/obj -D /usr/NetBSD-new-build -T /usr/tools
> > build
> 
> I used something very similar. What I found though...
> - make sure there are no stray .o files in your source tree
> - make sure there are no stray dependency files anywhere
> - make sure there are no stray obj directories
> ... especially when using -O - the build process gets awfully confused
> by these things. make distclean cleans what it thinks where you keep
> your objs, but nowhere else, so in doubt have a look if there's
> anything suspicious lurking anywhere. 

The above command is what is at
http://www.netbsd.org/Documentation/current/#using-anoncvs

I tried just doing the update -u, but the shell complained that the
kernel was too new.  The most recent build I have of 2.99 is unreliable
with disk I/O and networking together.  I couldn't track down the
specific problem because it would occur many hours into the building,
usually overnight, and my ssh session would be terminated.  I've not had
the same problems with 3.99.3.

tim