Non-GUI Installer Using a State File Always Creates the /usr Symbolic Links (Doc ID 1955626.1)

Last updated on AUGUST 03, 2016

Applies to:

Oracle Solaris Studio - Version Sun Studio 12 Update 1 to 12.3 [Release 12]
Oracle Solaris on x86-64 (64-bit)
Oracle Solaris on x86 (32-bit)
Oracle Solaris on SPARC (64-bit)
Oracle Solaris on SPARC (32-bit)
Using the GUI installer to generate a state file for later replay in a non-GUI installation will result in the /usr symbolic links being created, even though they were not created during the GUI installation phase. This issue has been verified only on solaris 10 OS.

The [ --record state_file.xml ] command line flag of the GUI installer will generate a state file based on the customization specified during the GUI installation session.

This state file may be used during a subsequent non-GUI installation to replay the prior GUI installation by specifying the [ --state state_file .xml ] command line flag to the non-GUI installer.

No matter whether the option to create the /usr symbolic links was specified ( or not ) during the replay non-GUI installation the /usr symbolic links will be created.

pl. note, linux or solaris 11 OS are not applicable here.

Symptoms

On Solaris 10, the package which creates the /usr symbolic links will be installed.

The existence of this package may be determined as follows.

# pkginfo | grep SPROsslnk
application SPROsslnk                        Sun Studio 12 update 1 /usr icon and symlinks

# pkginfo | grep studio-bin-links
application SPRO-12u2-studio-bin-links       Oracle Solaris Studio /usr symlinks and icon

# pkginfo | grep studio-bin-links
application SPRO-12-3-studio-bin-links       Oracle Solaris Studio /usr symlinks and icon

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms