I'm on a 64bit Solaris 10 Solaris system, where I'm trying to install
the Sun Studio 12 suite.   Due to space, I configured it to install
in /usr/local/opt instead.  The installation goes smoothly, it adds
some patches and netbeans (it uninstalled the previous old verion of
SUWspro)....

But where is the code?  Where are the symbolic links.  I don't have a /
usr/bin/symlinks file, so it should just create them (the script
initially asked me if I wanted this).

I had thought that /usr/bin/cc -> would be created to point ot the
SUNWspro compiler.

I looked through the scripts, didin't really see anything obviously
wrong.  So I wonder what else needs to happen on my part to get this
to work correctly.

I wasn't able to see the package available for uninstall, so I
manually ran the uninstaller, which I found buried under /usr/local/
opt/SUNWspro, to start over once I figure out how to get this working
properly.

I installed this with "installer -nodisplay"


Thanks.

Forrest wrote:
> I'm on a 64bit Solaris 10 Solaris system, where I'm trying to install
> the Sun Studio 12 suite.   Due to space, I configured it to install
> in /usr/local/opt instead.  The installation goes smoothly, it adds
> some patches and netbeans (it uninstalled the previous old verion of
> SUWspro)....
> 
> But where is the code?  Where are the symbolic links.  I don't have a /
> usr/bin/symlinks file, so it should just create them (the script
> initially asked me if I wanted this).
> 
> I had thought that /usr/bin/cc -> would be created to point ot the
> SUNWspro compiler.
> 
No, just put <path to your install>/SUNWspro/bin in you path.

-- 
Ian Collins.

Well, another thing I noticed (and neglected to mention) was there was
no bin directory under /usr/local/opt/SUNWspro -- I'll redo the
installation and see what happens.   Somewhat new to Solaris, but
really appreciating the flexibility of ZFS on this new 40T NAS I'm
putting together ;-)

Thanks.

Okay, I've run into the same problem before:

[ after installation ]

Approved patches will be installed in this order:

124864-01


Checking installed patches...
Verifying sufficient filesystem capacity (dry run method)...

Patch 124864-01 failed to install due to a failure produced by pkgadd.

See /var/sadm/patch/124864-01/log for details

Patchadd is terminating.


[ contents of the above-mentioned log ]

This appears to be an attempt to install the same architecture and
version of a package which is already installed.  This installation
will attempt to overwrite this package.

/usr/local/src/pkg/install-intel-S2/product-patches-intel-S2/124864-01/
SPROcpl/install/checkinstall: /usr/local/src/pkg/install-intel-S2/
product-patches-intel-S2/124864-01/SPROcpl/install/checkinstall:
cannot open
pkgadd: ERROR: checkinstall script did not complete successfully
Dryrun complete.
No changes were made to the system.

Note that I removed it with the uninstall.


The contents of /usr/local/opt/SUNWspro seems okay:

[root@nas SUNWspro]# ls
LEGAL-SS12  atd1        contrib     examples    installer
lib         prod
READMEs     bin         docs        include     inventory
man         sfw


Not sure the above error is serious or not - I'll have to look up the
patch number.  But I think this must be a problem.


Thanks.

Says it's an outdated patch - so I don't know why it would try to
apply it.  I guess I'll just ignore it and assume the install is
correct ;-)

On Fri, 27 Jun 2008 20:01:26 -0700, Forrest wrote:

> Says it's an outdated patch - so I don't know why it would try to
> apply it.  I guess I'll just ignore it and assume the install is
> correct ;-)

You probably want to lofi mount /usr/local/opt/SUNWspro at /opt/SUNWspro.
There are a lot of patches which need to be applied if you expect the
compiler suite to operate properly.

Yeah, I've had problems with symlinks before from /opt.  Lofi isn't
something I've used before - the manpage doesn't help much.  But it
sounds simple enough.


On Jun 27, 11:06=A0pm, Dave Uhring <daveuhr...@yahoo.com> wrote:
> On Fri, 27 Jun 2008 20:01:26 -0700, Forrest wrote:
> > Says it's an outdated patch - so I don't know why it would try to
> > apply it. =A0I guess I'll just ignore it and assume the install is
> > correct ;-)
>
> You probably want to lofi mount /usr/local/opt/SUNWspro at /opt/SUNWspro.
> There are a lot of patches which need to be applied if you expect the
> compiler suite to operate properly.

quoting Forrest (Fri, 27 Jun 2008 21:09:28 -0700 (PDT)):
> Yeah, I've had problems with symlinks before from /opt.  Lofi isn't
> something I've used before - the manpage doesn't help much.  But it
> sounds simple enough.

It is and works like a charm.

-- 
Dick Hoogendijk -- PGP/GnuPG key: 01D2433D
++ http://nagual.nl/ | SunOS 10u5 05/08 ++

In article <de0ff314-0efe-481b-90f1-cf489c79a6f7@y38g2000hsy.googlegroups.com>,
Forrest  <forrie@forrie.com> wrote:
>Well, another thing I noticed (and neglected to mention) was there was
>no bin directory under /usr/local/opt/SUNWspro -- I'll redo the
>installation and see what happens.   Somewhat new to Solaris, but
>really appreciating the flexibility of ZFS on this new 40T NAS I'm
>putting together ;-)

zfs create -o mountpoint=/opt/SUNWspro -o sharenfs=ro tank/opt/SUNWspro

Then you can mount /opt/SUNWspro on your stationary workstations or
inherit it in your development zones.

Happy hacking,
John
groenveld@acm.org

I like the ZFS mount option better - you can have this in the correct
location *and* share it with other Sun clients.