Hi, thanks for the follow-up!
Well it seems I wasn't clear enough, sorry :) I don't build onnv-gate, it's a medial imaging/3D application I build daily. Sometime before there wasn't a cvs in nevada (or at least I wasn't aware of any), and I needed a gnu toolchain too, and these were ok in jdsbld. So I used the cvs binary from that "package", and the other tools for while (aclocal & co). In recent nevadas cvs has been put into /bin, but I don't know when, because I had nv_85 for quite a while (until 101 came out). As I have /bin before /opt/jdsbld/bin in my path the build system picked up the new cvs. I noticed with 103 that with a regular cvs checkout the checkout stalls. But never at the same file, what's more, sometimes not even at the same project (the main project needs some 8 support libs to be built). I deliver 4 experimentals & 1 nightly a day, so this was a major pain... Others do not report this issue, so I think, it may be some kind of weird cvs error here. To circumvent this, I copied a previous cvs from a previous Solaris install's /opt/jdsbld/bin directory (liveupgrade rulez!:) ), so everything is fine now. Hope it's clearer now :) Thanks! -- This message posted from opensolaris.org
