I've done kernel compiles with or without X by removing it as a limiting
factor.  Re-direct the output messages of the make to a file.  This also
allows any warning messages to be later analyzed, such as:

make &>makelog.txt ...

X being active doesn't cause much issue, as the output is not scrolling
X bitmaps.  The '&' captures all output to standard out and standard
error.  During the compile I will check on progress by looking at the
size of the makelog.txt file, and 'tail makelog.txt' to see what is
currently being worked on.  I'll also disown the process to let it grind
away in the background.

This experience on building on an A2000/030/16M running X.

--Lance

On Sat, Jul 24, 2004 at 03:08:37PM +0000, Matthias Scheler wrote:
> In article <Pine.NEB.4.60.0407231254070.28615@lain.ziaspace.com>,
> 	John Klos <john@ziaspace.com> writes:
> > 2.0 self builds. Yay!
> > 
> >           build.sh started: Tue Jul 20 23:33:14 UTC 2004
> >           build.sh ended:   Fri Jul 23 11:28:44 UTC 2004
> 
> With or without X11?
> 
> > It's interesting to note that it took 2.5 days on a 66 MHz m68060 ...
> 
> Who much memory?
> 
> > Compare that with 18 hours to build 1.6...
> 
> That's mostly GCC 3.3.x's fault.
> 
> 	Kind regards
> 
> -- 
> Matthias Scheler                                  http://scheler.de/~matthias/