Sun Studio 11 patches 120760-03 121015-02

Solaris 10 (01/2006) was loaded anew on a host. The Sun Studio 11 packages were also loaded on it.

Packages 120760-03 and 121015-02 were suggested. They would not install unless the option "pkgadd -G /var/sadm/spool/120760-03.jar.dir" was used. I applied the patches manually with the "-G" option. It worked saying that it was not necessary to do this patch.

When I ran "cc -o a.out example.cc", I now get a run-time error saying "/opt/ss11/SUNWspro/prod/bin/acomp" killed trying to open libyabe.so.

I will now uninstall the whole Studio 11 and try again. You can see why I am sorry that I attempted these two patches. I will report back once I uninstall and re-install the Sun Studio 11 codes.

[720 byte] By [j.k.harrison] at [2007-11-26 6:22:26]
# 1

I installed Sun Studio 11 anew. I ran updatemanager and I get the message: Install of update failed. Utility used to install the update is not able to add packages. Utility used to install the update failed with exit code 5.

I went to the location "/var/sadm/patch/120760-03" and looked at the log. It mentioned that the package SPROlang was already installed. I must specify the -G option. To install the new instance of this package ... and then install the new instance of this package in all zones. I am not zone educated. I guess is that the global one is fine. What do I do to get pass the hurdle. I am reluctant to remove the packages "SPROcc", "SPROlang" and "SPROlangx" and try this again.

I would need help interpreting what to do next. I installed the Sun Studio 11 under the base location "/opt/ss10/...". I might try the pkrm again with the extra syntax.

jkharrison at 2007-7-6 14:09:37 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 2

Sun incident 64979050 was opened to check this issue out.

They acknowledged these problems based on Solaris 10 security features. They said to refer to bug ids 6337009, 6216434, 6374972 and 6214678.

They think that it will be resolved when Solaris 10 Update 1 is released. I am only passing this information on as terse as I can.

jkharrison at 2007-7-6 14:09:37 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 3

Sun closed out the request. Initially they thought that the problem could be fixed if I was running at Solaris 10 update 1. All along the way, I have been running the latest 01/2006 and I have been religiously patching with updatemanager. They do think it is a bug. Perhaps they will report it in another bug id.

jkharrison at 2007-7-6 14:09:37 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 4

I have had some errors while trying to install Sun Studio 11 patches from updatemanager, too. I cannot confirm which patches I tried, but for all of them installation failed with this error. I didn't try to install them manually with -G. I wonder if there is another way to install Sun Studio 11 so that it gets installed in all zones and stops complaining when I try the updates.

-- Douglas

datique at 2007-7-6 14:09:37 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 5
I have the same problem with patches, 121016-02, 121020-02, 120759-04, and 121018-02.Manually installing with the -G option didn't lead to a successful installation either.
lqqnguyen at 2007-7-6 14:09:37 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 6
Hi all.Could one (or more!) of you post the errors you are getting when trying to install, and the syntax used?
ForumModerator at 2007-7-6 14:09:37 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 7

I will not be able to reproduce the circumstances. The customer had me uninstall Sun Studio 11 and install the buggier Sun Studio 10 for unrelated reasons.

The message for patches 120760-03 and 121015-02 should be easy to reproduce. I used the patch manager and it failed stating to try the install using a different technique.

jkharrison at 2007-7-6 14:09:37 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 8

The following are the failed installation messages from the Sun Update Manager:

121016-02

Sun Studio 11_x86: Patch for Sun C_x86 5.8 Compiler

Failed

Install of update failed. Utility used to install the update is not able to add packages. Utility used to install the update failed with exit code 5.

121020-02

Sun Studio 11_x86: Patch for x86 Fortran 95 8.2 Compiler

Failed

Utility used to install the update failed with exit code {0}.

120759-04

Sun Studio 11_x86: Sun Compiler Common patch for x86 backend

Failed

Install of update failed. Utility used to install the update is not able to add packages. Utility used to install the update failed with exit code 5.

121018-02

Sun Studio 11_x86: Patch for Sun C++ 5.8 compiler

Failed

Utility used to install the update failed with exit code {0}.

Log files:

# more /var/sadm/patch/121016-02/log

pkgadd: ERROR: The package <SPROcc> is currently installed on the system in the

global zone. To install the new instance of this package in the global

zone only, you must specify the -G option. To install the new instance

of this package in all zones you must first remove the existing instance

of this package from the global zone first (via pkgrm) and then install

the new instance of this package in all zones.

pkgadd: ERROR: package <SPROcc> cannot be installed on this system/zone

# more /var/sadm/patch/120759-04/log

pkgadd: ERROR: The package <SPROlang> is currently installed on the system in the

global zone. To install the new instance of this package in the global

zone only, you must specify the -G option. To install the new instance

of this package in all zones you must first remove the existing instance

of this package from the global zone first (via pkgrm) and then install

the new instance of this package in all zones.

pkgadd: ERROR: package <SPROlang> cannot be installed on this system/zone

Finally, attempting patchadd with -G:

# patchadd -G 121016-02

Validating patches...

Loading patches installed on the system...

Done!

Loading patches requested to install.

Done!

Checking patches that you specified for installation.

Done!

Approved patches will be installed in this order:

121016-02

Checking installed patches...

Verifying sufficient filesystem capacity (dry run method)...

Patch 121016-02 failed to install due to a failure produced by pkgadd.

See /var/sadm/patch/121016-02/log for details

Patchadd is terminating.

# more /var/sadm/patch/121016-02/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.

/home/hiduid/patches/121016-02/SPROcc/install/checkinstall: /home/hiduid/patches/121016-02/SPROcc/install/checkinstall: cannot open

pkgadd: ERROR: checkinstall script did not complete successfully

Dryrun complete.

No changes were made to the system.

#

lqqnguyen at 2007-7-6 14:09:37 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 9
Can you try placing the patch in /tmp and installing it from there instead of from your home directory. Let us know if this helps.
ForumModerator at 2007-7-6 14:09:37 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 10

I have exactly this problem but with patches 121016-02, 120759-05, and 121020-02. I'm running Solaris 10 1/06 x86, Sun Studio 11, and Sun Update Manager v.1.04a. The only way I could get these patches to install was to manually remove all of the packages the patch installer complained about (pkgrm SPROcc, try to apply the patch, pkgrm the next package it complained about, and so on) until it stopped complaining. Then, install the patch with smpatch (patchadd doesn't work). Once the patch is installed, pkgadd all of the packages you removed (they're in the kits/ide/packages subdirectory of the installation tarball).

This is very tedious. If Sun admits this is a bug and is working on a fix, I recommend waiting for it.

radmanly at 2007-7-6 14:09:37 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 11

> Can you try placing the patch in /tmp and installing

> it from there instead of from your home directory.

> Let us know if this helps.

Thank you, patchadd -G worked for all 4 packages once they were placed in the /tmp directory. Any idea why Sun Update Manager is having trouble with these?

lqqnguyen at 2007-7-6 14:09:37 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 12
That worked for me, too. Plus, it was much easier than my original method. :-) Thanks.
radmanly at 2007-7-6 14:09:37 > top of Java-index,Administration Tools,Sun Update Connection-System...
# 13
> Any idea why Sun Update Manager > is having trouble with these?Yes it's a combination of different issues (see earlier in th thread for the bug id's) thats currently being investigated.
ForumModerator at 2007-7-6 14:09:37 > top of Java-index,Administration Tools,Sun Update Connection-System...