thanks... yes i did want to time it.

well... this arrived too late but i estimate that it took about 37 hours 
looking at the creation times in /bin /sbin etc. this was on a sparc classic 
with 48MB mem.

GREG

> On Wed, Nov 21, 2001 at 12:33:35PM -0500, Michael G. Schabert wrote:
> > Actually, I think he's asking not for a pre-estimate, but rather if 
> > there's a way that he can tell how long it took after he does it.
> 
> Ha, maybe
> 
> > 
> > There's a few ways to do this, depending on your shell. Some shells 
> > have a built-in timer function. There is also a system command 
> > "time", which can prepend other commands, much like "nice" can. So 
> > you can type "time make build". If you're using one of the shells 
> > with a built-in time function, you can even set it up so that any 
> > command that takes longer than "x" seconds automagically prints out 
> > how long it took after it completes...but note that the default 
> > format of the shell-time is different than the /usr/bin/time.
> > 
> > Another way that you can do it is to use cron to perform the make 
> > build. The first line printed after typing "make build" is "build 
> > started at xxx date/time" or similar. Cron jobs are e-mailed to the 
> > owner after completion. So you can see that it started at, say 9am 
> > and the date on the email showed that cron sent it at 8pm, giving you 
> > an 11 hour compile time.
> 
> And, the easiest maybe:
> make build >& build.log (or make build > build.log 2>&1 if you're using sh)
> and look at the content of make.log :)
> 
> --
> Manuel Bouyer, LIP6, Universite Paris VI.           Manuel.Bouyer@lip6.fr
> --