Oracle Solaris Studio 12.2 Installation Guide

(1)

Oracle® Solaris Studio 12.2 Installation Guide

Part No: 821–1385 October 2010

(2)

This software and related documentation are provided under a license agreement containing restrictions on use and disclosure and are protected by intellectual property laws. Except as expressly permitted in your license agreement or allowed by law, you may not use, copy, reproduce, translate, broadcast, modify, license, transmit, distribute, exhibit, perform, publish, or display any part, in any form, or by any means. Reverse engineering, disassembly, or decompilation of this software, unless required by law for interoperability, is prohibited.

The information contained herein is subject to change without notice and is not warranted to be error-free. If you find any errors, please report them to us in writing.

If this is software or related software documentation that is delivered to the U.S. Government or anyone licensing it on behalf of the U.S. Government, the following notice is applicable:

U.S. GOVERNMENT RIGHTS Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are

“commercial computer software” or “commercial technical data” pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

This software or hardware is developed for general use in a variety of information management applications. It is not developed or intended for use in any inherently dangerous applications, including applications which may create a risk of personal injury. If you use this software or hardware in dangerous applications, then you shall be responsible to take all appropriate fail-safe, backup, redundancy, and other measures to ensure its safe use. Oracle Corporation and its affiliates disclaim any liability for any damages caused by use of this software or hardware in dangerous applications.

Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners.

AMD, Opteron, the AMD logo, and the AMD Opteron logo are trademarks or registered trademarks of Advanced Micro Devices. Intel and Intel Xeon are trademarks or registered trademarks of Intel Corporation. All SPARC trademarks are used under license and are trademarks or registered trademarks of SPARC International, Inc. UNIX is a registered trademark licensed through X/Open Company, Ltd.

This software or hardware and documentation may provide access to or information on content, products, and services from third parties. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to third-party content, products, and services. Oracle Corporation and its affiliates will not be responsible for any loss, costs, or damages incurred due to your access to or use of third-party content, products, or services.

Ce logiciel et la documentation qui l’accompagne sont protégés par les lois sur la propriété intellectuelle. Ils sont concédés sous licence et soumis à des restrictions d’utilisation et de divulgation. Sauf disposition de votre contrat de licence ou de la loi, vous ne pouvez pas copier, reproduire, traduire, diffuser, modifier, breveter, transmettre, distribuer, exposer, exécuter, publier ou afficher le logiciel, même partiellement, sous quelque forme et par quelque procédé que ce soit. Par ailleurs, il est interdit de procéder à toute ingénierie inverse du logiciel, de le désassembler ou de le décompiler, excepté à des fins d’interopérabilité avec des logiciels tiers ou tel que prescrit par la loi.

Les informations fournies dans ce document sont susceptibles de modification sans préavis. Par ailleurs, Oracle Corporation ne garantit pas qu’elles soient exemptes d’erreurs et vous invite, le cas échéant, à lui en faire part par écrit.

Si ce logiciel, ou la documentation qui l’accompagne, est concédé sous licence au Gouvernement des Etats-Unis, ou à toute entité qui délivre la licence de ce logiciel ou l’utilise pour le compte du Gouvernement des Etats-Unis, la notice suivante s’applique :

U.S. GOVERNMENT RIGHTS. Programs, software, databases, and related documentation and technical data delivered to U.S. Government customers are

"commercial computer software"or"commercial technical data"pursuant to the applicable Federal Acquisition Regulation and agency-specific supplemental

regulations. As such, the use, duplication, disclosure, modification, and adaptation shall be subject to the restrictions and license terms set forth in the applicable Government contract, and, to the extent applicable by the terms of the Government contract, the additional rights set forth in FAR 52.227-19, Commercial Computer Software License (December 2007). Oracle America, Inc., 500 Oracle Parkway, Redwood City, CA 94065.

Ce logiciel ou matériel a été développé pour un usage général dans le cadre d’applications de gestion des informations. Ce logiciel ou matériel n’est pas conçu ni n’est destiné à être utilisé dans des applications à risque, notamment dans des applications pouvant causer des dommages corporels. Si vous utilisez ce logiciel ou matériel dans le cadre d’applications dangereuses, il est de votre responsabilité de prendre toutes les mesures de secours, de sauvegarde, de redondance et autres mesures nécessaires à son utilisation dans des conditions optimales de sécurité. Oracle Corporation et ses affiliés déclinent toute responsabilité quant aux dommages causés par l’utilisation de ce logiciel ou matériel pour ce type d’applications.

Oracle et Java sont des marques déposées d’Oracle Corporation et/ou de ses affiliés.Tout autre nom mentionné peut correspondre à des marques appartenant à d’autres propriétaires qu’Oracle.

AMD, Opteron, le logo AMD et le logo AMD Opteron sont des marques ou des marques déposées d’Advanced Micro Devices. Intel et Intel Xeon sont des marques ou des marques déposées d’Intel Corporation. Toutes les marques SPARC sont utilisées sous licence et sont des marques ou des marques déposées de SPARC International, Inc. UNIX est une marque déposée concédé sous license par X/Open Company, Ltd.

110606@25097

(3)

Preface

TheOracle Solaris Studio 12.2 Installation Guideguide gives instructions on how to perform the following tasks:

■ Use the package installer to install the Oracle Solaris Studio 12.2 software

■ Install the required Oracle Solaris 10 patches

■ Run the Integrated Development Environment (IDE)

■ Uninstall the Oracle Solaris Studio 12.2 software

Note –This Oracle Solaris Studio release supports systems that use the SPARC and x86 families of processor architectures: UltraSPARC, SPARC64, AMD64, Pentium, and Xeon EM64T. The supported systems for the version of the Solaris operating system you are running are available in the hardware compatibility lists athttp://www.sun.com/bigadmin/hcl. These documents cite any implementation differences between the platform types.

In this document, these x86 related terms mean the following:

■ “x86” refers to the larger family of 64–bit and 32–bit x86 compatible products.

■ “x64” points out specific 64–bit information about AMD64 or EM64T systems.

■ “32–bit x86” points out specific 32–bit information about x86 based systems.

For supported systems, see the hardware compatibility lists.

Who Should Use This Book

This book is designed for system administrators who install software and for developers who use software development applications. Experience with the Oracle Solaris operating system and UNIX commands is required.

7

(8)

Accessing Oracle Solaris Studio Documentation

You can access the documentation at the following locations:

■ The documentation is available from the documentation index page at http://www.oracle.com/

technetwork/server-storage/solarisstudio/documentation/index.html.

■ Online help for all components of the IDE is available through the Help menu, as well as through the F1 key, and through Help buttons on many windows and dialog boxes, in the IDE.

■ Online help for the Performance Analyzer and the Thread Analyzer is available through the Help menu, as well as through the F1 key, and through Help buttons on many windows and dialog boxes, in the Performance Analyzer.

■ Online help for DLight and dbxtool is available through the Help menu, as through the F1 Key, and through Help button on many windows and dialog boxes, in these tools.

Documentation in Accessible Formats

The documentation is provided in accessible formats that are readable by assistive technologies for users with disabilities. You can find accessible versions of documentation as described in the following table.

Type of Documentation Format and Location of Accessible Version

Manuals and Tutorials HTML from the Oracle Solaris Studio 12.2 collection on http://docs.sun.com

What's New in the Oracle Solaris Studio 12.2 Release(information that was included in the component Readmes in previous releases)

HTML from the Oracle Solaris Studio 12.2 collection on http://docs.sun.com

Man pages In the installed product through themancommand

Online help HTML available through the Help menu Help buttons, and F1 key in the IDE, Performance Analyzer, DLight, and dbxtool.

Release notes HTML from the Oracle Solaris Studio 12.2 collection on http://docs.sun.com

Preface

(9)

Related Third-Party Web Site References

Third-party URLs are referenced in this document and provide additional, related information.

Note –Oracle is not responsible for the availability of third-party web sites mentioned in this document. Oracle does not endorse and is not responsible or liable for any content, advertising, products, or other materials that are available on or through such sites or resources. Oracle will not be responsible or liable for any actual or alleged damage or loss caused or alleged to be caused by or in connection with use of or reliance on any such content, goods, or services that are available on or through such sites or resources.

Typographic Conventions

The following table describes the typographic conventions that are used in this book.

TABLE P–1 Typographic Conventions

Typeface Meaning Example

AaBbCc123 The names of commands, files, and directories, and onscreen computer output

Edit your.loginfile.

Usels -ato list all files.

machine_name% you have mail.

AaBbCc123 What you type, contrasted with onscreen computer output

machine_name%su Password:

aabbcc123 Placeholder: replace with a real name or value The command to remove a file isrm filename.

AaBbCc123 Book titles, new terms, and terms to be emphasized

Read Chapter 6 in theUser's Guide.

Acacheis a copy that is stored locally.

Donotsave the file.

Note:Some emphasized items appear bold online.

Preface

9

(10)

Shell Prompts in Command Examples

The following table shows the default UNIX system prompt and superuser prompt for shells that are included in the Solaris OS. Note that the default system prompt that is displayed in command examples varies, depending on the Solaris release.

TABLE P–2 Shell Prompts

Shell Prompt

Bash shell, Korn shell, and Bourne shell $ Bash shell, Korn shell, and Bourne shell for superuser #

C shell machine_name%

C shell for superuser machine_name#

Documentation, Support, and Training

See the following web sites for additional resources:

■ Documentation (http://docs.sun.com)

■ Support (http://www.oracle.com/us/support/systems/index.html)

■ Training (http://education.oracle.com)– Click the Sun link in the left navigation bar.

Oracle Welcomes Your Comments

Oracle welcomes your comments and suggestions on the quality and usefulness of its documentation. If you find any errors or have any other suggestions for improvement, go to http://docs.sun.comand click Feedback. Indicate the title and part number of the documentation along with the chapter, section, and page number, if available. Please let us know if you want a reply.

Oracle Technology Network (http://www.oracle.com/technetwork/index.html)offers a range of resources related to Oracle software:

■ Discuss technical problems and solutions on theDiscussion Forums (http://forums.oracle.com).

■ Get hands-on step-by-step tutorials withOracle By Example (http://www.oracle.com/

technology/obe/start/index.html).

■ DownloadSample Code (http://www.oracle.com/technology/sample_code/

index.html).

Preface

(11)

Preparing for Installation

This chapter includes information about the following:

■ “Software Installation Overview” on page 11

■ “System Requirements” on page 12

■ “Choosing Local or Remote Display of the Installer” on page 13

■ “Installing to an NFS-Mounted Filesystem” on page 14

■ “Choosing an Installation Method” on page 15

Software Installation Overview

The following steps outline the general process you follow to install the Oracle Solaris Studio 12.2 software, product serial number, and supporting software.

Step Task Description For Instructions

1. Verify that the system on which you are installing the Oracle Solaris Studio 12.2 software meets the minimum hardware and operating system requirements for this release.

Using a system that meets the system requirements is recommended for proper performance.

See“System Requirements” on page 12

2. Determine whether you are going to display the installer locally or remotely.

You can install the Oracle Solaris Studio software using a remote display or local display.

See“Choosing Local or Remote Display of the Installer” on page 13 3. Choose an installation method. There are two ways to install

the Oracle Solaris Studio software.

See“Choosing an Installation Method” on page 15

4. Install the Oracle Solaris Studio 12.2 software and the required OS patches.

Step through the installation information.

See“Installing the Oracle Solaris Studio Software” on page 17

1

C H A P T E R 1

11

(12)

System Requirements

Oracle Solaris Studio 12.2 software supports the hardware and operating system requirements shown inTable 1–1.

Note –For further disk space requirements and important last minute information about this release, see the release notes athttp://docs.sun.com/app/docs/doc/821-1785.

TABLE 1–1 System Requirements

Solaris OS on SPARC based systems

Solaris OS on x86 based

systems Linux OS on x86 based systems Operating system Solaris 10 1/06 and subsequent Solaris 10 OS

updates

SuSE Linux Enterprise Server 11

RedHat Enterprise Linux 5 Oracle Enterprise Linux 5

CPU Sun UltraSPARC-based systems

Fujitsu SPARC64 platform-based systems

32 and 64 bit systems (Pentium class or newer) based on AMD and Intel x86 CPUs

Memory Recommended: 1 to 2 GB

Minimum: 512 MB (more may be needed for working with large projects in the IDE)

Temporary disk space required by the installer

1.8 GB 1.5 GB 1 GB

Disk space required by the installed product (Use the df -kcommand to check your disk space.)

1.4 GB 1.13 GB 1.12 GB

Swap space Recommended: 2 to 4 GB

Minimum: 1 GB

To add swap space to your system, see“Adding Swap Space” on page 37 Operating system

configuration

For the Solaris 10 OS: Entire Solaris Software Group Plus OEM Support, Entire Solaris Software Group, or Developer Solaris Software Group (To determine your operating system configuration, you need to verify the installed packages. Specific packages are installed for each configuration. See the Solaris OS installation documentation for more details.)

Linux OS must include the Development/Libraries Package Group.

System Requirements

(13)

Java SE Development Kit (JDK) 6 Update 13 or later is required to run the IDE, dbxtool, DLight, and Performance Analyzer. If you plan to use these tools and do not have the required JDK, you can download the JDK fromhttp://www.oracle.com/technetwork/java/javase/

downloads/index.htmland install it after you have installed Oracle Solaris Studio.

Choosing Local or Remote Display of the Installer

You can display the installer either locally or remotely while you are installing the Oracle Solaris Studio 12.2 software:

■ Local display.The source computer and the display computer are the same computer.The GUI installer window or non-GUI installer messages are displayed on the same computer that contains the product DVD or downloaded files and runs the installer.

■ Remote display.The source computer and the display computer are different computers.

The source computer contains the product DVD or downloaded files and runs the installer.

The display computer displays the GUI installer window or non-GUI installer messages. To install using a remote display, follow the instructions in the remainder of this section.

▼

Preparing for Installation Using a Remote Display

On the display computer, enable client access to the X server by typing the following on the command line:

xhost + source-computer-name

Replacesource-computer-namewith the output of the/usr/bin/hostnamecommand entered on the source computer, which is the computer that contains the product DVD or downloaded files.

Log in to the source computer and become a superuser (root).

rlogin source-computer-name -l rootname Password: root-password

On the source computer, set the display to the monitor that is attached to the display computer.

If you use the C shell, type:

setenv DISPLAY display-computer-name:n.n If you use the Bourne shell, type:

DISPLAY=display-computer-name:n.n export DISPLAY

If you use the Korn shell, type:

export DISPLAY=display-computer-name:n.n 1

2

3

Choosing Local or Remote Display of the Installer

Chapter 1 • Preparing for Installation 13

(14)

Replacedisplay-computer-namewith the output of the/usr/bin/hostnameentered on the display computer.

Installing to an NFS-Mounted Filesystem

To install the Oracle Solaris Studio software on an NFS-mounted filesystem, you must run the installer on a supported system regardless of where the NFS partition is mounted. In the following procedure, the server is the machine with the physical disk on which the installed software will reside, and the client is the machine on which you run the installer and which NFS-mounts the filesystem from the server.

Note –The best way to share the product image as an NFS-mounted filesystem is to export it from a supported system. Run the installer on the server and share the directory in which the software is installed. Use the following NFS install procedure only if your NFS server is not a supported platform for the product.

After mounting the filesystem you can install the Oracle Solaris Studio product on the server by running the graphical user interface (GUI) installer or non-GUI installer on the client machine.

You would specify the directory on which you mounted the filesystem as the installation directory for the Oracle Solaris Studio 12.2 software.

After you have installed the software, any machine that is running the Oracle Solaris 10 OS can mount the filesystem from the server on which you installed the software, and run the software.

Each client machine that runs the software must have the required OS patches installed (see Appendix D, “Patch Identification Numbers and Descriptions”). You can install the patches using theinstall_patchesutility (see“Installing the Required Oracle Solaris OS Patches” on page 23.

To uninstall Oracle Solaris Studio software installed on an NFS-mounted filesystem, you must run the uninstaller on the same client machine you used to install the software, and you must mount the filesystem prior to running the uninstaller.

▼

To Prepare for Installing the Oracle Solaris Studio Software on an NFS-mounted Filesystem

On the server machine, share the filesystem with the appropriate options. It is essential that root on the client machine on which the installer will be run have full access to the NFS filesystem:

share -F nfs -o root=client-machine,rw filesystem 1

Installing to an NFS-Mounted Filesystem

(15)

On the client machine, mount the shared filesystem with read/write access:

mount server-machine:filesystem installation-directory

Choosing an Installation Method

There are two ways to install the Oracle Solaris Studio 12.2 software:

Package installer, graphical user interface (GUI) mode

The graphical user interface installer is an installation wizard that displays pages for a series of installation steps.

On each page, you can quit, go back to the previous step, or go on to the next step. You can choose the installation directory and which components of the Oracle Solaris Studio 12.2 software you want to install. Or you can run the installer to install only the runtime libraries.

Package installer, non-GUI mode The non-GUI mode of the package installer installs all components of the Oracle Solaris Studio 12.2, or only the runtime libraries, silently.

2

Choosing an Installation Method

Chapter 1 • Preparing for Installation 15

(16)

16

(17)

Installing the Oracle Solaris Studio 12.2 Software

■ “Installing the Oracle Solaris Studio Software” on page 17

■ “Installing the Required Oracle Solaris OS Patches” on page 23

■ “Setting Up Access to the Developer Tools and Man Pages” on page 23

■ “Starting the Oracle Solaris Studio 12.2 IDE” on page 24

Installing the Oracle Solaris Studio Software

You can install the Oracle Solaris Studio 12.2 software and the required OS patches on a single-user system. Or you can install the software and OS patches on a server for use by client systems with the same architecture, and then install the OS patches on each client system that will access the Oracle Solaris Studio software on the server.

Tip –Installation from a network location can take a significant amount of time, so if possible, make a copy of the installation bundle on each system where you plan to install the software, and run the installer locally.

Installing in a Zone

To install the software in a zone on a Solaris 10 system, run the installer in that zone. If you are installing in the global zone and want the software to be available in that zone only, select the Install in current zone only checkbox in the GUI installer, or specify the--current-zone-only option when starting the non-GUI installer.

2

C H A P T E R 2

17

(18)

Installing in an Alternate Root Directory

To install the software using an alternate root directory, use the non-GUI installer with the --use-alternative-rootdirectoryoption.

Installing on Multiple Systems

To install the software on multiple systems, you can use the--recordstate_file.xmloption when starting the GUI installer to record an installation that you can repeat using the--state state_file.xmloption with the non-GUI installer.

Installing Oracle Solaris Studio With the Graphical User Interface Installer

The graphical user interface (GUI) installer lets you choose the installation directory and select which components of the Oracle Solaris Studio 12.2 software you want to install. For a complete list of the valid command-line options when starting the GUI installer, see“Command-Line Options for the GUI Installer” on page 33.

The GUI installer requires the Java 2 Software Development Kit (JDK) 5, Update 3.

▼

Using the Graphical User Interface Installer

If you are not currently superuser (root), become superuser by typing:

su

Password: root-password

In the directory that contains the installer, start the installer by typing:

./SolarisStudio12.2-OS-platform-pkg-ML.sh

The System Analysis page tells you:

■ If your system is missing any of the required OS patches.

If you need to install these patches, you can do so by:

■ Clicking More Info and then clicking Execute install_patches.sh now.

■ Running theinstall_patches.shutility from the command line after you have installed Oracle Solaris Studio.

For a complete list of the valid command-line options when starting the

install_patches.shutility, see“Command-Line Options for theinstall_patches.sh Utility” on page 35

1

2

3

Installing the Oracle Solaris Studio Software

(19)

The required OS patches must also be installed with theinstall_patches.shutility on client systems that will use the Oracle Solaris Studio 12.2 software on a server. For more information, see“Installing the Required Oracle Solaris OS Patches” on page 23.

■ If your system does not have JDK 6, Update 13, which is required for running the IDE, dbxtool, DLight, and the Performance Analyzer. If you plan to use these tools, you can download the required JDK fromhttp://www.oracle.com/technetwork/java/javase/

downloads/index.html.

The Oracle Solaris Studio Installer page gives you the option of selecting which components of the Oracle Solaris Studio software to install:

a. Click Next if you want to install all components of the software.

b. Click Customize if you want to select which components of the software to install. The Customize Installation dialog box lists the components and indicates which, if any,

components are already installed. Click the checkbox for any component you do not want to install to remove the checkmark. Click OK, then click Next.

Note –To install only the runtime libraries, you must have specified the--libraries-only option when you started the installer (see“Installing the Runtime Libraries Only With the GUI Installer” on page 20.

On the Oracle Solaris Studio Installation page:

a. Specify a different installation directory if you do not want to install the software in the default installation directory/opt. If you already have some components of Oracle Solaris Studio 12.2 software installed, the installer will install additional components only in the same directory.

b. By default, the installer creates symbolic links in the/usr/bindirectory and the

/usr/share/mandirectory to the Oracle Solaris Studio 12.2 software and man pages. If you already have symbolic links in/usr/binand/usr/share/manto a previous Sun Studio release, the links to Oracle Solaris Studio 12.2 will replace them. If you do not want the symbolic links created, or you do not want links to a previous release replaced, click the Create symbolic links in /usr/bin checkbox to remove the checkmark. (If you already have the links to Oracle Solaris Studio 12.2 installed, the checkbox is not displayed.)

c. If you are running the installer on a system that has zones, the Install Oracle Solaris Studio software to current zone only checkbox is displayed. By default, the installer installs the software to the current zone only. If you want the software installed to all zones, click the checkbox to remove the checkmark. When you run the installer in the global zone, installing in the current zone only makes the installed product visible only in the global zone.

d. Click Next.

4

5

Chapter 2 • Installing the Oracle Solaris Studio 12.2 Software 19

(20)

On the Summary page, verify that the list of components to be installed is correct and that you have adequate space on your system for installation. Then click Install to start the installation.

When the installation is complete, the Setup Complete page is displayed. Click Finish to exit the installer.

After installation, the installer opens a web browser and asks you to use your Sun Online Account to register your copy of Oracle Solaris Studio with the Sun Inventory. Registration is not required, but it allows you to organize your products in the Sun Inventory and receive timely information from Sun. The installer also registers this copy of Oracle Solaris Studio in your local Service Tags database (if this service is available).

If Oracle Solaris Studio 12.2 is going to be used from client systems, then on each client system, set thePATHandMANPATHto access the Oracle Solaris Studio 12.2 software and man pages on the server (see“Setting Up Access to the Developer Tools and Man Pages”on page 23).

If you installed the Oracle Solaris Studio 12.2 software on a single-user system, type the following to determine whether you need to set up your access to the Oracle Solaris Studio 12.2 software tools and man pages:

/usr/bin/version

a. If you receive the message/usr/bin/version: not foundor the command reports an earlier version of Sun Studio software, see“Setting Up Access to the Developer Tools and Man Pages”on page 23for information on setting yourPATHandMANPATHto point to the Oracle Solaris Studio 12.2 software.

b. If the command reports Oracle Solaris Studio 12.2 software, you do not need to set yourPATH andMANPATH.

Installing the Runtime Libraries Only With the GUI Installer

You can use the GUI installer to install the Oracle Solaris Studio runtime libraries only.

Note –If you run the installer to install only the libraries, you cannot run the installer later to install additional components without first running the uninstaller to uninstall the libraries.

▼

Using the Graphical User Interface Installer

su

Password: root-password 6

7

8

9

10

1

(21)

./SolarisStudio12.2-OS-platform-pkg-ML.sh --libraries-only

On the Oracle Solaris Studio Installer page, click Next.

On the Oracle Solaris Studio Installation page, specify a different installation directory if you do not want to install the libraries in the default installation directory/opt.

On the Summary page, verify that you have adequate space on your system for installation.

Then click Install to start the installation.

When the installation is complete, the Setup Complete page is displayed. Click Finish to exit the installer.

Installing Oracle Solaris Studio With the Non-GUI Installer

By default, the non-GUI installer installs all components of the Oracle Solaris Studio 12.2 software silently in the default installation directory. You can start the installer with the --installation-locationdirectoryoption to install all components in a directory of your choice. You can start the installer with the--libraries-onlyto install the runtime libraries only (see“Installing the Runtime Libraries Only With the Non-GUI Installer” on page 22). For a complete list of the valid command-line options when starting the non-GUI installer, see

“Command-Line Options for the Non-GUI Installer” on page 34.

▼

Using the Non-GUI Installer

su

./SolarisStudio12.2-OS-platform-pkg-ML.sh --non-interactive

The installer runs silently and returns your prompt when installation is complete. It writes a log file in the/root/.nbi/logsdirectory.

If the Oracle Solaris Studio 12.2 is going to be used from client systems, then on each client system, set thePATHandMANPATHto access the Oracle Solaris Studio 12.2 software and man pages on the server (see“Setting Up Access to the Developer Tools and Man Pages”on page 23).

2

3 4

5

6

1

2

3

4

(22)

If you installed the Oracle Solaris Studio 12.2 software on a single-user system, type the following to determine whether you need to set up your access to the Oracle Solaris Studio 12.2 software tools and man pages:

/usr/bin/version

a. If you receive the message/usr/bin/version: not foundor the command reports an earlier version of Sun Studio software, see“Setting Up Access to the Developer Tools and Man Pages”on page 23for information on setting yourPATHandMANPATHto point to the Oracle Solaris Studio 12.2 software.

b. If the command reports Oracle Solaris Studio 12.2 software, you do not need to set yourPATH andMANPATH.

Installing the Runtime Libraries Only With the Non-GUI Installer

You can use the non-GUI installer to install the Oracle Solaris Studio Runtime Libraries only.

Note –If you run the installer to install only the libraries, you cannot run the installer later to install The Oracle Solaris Studio software without first running the uninstaller to uninstall the libraries.

▼

Using the Non-GUI Installer

su

./SolarisStudio12.2-OS-platform-pkg-ML.sh --non-interactive --libraries-only

The installer runs silently and returns your prompt when installation is complete. It writes a log file in the/root/.nbi/logsdirectory.

5

1

2

3

(23)

Installing the Required Oracle Solaris OS Patches

Several operating system patches are required for the proper operation of the compilers and tools in the Oracle Solaris Studio 12.2 release on the Solaris OS (seeAppendix D, “Patch Identification Numbers and Descriptions”). To install the required Solaris OS patches, you can run theinstall_patches.shutility that is included in the product download.

If you are running the GUI installer, the System Analysis page informs you if your system does not have the required OS patches. You can then run theinstall_patches.shutility by clicking More info, and then clicking Execute install_patches.sh now.

If you are running the non-GUI installer, run theinstall_patches.shutility after installation to ensure that your system has the required OS patches.

If you have installed the Oracle Solaris Studio 12.2 software on a server and it is going to be used from client systems, then do the following:

1. On each client system, mount the directory on the server into which you downloaded the package installer.

mount server:filesystem download_directory

2. On each client system, run theinstall_patches.shutility to install the required Solaris OS patches.

Setting Up Access to the Developer Tools and Man Pages

Because the Oracle Solaris Studio 12.2 software product components and man pages are not installed into the system directories/usr/bin/and/usr/share/man, you might need to change yourPATHandMANPATHenvironment variables to enable use of the Oracle Solaris Studio 12.2 software.

You do not need to change your paths if:

■ You did not previously install Sun Studio 11 software, Sun Studio 12 software, or Sun Studio 12 Update 1 software on your system.

■ The response to the command/usr/bin/versionis Oracle Solaris Studio 12.2 software.

On Solaris platforms, add the path/installation_directory/solstudio12.2/binto yourPATH environment variable. On Linux platforms, add the path

/installation_directory/oracle/solstudio12.2/binto yourPATHenvironment variable. If you have previous versions of Sun Studio, Sun ONE Studio, or Forte Developer software installed, add the path before the paths of the previous installations.

On Solaris platforms, add the path/installation_directory/solstudio12.2/man/to your MANPATHenvironment variable. On Linux platforms, add the path

/installation_directory/sun/solstudio12.2/man/to yourMANPATHenvironment variable.

Setting Up Access to the Developer Tools and Man Pages

(24)

Starting the Oracle Solaris Studio 12.2 IDE

Once you have the Oracle Solaris Studio 12.2 software and the required OS patches installed, and have added the software installation directory to your path, you can start using the software. To start the IDE, type the following:

solstudio &

Note –The full path to the command is/installation_directory/solstudio12.2/bin/solstudio on Solaris systems, and/installation_directory/oracle/solstudio12.2/bin/solstudioon Linux platforms.

Starting the Oracle Solaris Studio 12.2 IDE

(25)

Uninstalling the Oracle Solaris Studio 12.2 Software

■ “Uninstalling When Previous Releases of Sun Studio Software Are Installed” on page 25

■ “Choosing Local Display or Remote Display of the Uninstaller” on page 25

■ “Uninstalling the Software” on page 26

Uninstalling When Previous Releases of Sun Studio Software Are Installed

If you installed the Oracle Solaris Studio 12.2 software on a system that has previous Sun Studio software installations, then only Oracle Solaris Studio 12.2 is removed when you run the uninstaller. The uninstaller removes all of the installed product components.

Choosing Local Display or Remote Display of the Uninstaller

You can display an uninstaller either locally or remotely while you are uninstalling Oracle Solaris Studio 12.2 software.

▼

Preparing for Uninstallation Using a Remote Display

On the display computer, enable client access to the X server by typing the following on the command line:

xhost + source-computer-name

Replacesource-computer-namewith the output of the/usr/bin/hostnamecommand entered on the source computer, which is the computer that contains the product CD-ROM or downloaded files.

3

C H A P T E R 3

1

25

(26)

Log in to the source computer and become a superuser (root).

rlogin source-computer-name -l rootname Password: root-password

On the source computer, set the display to the monitor that is attached to the display computer.

If you use the C shell, type:

setenv DISPLAY display-computer-name:n.n If you use the Bourne shell, type:

DISPLAY=display-computer-name:n.n export DISPLAY

If you use the Korn shell, type:

export DISPLAY=display-computer-name:n.n

Replacedisplay-computer-namewith the output of the/usr/bin/hostnameentered on the display computer.

Uninstalling the Software

You can uninstall all of the installed components of the Oracle Solaris Studio 12.2 software using the graphical user interface uninstaller or the non-GUI uninstaller.

▼

Using the Graphical User Interface Uninstaller

su

Go to the installation directory, for example,/opt/solstudio12.2.

Start the GUI uninstaller by typing:

./uninstall.sh &

On the Summary page, click Uninstall to start the uninstallation.

When the uninstallation is complete, the Setup Complete page is displayed. Click Finish to exit the uninstaller.

2

3

1

2 3

4 5 Uninstalling the Software

(27)

▼

Using the Non-GUI Uninstaller

su

Go to the installation directory, for example,/opt/sunstudio12.2.

Start the non-GUI uninstaller by typing:

./uninstall.sh --non-interactive

The uninstaller runs silently and returns your prompt when uninstallation is complete.

1

2 3

4

Uninstalling the Software

Chapter 3 • Uninstalling the Oracle Solaris Studio 12.2 Software 27

(28)

28

(29)

Troubleshooting

This chapter describes how to fix problems that can occur during Oracle Solaris Studio 12.2 installation and uninstallation.

The chapter includes information about the following:

■ “GUI Installer Will Fail IfTMPDIRPoints to Non World-Writable Directory” on page 29

■ “GNOME Errors Might Occur When Starting GUI Installer” on page 30

■ “Installer Lock File Might Prevent Installer From Starting” on page 30

■ “Fixing a Failed Installation or Uninstallation” on page 30

■ “Installation Will Fail on an NFS-Mounted Filesystem If Write Permission is Not Set” on page 32

■ “Viewing the Installation Log File” on page 32

GUI Installer Will Fail If TMPDIR Points to Non World-Writable Directory

If you choose to install the symbolic links to Oracle Solaris Studio software in the/usr/binand /usr/man/sharedirectories, and yourTMPDIRenvironment variable is pointing to a directory that is not world-writable, then the GUI installer will fail to complete installation. To ensure that this situation does not occur, unset yourTMPDIRenvironment variable or set it to a world-writable directory before starting the installer.

4

C H A P T E R 4

29

(30)

GNOME Errors Might Occur When Starting GUI Installer

On some systems, GNOME errors might occur when you start the GUI installer. If such errors prevent the GUI installer from starting, use the non-GUI installer.

Installer Lock File Might Prevent Installer From Starting

If the installer is interrupted or quits without completing the installation, a lock file might prevent you from restarting the installer. If you receive a message that an instance of the installer is already running when you try to start the installer, you might need to remove a lock file from the/root/.nbidirectory.

Fixing a Failed Installation or Uninstallation

On Solaris platforms, the installer stores information on which Oracle Solaris Studio 12.2 packages it has installed in two places:

■ Theproductregistryfile, the Solaris Product Registry database

■ The/root/.nbidirectory

On Linux platforms, the installer stores information on which Oracle Solaris Studio 12.2 packages it has installed in two places:

■ The database of installed packages

■ The/root/.nbidirectory

If some packages were not properly installed, you will have problems using the Oracle Solaris Studio software, and you might have problems installing additional components or uninstalling the software.

For example, if the installer quit before installation was complete, the uninstaller

(uninstall.sh) might not be present in your installation directory. Or if you used thepkgadd command to install any of the packages, theproductregistryfile or theproduct-cache directory in the/root/.nbidirectory might be corrupted. In such cases, the uninstaller cannot uninstall the packages and you need to remove them in the correct way in order to be able to rerun the installer.

If the uninstaller quits before all the product files are deleted, rerunning the uninstaller will not delete the remaining files and you need to remove them in the correct way to complete the uninstallation of the product.

Do not uninstall the product by removing the installation directory. Packages will still be registered in theproductregistrydatabase and the/root/.nbidirectory, and the installer will not run.

GNOME Errors Might Occur When Starting GUI Installer

(31)

▼

Fixing a Failed Installation or Uninstallation on Solaris Platforms

Become superuser by typing:

su

Open the Solaris Product Registry tool by typing:

/usr/bin/prodreg &

In the left pane of the tool, expand the Unclassified Software node.

Select all of the package names containing Oracle Solaris Studio 12.2 and click Uninstall. Follow the instructions to remove the packages.

Click Exit to exit the tool.

Remove the/root/.nbidirectory by typing:

rm -r /.nbi

▼

Fixing a Failed Installation or Uninstallation on Linux Platforms

Become superuser by typing:

su

Find all of the Oracle Solaris Studio packages by typing:

rpm -q -a | grep solstudio12.2

Remove each Oracle Solaris Studio 12.2 rpm package by typing:

rpm -e package-name

Oracle Solaris Studio 12.2 rpm packages have the suffix12.2-1, for example,

solstudio12u2-cc-12.2-1. Be careful not to remove packages from Sun Studio releases, which have different suffixes.

Remove the/root/.nbidirectory by typing:

rm -r /.nbi 1

2

3 4

5 6

1

2

3

4

Fixing a Failed Installation or Uninstallation

Chapter 4 • Troubleshooting 31

(32)

Installation Will Fail on an NFS-Mounted Filesystem If Write Permission is Not Set

If installation fails on an NFS-mounted filesystem, ensure that you have write permission on that filesystem. You can check for write permission by following these instructions. For information about installing on an NFS-mounted filesystem, see“Installing to an NFS-Mounted Filesystem” on page 14.

1. Check for write permission by typing:

touch /net/remote-system/opt/testfile

If you receive an error message, then you do not have write permission. For example:

touch /net/harker/opt/testfile

touch: /net/harker/opt/testfile cannot create

2. Choose another installation directory on which you have write permission, or contact your system administrator to change the filesystem permissions.

Viewing the Installation Log File

When you install the Oracle Solaris Studio 12.2 software, a log file that contains a record of the installation session is automatically generated. Log files are stored in the/root/.nbi/logs directory.

Installation Will Fail on an NFS-Mounted Filesystem If Write Permission is Not Set

(33)

Command-Line Options for the

Installer,Uninstaller,and install_patches Utility

Command-Line Options for the GUI Installer

The following command-line options are valid when you are starting the GUI installer.

--current-zone-only Install only in the current zone. When you run the installer in the global zone, this option makes the installed product available only in that zone.

--help Display information on the options.

--javahomedirectory Use the JDK in directory when running the installer.

This option is needed when the installer cannot locate a JDK in a standard location on your system, and you need to point it to one.

--libraries-only Perform runtime libraries only installation.

--localelocale Override the default locale for the installer with the specified locale. Valid locales areen(English),ja (Japanese), andzh(Simplified Chinese).

--outputoutput_file Write all installer output to the specified file.

--recordstate_file.xml Record an installer session in the GUI installer so that you can use repeat the installation on another system with the non-GUI installer. This option is especially useful when you want to install a subset of the product components on multiple systems.

--tempdirdirectory By default, the installer extracts temporary data into the/tmpdirectory. If there is not sufficient space in the /tmpdirectory on your system, you can specify another directory for the installer to use.

--verbose Write verbose output to the console.

A

A P P E N D I X A

33

(34)

Command-Line Options for the Non-GUI Installer

The following command-line options are valid when you are starting the non-GUI installer.

--create-symlinks Create symbolic links in the/usr/binand /usr/share/mandirectories to the Oracle Solaris Studio 12.2 software and man pages.

--current-zone-only Install only in the current zone. When you run the installer in the global zone, this option makes the installed product visible only in that zone.

--extract-installation-datadirectory Extract installation data, do not perform installation.

--help Display information on the options.

--installation-locationdirectory Install Oracle Solaris Studio software in the specified directory instead of in the default installation directory/opt.

--javahomedirectory Use the JDK in directory when running the installer.

This option is needed when the installer cannot locate a JDK in a standard location on your system, and you need to point it to one.

--libraries-only Perform runtime libraries only installation.

--localelocale Override the default locale for the installer with the specified locale. Valid locales areen(English),ja (Japanese), andzh(Simplified Chinese).

--non-interactive Start the installer in non-GUI mode.

--silent-logs-dirdirectory Write the installer log file to the specified directory.

--statestate_file.xml Play back the state file recorded by the GUI installer to silently repeat an installation session. This option lets you install a subset of the product components in non-GUI mode.

--tempdirdirectory By default, the installer extracts temporary data into the/tmpdirectory. If there is not sufficient space in the /tmpdirectory on your system, you can specify another directory for the installer to use.

--use-alternative-rootdirectory Install in the specified root directory instead of the default root directory/. Specify the full path of the directory to use as the alternate root. This option is valid only on systems running the Solaris OS.

--verbose Write verbose output to the console.

Command-Line Options for the Non-GUI Installer

(35)

Command-Line Options for the Uninstaller

The following options are valid when starting the uninstaller.

--localelocale Override the default locale for the uninstaller with the specified locale. Valid locales areen(English),ja (Japanese), andzh(Simplified Chinese). This option is valid only for the GUI uninstaller.

--non-interactive Run the uninstaller in non-GUI mode and uninstall installed components of the software.

--outputoutput_file Write all uninstaller output to the specified file. This option is valid only for the GUI uninstaller.

--use-alternative-rootdirectory Uninstall from the specified root directory instead of the default root directory/. This option is valid only for the non-GUI uninstaller.

Command-Line Options for the install_patches.sh Utility

The following options are valid when starting theinstall_patches.shutility.

-G Add patches to packages in the current zone only.

When you run the utility in the global zone, this option makes the patches available in that zone only.

-p Install Oracle Solaris Studio product patches if

available. If you specify this option and no product patches are available, the utility displays a message telling you so.

-llocale Override the default locale for the utility with the

specified locale. Valid locales areen(English),ja (Japanese), andzh(Simplified Chinese).

-Rdirectory Install patches in the specified root directory instead

of the default root directory/. Specify the full path of the directory to use as the alternate root.

-h Display information on the options.

Command-Line Options for theinstall_patches.shUtility

Appendix A • Command-Line Options for the Installer,Uninstaller,andinstall_patchesUtility 35

(36)

36

(37)

Adding Swap Space

If the system on which you are installing the software does not have the required minimum 1 GB of swap space, add swap space by doing the following.

▼

Adding Swap Space on a Solaris System

Become a superuser (root) by typing:

% su

Create a file in a selected directory to add swap space by typing:

mkfile number[m|k|b] /directory/swap-file-name

wherenumberis an amount of swap space, followed by eithermfor megabyte,kfor kilobyte, orb for block. Thedirectoryis a directory in which you have permission to add swap space. The swap-file-nameis the name of the swap file you are creating.

For example, to create a 16-megabyte swap file named16mswapin thefoodirectory, type the following:

mkfile 16m /foo/16mswap

See themkfile(1M) man page for more information.

Verify that the file was created by typing:

ls -l /directory/swap-file-name

The new file appears in the directory. For example:

ls -l /foo/16mswap

-rw---T 1 root other 16777216 Dec 12 14:24 /foo/16mswap

B

A P P E N D I X B

1

2

3

37

(38)

Run theswapcommand to specify the additional swap space by typing:

swap -a /directory/swap-file-name

Verify that the extra swap space was added by typing:

swap -s

The output shows the allocated swap space. For example:

swap -s

total: 289336k bytes allocated + 27008k reserved = 316344k used, 298336k available

▼

Adding Swap Space on a Linux System

Become a superuser (root) by typing:

% su

Create a file in a selected directory to add swap space by typing:

dd if=/dev/zero of=/dir/myswapfile bs=1024 count=number_blocks_needed

wherediris a directory in which you have permission to add swap space. Themyswapfileis the name of the swap file you are creating. Thenumber_blocks_neededis an amount of 1024-byte blocks you want to create. See thedd(1) man page for more information.

Verify that the file was created by typing:

ls -l /dir/myswapfile

The new file appears in the directory.

Initialize the new swap area by typing:

mkswap /dir/myswapfile

See themkswap(8) man page for more detailed information.

Run theswaponcommand to enable the new swap space for paging and swapping by typing the following:

swapon -a /dir/myswapfile

Verify that the extra swap space was added by typing:

swapon -s

The output shows the allocated swap space.

4

5

1

2

3

4

5

6 Adding Swap Space

(39)

Oracle Solaris 12.2 Components and Packages

This appendix lists the components, and packages that comprise the Oracle Solaris Studio 12.2 software.

Table C–1lists the Oracle Solaris Studio 12.2 software package configuration and component information for the Solaris OS on SPARC based systems.

Table C–2lists the Oracle Solaris Studio 12.2 software package configuration and component information for the Solaris OS on x86 based systems.

Table C–3lists the Oracle Solaris Studio 12.2 RPM package and component information for Linux platforms.

TABLE C–1 Oracle Solaris Studio 12.2 Components and Packages for SPARC Based Systems

Component Packages

C and C++ Compilers SPRO-12u2-cc

SPRO-12u2-c++

SPRO-12u2-c++-libs

Fortran Compiler SPRO-12u2-fortran

SPRO-12u2-f90-libs

dbx Debugger SPRO-12u2-dbx

dbxtool SPRO-12u2-dbxtool

dmake SPRO-12u2-dmake

IDE SPRO-12u2-studio-ide

SPRO-12u2-netbeans

DLight Observability Tool SPRO-12u2-dlight

C

A P P E N D I X C

39

Oracle Solaris Studio 12.2 Installation Guide