tinderbox information.

[John Dennis]

With respect to bonsai, I just want to give a heads up that I'm working
on it, as well as LXI, no point in duplicating efforts, additional help
always welcome if you're expert.

On Tue, 2004-03-09 at 14:44, Egbert Eich wrote:
> John Dennis writes:
>  > On Tue, 2004-03-09 at 13:06, Egbert Eich wrote:
>  > 
>  > The idea is that ALL errors should be logged, this makes it easier to
>  > fix everything at once. Otherwise you would have to fix the first
>  > problem, checkin, rebuild, and repeat the cycle. I'm not sure why you
>  > say the area where the problem happened is not easy to spot.
> 
> Maybe I'm too stupid to do so. I've looked thru 
> numerous logs without spotting any build error.
> Can you educate me? 

Well, I haven't had a chance to check the logs but its a standard build
log, if the build failed there is likely a compiler error which should
have an error message. Of course other things can go wrong, CVS errors,
or even an error in the Tinderbox script. When Jim and I worked on it we
were pretty careful to catch and report all errors, but I don't think we
were clever enough to make sure all the errors messages started with the
string "ERROR" making it easier to find, we'll fix that.

There is one other possibility, if you go to the bottom of the log and
the log says the build was successful but Tinderbox does not agree (one
case where you would search for an error and not find it) then we need
to modify how the Tinderbox script checks for a successful build. What
we do now is check the process exit status on every command we run. Make
should be reporting the correct error status, but I wouldn't fall over
in surprise is there is a broken make program out there.

>  > 
>  > > 2. The Makefiles don't get rebuild. If something was
>  > >    changed within an Imakefile or config file it will
>  > >    not show up in the logs.
>  > 
>  > It will on a "clobber build", perhaps it should clobber more often. Or
>  > perhaps on a non-clobber it should start out with a
>  > 
>  > make Makefile
>  > make Makefiles
>  > make depdend
>  > make include
> 
>  make includes
>              ^
>  > make
>  > 
> 
> make all
>      ^^^

Or "make Everything" as was suggested by Michel. O.K. you can tell how
long I've been around :-) Years ago the top level makefile didn't have
nice targets and you had to do things manually, old habits die hard, the
other suggestions are better.

> It should clobber every time. At least now.
> And it should be done if a previous build broke.

I'm not sure about clean clobber everytime, but its worth considering if
others agree. I'm also not sure if a clobber is justified if the
previous build failed. If there was a trival syntax error in one file,
do you really want to blow everything away and wait a long time to see
if its fixed? Wouldn't you rather start from where you left off and
immediately verify the fix? At the moment the tinder client does not
retain state from previous builds which would be necessary to implement
this behavior, I can look and see if its possible.