In fact a rebuild takes longer than 35 hours, depending on which "nightly" options you put into - or remove from - opensolaris.sh and sfw-opensolaris.sh. When you then add the time for constructing the DVD iso, then it can take one and a half day. Fortunately you don't necessarily have to sit there all the time, although it is exciting. You can conveniently identify the build faliures later from the nightly logfiles (problems is, that they are totally incomplete when the nightly process goes into some subdirs, this seems to be a bug in nightly or OS/Net's and usr/sfw's Makefiles). Normally it is the safest option, the use bldenv and run all make targets manually, without "-k"! This means you sit there for some time .... :-)
As I'm using /usr/sfw/bin/gcc as primary compiler (and have disabled shadow-compilation for speed reasons), the likelyhood that I run into a linking error is higher, than if I would be a fan of proprietary closed-src compilers like Studio. Because by default Studio is the primary compiler and gcc the shadow compiler with shadow-compilation enabled. But shadow-compilation ommits the linking step, and therefore bugs related to it don't get fixed in real-time. However, I do prefer gcc, simply because it works much better with free software. Certain things, like qemu's dyngen compiler or Xorg's legacy sparcPci.c cannot even be ported to Studio, even if you try hard. End of FYI-update. Regards, Martin
