I think the fix is to use one of the correct ways to install the bits. There are a lot of tarballs floating around.
If one of our official tarballs is messed up we should figure out where it came from and fix it. If someone can point me to a tarball that's messed up, I can poke the right person to get it fixed. --chris James Carlson wrote: > Raymond writes: >> Yes, I just see executable /opt/SUNWspro/bin/cc file instead of symlink to >> ../prod/bin. >> >> My version of SunStudio12 is a newest tarball version ' >> SunStudio12ml-solaris-x86-200709-ii.tar.bz2'. >> So how to figure it out? > > I have no clue how it happened, but from a few google searches, it > sounds like it's not an uncommon problem. I recommend at least filing > a bug so that someone else can take a look. (Did you use "cp -r" to > move it around after installing?) > > The quick fix I would suggest would be checking first that the bin/* > binaries are identical to the prod/bin/* counterparts. If so, then > just replace each instance in bin with the proper symlink. > > Something like this (untested) ought to do it: > > #!/bin/sh > cd /opt/SUNWspro/bin > for i in *; do > if [ -f $i -a -f ../prod/bin/$i ]; then > if cmp -s $i ../prod/bin/$i; then > rm -f $i > ln -s ../prod/bin/$i > else > echo "$i and ../prod/bin/$i are different" > fi > fi > done >
