Is your closed gate in sync with your main gate? Is your main gate in sync with the snapshots for build 129? If not, I suspect you're missing some respin info as I believe this is when a putback happened right at gate closure and the closed and open bits were out of sync. As I've been told in the past, always clone from the snapshots and don't rely on the tags being 100% accurate off of the main gate.
--Mike On Mon, 2010-02-01 at 19:15 -0600, Will Fiveash wrote: > I have a ON repo that is at onnv_129 level on two systems, one a x86, > the other sparc. While nightly runs fine on the x86, I'm seeing the > following error when I do a nightly (with the clobber option): > > "../../sun4/io/memtest/memtest.c", line 2886: undefined symbol: promvp > "../../sun4/io/memtest/memtest.c", line 2886: warning: operands have > incompatible pointer types: op "==" (E_OPERANDS_INCOMPAT_PTR_TYPES) > cc: acomp failed for ../../sun4/io/memtest/memtest.c > *** Error code 3 > dmake: Warning: Command failed for target `obj64/memtest.o' > Current working directory > /builds/willf/hg/sparc/6886774_pam_pkinit/usr/closed/uts/sun4u/memtest > > Is this a known problem with onnv_129? I tried searching the flag day > maill and bug reports but didn't anything that directly mentioned the > undefined symbol error. Note, the sparc build system is running > snv_130. >
