Joep Vesseur 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?
I had "-t" in my nightly option earlier, but that alone didn't help until I set the BUILD_TOOLS to the local /opt tools instead of using the default /ws/onnv-tools/. thanks, -jane > > Joep
