On Thu, Apr 23, 2009 at 8:05 AM, Joep Vesseur <Joep.Vesseur at sun.com> wrote: > On 04/22/09 22:39, Jane Chu wrote: >> Hi, >> >> I get the following *intermittently* from running nightly build - >> >> >> ? ? ? ? No 32-bit compiler found >> ? ? ? ? *** Error code 1 >> >> ? ? ? ? No 64-bit compiler found >> ? ? ? ? *** Error code 1 >> >> ? ? ? ? /usr/java/bin/javac >> ? ? ? ? java full version "1.6.0_13-b03" >> >> ? ? ? ? Aborting due to missing compiler. >> >> The problems happens on sparc and x64 build machines maintained >> by RE groups. ?It doesn't stick to a particular build machine OS, >> nor build workspace, it comes and goes for no apparent reason. >> >> Does anyone have an idea what might be the culprit? > > I usually get this when I do a full build (including clobber) with '-t': > the clobber throws away usr/src/tools which contains cw, and the subsequent > build can't find "cw" which it uses as a compiler front-end. > > The steps that nightly then runs are: > ?- do clobber (aka "rm cw") > ?- check compiler versions (aka run cw) > ?- build tools (aka "make cw") > which doesn't work if clobber throws away the compiler to be used (cw) > > I'm not sure why not many people run into this - maybe everyone nowadays runs > nightly with +t?
usr/src/tools/env/opensolaris.sh includes that as one of the default nightly options, though even with that, shouldn't doing a full build w/ nightly on a clean workspace work without any special intervention (i.e. hg clone; set CODEMGR_WS in env file, nightly envfile)? That's why I was asking if I was doing something wrong. It seems like I hit this every couple of months where something (usually things that used to be part of NWS prior to its merge w/ ON) tries to build before usr/src/tools is built, causing nightly to fail (though the error messages sometimes means it takes a while to figure out that is the issue).
