Installing Sun Studio 10 into a non-global zone
By terryh on Jun 23, 2005
I've seen reports that the Sun Studio 10 compilers and tools won't install into a non-global zone. Unfortunately I wasn't up to speed on Zones during the time we were developing that release, so the installer wasn't developed with zones in mind. It turns out that it "nearly" works. The testing I have done shows that a default install in the global zone works fine, and this install is then visible to non-global zones. So that's one workaround. The failure in the non-global zone is due to a particular package attempting to create symlinks in /usr/ccs/bin during it's post-install phase. The default non-global zone configuration is a so-called sparse root zone. But if you configure a whole root zone, then your non-global zone isn't sharing /usr with the global zone, and the failure won't happen. You can even just remove inherit-pkg-dir dir=/usr (leaving three other directories shared with the global zone) while configuring your zone. That's the second workaround.
We've updated the package for the next release of the product, so that it doesn't create the symlinks, so Sun Studio 10, update 1 compilers and tools will install cleanly into a non-global zone.
There is also a hack way to get it to work in a default sparse root zone. I am in no way recommending this, but if you manually install SPROcc, ignoring the errors about the symlinks, and create the appropriate entry in /var/sadm/install/productregistry, then the installer will see that the package is already installed, and won't try to install it. Therefore it will never see the pkgadd failure, and will report a successful install.