[releng_6 tinderbox] failure on sparc64/sparc64

Matthew Jacob mj at feral.com
Sat Feb 4 10:59:19 PST 2006

> I would think that the tinderboxes should run 100% the same flags as
> what normal release builds use.  Nothing more, nothing less.

What I would like to see is a pointer to a procedure and tools to make 
sure builds aren't broken.

I've been refreshing my memory about email going back about 5 years, and 
at that time there was a lot of wrangle over people not doing adequate 
checking for at least syntactic correctness for multiple platforms.

I certainly have broken a lot more than I would like lately, and part of 
this (other than being too stupid and hasty) came about because it 
wasn't actually obvious what would be a good pre-commit compile check 
for kernels for me to follow.

At the very least I've now come up with:

  compile GENERIC (easy enough to do)
  compile LINT (this wasn't obvious how to make LINT)
  compile PAE (for i386 at least)

Since the complaint of 5 years ago by many was that they didn't have 
alphas to compile on is still relatively true (that is, few people have 
more than one architecture) has been addressed in two ways (tinderbox, 
and cross-compilers), the issue should be better, but for three things 
I've observed:

a) The tinderbox breakage is being treated as bad as stop ship type of 
bug rather than being informative as it should be. I feel I got roasted 
and slammed for what should have been simply a "hey- Matt- come fix this 

b) It's instantly not obvious to me (being lazy and not having kept all 
my committer mail in a way I can find) how *I* can do a tinderbox run 

c) Similarily, I don't know how to build a cross-build environment. I 
should, and I bet if grovel around a bit I can find out how to do so.

The point here is that if well-meaning and moderately intelligent 
committers miss steps that are important to keeping the quality up, 
please point them at documentation that gives a reasonably coherent set 
of steps as to how to correct their errors. I'm sure that most of those 
who err will spend the extra late night hours to get it right then.

More information about the freebsd-sparc64 mailing list