Greg Oster writes:
> Johnny Billquist writes:
> > But for my purposes, my fix will do. I want it to compile, and obviously 
> > the VAX keeps getting less and less interest, so I'm not holding my 
> > breath for it to get fixed any other way.
> > I suspect before long, the VAX won't even be supported any more. It's 
> > been several years since you last could run build.sh from start to 
> > finish on a native build on a VAX.
> 
> Actually... 
> ===> Summary of results:
>          build.sh command: ./build.sh -U -u -o -V MAKECONF=/u3/builds/mk.conf
>  -D /u3/builds/build.vax/install -R /u3/builds/build.vax/release -T /u3/build
> s/build.vax/tools release
>          build.sh started: Sun Nov 27 15:15:16 UTC 2005
>          MACHINE:          vax
>          MACHINE_ARCH:     vax
>          TOOLDIR path:     /u3/builds/build.vax/tools
>          DESTDIR path:     /u3/builds/build.vax/install
>          RELEASEDIR path:  /u3/builds/build.vax/release
>          makewrapper:      /u3/builds/build.vax/tools/bin/nbmake-vax
>          Updated /u3/builds/build.vax/tools/bin/nbmake-vax
>          Successful make release
>          build.sh started: Sun Nov 27 15:15:16 UTC 2005
>          build.sh ended:   Sat Dec  3 00:41:13 UTC 2005
> ===> .
> 
> That's a build of 3.0_RC3 on a 1.5.3 system :)  (4000/60, in this case)

Actually.. I was looking at the wrong box... that's a build of 3.0_RC3 
on a 3.0_RC3 system... (still 4000/60).  (I think I started to go 
from 1.5.3->3.0, but encountered enough weirdness that I installed a 
cross-built 3.0_RC3, and then built a native 3.0_RC3 from there..)

Later...

Greg Oster