The Sun Studio 12 Release Notes contain last-minute installation details and other information about the software. This document applies to the English-only release of the software. For information about the multi-language release, see the Sun Studio 12 Release Notes (English, Japanese, Simplified Chinese).

Information in this document updates and extends information in the component readme files.

You can access the readme files on the Sun Developer Network (SDN) Sun Studio portal at http://developers.sun.com/sunstudio/documentation/ss12/index.html.

Contents 

1. System Requirements
2. Disk Space Requirements by Installer
3. Patches
4. Installation Information
5. Update Notification
6. IDE Information
7. Fortran Information
8. Third-Party Software Information
9. Features That Might Be Removed in a Future Release
10. Documentation Information

A. System Requirements

The Sun Studio 12 software can be installed on the Solaris^TM Operating System (Solaris OS) on SPARC® based systems, the Solaris OS on x86 based systems, and the Linux operating system. The system requirements are as follows.

To check or add swap space, see the instructions in Appendix A of the Sun Studio 12 Quick Installation guide.

B. Disk Space Requirements by Component

The suggested available disk space you need to install the Sun Studio 12 software on the Solaris OS on SPARC platforms is 1.5 GByte. The suggested available disk space you need to install the Sun Studio 12 software on the Solaris OS on x86 platforms is 1GByte. The suggested available disk space you need to install the Sun Studio 12 software on the Linux OS is 1GByte. The following table shows the size of the installed Sun Studio 12 software.

C. Patches

This section lists the required patches for this Sun Studio 12 release.

Operating System Patches

Operating system (OS) patches are provided for Sun Studio 12 software. These patches are required for the proper operation of the compilers and tools in this release.

The following required Solaris OS patches are included in this Sun Studio 12 release. These patches are installed only at your request by the prepare_system command, the batch_installer command, the graphical user interface installer, or the command-line installer. For more information, see Sun Studio 12 Installation Reference.

Note: The Kernel patches are not installed by the prepare_system command, batch_installer command, graphical user interface installer, or command-line installer, but are provided in the product download file and on the product DVD for your convenience. Before installing either of Kernel patches, read the README file included with the patch for important information on risks and proper procedure.

JDK Technology Required Operating System Patches

The following patches are required for the proper operation of the JDK technology.

These patches are installed only if you specifically request them to be installed using the prepare_system command. For more information, see Sun Studio 12 Installation Reference.

Note: Before using the prepare_system command to install the patches required by the JDK software on Solaris 10 1/06 platforms, read the README files included with the Kernel patches for important information on risks and proper procedure.

D. Installation Information

This section describes known installation issues for this Sun Studio 12 release.

Disk Space

Each filesystem written to by the Sun Studio installer should have enough space to hold the sum of all elements that will be stored in that filesystem.

For most installations, only the filesystem containing the installation directory (by default /opt on Solaris platforms and /opt/sun on Linux platforms) must have sufficient free space for a full installation. But if you specify an alternate root or are installing the Sun Studio software in multiple zones, other filesystems might be affected.

The disk space required by the Sun Studio software, in each zone in which it is installed is:

Solaris OS on SPARC based systems	1500 MB
Solaris OS on x86 based systems	1100 MB
Linux OS on x86 based systems	1000 MB

The disk space required for additional elements, per affected zone is:

NetBeans 5.5.1 IDE and NetBeans C/C++ Development Pack 5.5.1
All platforms	400 MB
JDK 1.5.0_09 software
All platforms	200 MB
Copy of prerequisite software
Solaris OS on SPARC based systems	1200 MB
Solaris OS on x86 based systems	750 MB
Linux OS on x86 based systems	200 MB

Absence of Patches Required by the JDK Not Reported

Due to a known defect, the prepare_system command, graphical user interface installer, and command-line installer do not check for the presence of the patches required by the JDK, or report the absence of these patches when listing missing prerequisite software.

These patches are not installed by the batch installer, graphical user interface installer, or command-line installer. You can install them only with the -s jdk_patches option of the prepare_system command. For the Solaris 10 1/06 platforms, this option installs required Kernel patches. Before using this option, read the READMEs included with these patches for important information on risks and proper procedure.

Exception When Uninstalling

An exception might be issued when you are running the graphical user interface uninstaller, the command-line uninstaller, or the batch mode (silent command-line) uninstaller.

The uninstaller might immediately exit with a multi-line "Exception" message. For example:

usr/bin/java -cp . uninstall_Sun_Studio_12 -nodisplay
Exception in thread "main" java.lang.NoClassDefFoundError: while resolving class: uninstall_Sun_Studio_12
at java.lang.VMClassLoader.resolveClass(java.lang.Class) (/usr/lib/libgcj.so.5.0.0)
at java.lang.Class.initializeClass() (/usr/lib/libgcj.so.5.0.0)
at java.lang.Class.forName(java.lang.String, boolean, java.lang.ClassLoader) (/usr/lib/libgcj.so.5.0.0)
...

If you receive this message, you must ensure that the version of the Java^TM runtime environment on your system is a version that is compatible with the Sun Studio installer and uninstaller.

The Sun Studio installer is compatible with the versions of the Java runtime environment found in JDK 1.5.0 software and JDK 1.6.0 software. If neither of these versions of the JDK software is installed on your system, you must install one of them. You can install the JDK 1.5.0_09 software included in the prerequisite software provided in the product download directory and on the product DVD by running the prepare_system command:

./prepare_system -s java

If you do not have access to the prerequisite software provided with the product, you can download the JDK software from http://java.sun.com/downloads

When a compatible version of the Java runtime environment is available on the system, you can run the uninstaller successfully run using a command such as:

/usr/jdk/jdk1.5.0_09/bin/java -cp . uninstall_Sun_Studio_12 -nodisplay

Installer Failure

The batch installer, graphical user interface installer, or command-line installer might fail with a brief message, complaining of "No suitable java."

For example:

./batch_installer --accept-sla
No suitable java found. Please add one to your path.

or

./installer
No suitable java found. Please add one to your path.

This message is issued because the Sun Studio installation software needs to find a compatible version of the Java runtime environment either in your search path, or at the explicit installation point /bin/java. The Sun Studio installer is compatible with the versions of the Java runtime environment found in JDK 1.5.0 software and JDK 1.6.0 software.

If you receive this message, you can add a symbolic link at /bin/java, or you can temporarily modify your search path to include a compatible Java runtime environment.

For example:

ln -s /usr/jdk/jdk1.5.0_09/bin/java /bin/java
./installer

If neither the JDK 1.5.0 software or the JDK 1.6.0 software is installed on your system, you must install one of them. You can install the JDK 1.5.0_09 software included in the prerequisite software provided in the product download directory and on the product DVD by running the prepare_system command:

./prepare_system -s java

If you do not have access to the prerequisite software provided with the product, you can download the JDK software from http://java.sun.com/downloads

prepare_system Command Failure

The prepare_system command might fail during the installation of NetBeans 5.5.1 IDE for no apparent reason.

For example:

prepare_system -s netbeans
Preparation failed at step netbeans.

This failure occurs because the NetBeans installation software needs to find a compatible version of the Java runtime environment either in your search path, or at one of these explicit installation points:

/usr/jdk/latest/bin/java
/usr/jdk/jdk1.5.0_09/bin/java

The NetBeans installer is compatible with the versions of the Java runtime environment found in JDK 1.5.0 software and JDK 1.6.0 software.

If this failure occurs, you can either temporarily modify your search path to provide a compatible version of Java runtime environment, or add a symbolic link at one of the installation points mentioned above. For example:

ln -s /usr/jdk/jdk1.6.0 /usr/jdk/latest
prepare_system -s netbeans

If neither the JDK 1.5.0 software or the JDK 1.6.0 software is installed on your system, you must install one of them. You can install the JDK 1.5.0_09 software included in the prerequisite software provided in the product download directory and on the product DVD by running the prepare_system command:

./prepare_system -s java

If you do not have access to the prerequisite software provided with the product, you can download the JDK software from http://java.sun.com/downloads

Uninstalling the Sun Studio 12 Software

If you want to uninstall an installation of the Sun Studio 12 software, use the provided uninstaller, rather than attempting to uninstall the software manually. The use of the graphical user interface installer, command-line installer, and batch mode (silent command-line) installer are described in Chapter 3 of the Sun Studio 12 Quick Installation guide.

If you experience difficulties using the uninstaller, and cannot successfully uninstall the software using it, a safe procedure for uninstalling manually is described in Chapter 3 of the Sun Studio 12 Installation Reference guide.

Installation Directory

Software installed by the Sun Studio 12 installers and prepare_system command is placed at the following locations:

On Solaris platforms (the default installation_directory is /opt)
Sun Studio 12 software	[/alternate_root]/installation_directory/SUNWspro/*
JDK software	/usr/jdk/jdk1.5.0_09/*
NetBeans 5.5.1 IDE and NetBeans C/C++ Development Pack 5.5.1	[/alternate_root]/installation-directory/netbeans-5.5.1
On Linux platforms (the default installation_directory is /opt/sun)
Sun Studio 12 software	[/alternate_root]/installation_directory/sunstudio12/*
JDK software	/usr/java/jdk1.5.0_09/*
NetBeans 5.5.1 IDE and NetBeans C/C++ Development Pack 5.5.1	[/alternate_root]/installation-directory/netbeans-5.5.1

If you specified an alternate root directory, the full path to the actual installation directory is constructed by concatenating the alternate root path followed by the installation directory path.

For example:

• On a Solaris system, you specify an alternate root path of /export/home/SS12, and do not override the default installation directory path /opt. The effective installation directory path is:

  /export/home/SS12/opt
  



• On a Solaris system, you specify the installation directory /opt/myss12/, with no alternate root directory, and request that the Sun Studio 12 software and NetBeans software be installed. This installation creates the following directories:

  /opt/myss12/SUNWspro
  /opt/myss12/netbeans-5.5.1
  

• On a Linux system, you do not specify an installation directory (leaving the default /opt/sun), nor an alternate root directory, and request that the Sun Studio 12 software and NetBeans software be installed. This installation creates the following directories:

  /opt/sun/sunstudio12
  /opt/sun/netbeans-5.5.1
  

Restrictions on Multiple Sun Studio Installations

You can have several installations of Sun Studio software on the same system with the following restrictions:

• Each release (Sun Studio 12 software, Sun Studio 11 software, etc.) can be installed only once on a given system.
• You must uninstall the Sun Studio 12 Early Access release before installing the Sun Studio 12 release.
• You must install each release of Sun Studio software in a different installation directory.
• If you have installed one or more components of Sun Studio 12 software, any future installations of Sun Studio 12 components must be installed in the same directory.

Installer Features Not Available on Linux Platforms

The following installer features are not available on Linux:

• Installation in zones
• Installation on a server for use by clients with a different architecture
• Adding symbolic links to /usr/bin and /usr/share/man

Installation Directory Path Without Leading /

If you specify an installation directory path without a leading "/" character, the installer fails, producing a multi-line error message such as:

./batch_installer --accept-sla -d opt/myss12
			          ^^^^^^^^^^ note lack of leading "/"
Task Failed: java.lang.NullPointerException
java.lang.NullPointerException
	at java.io.File.(File.java:194)
	at com.sun.install.products.UninstallUnit.mkdirs(UninstallUnit.java:504)
	at com.sun.install.products.UninstallUnit.mkdirs(UninstallUnit.java:511)
	at com.sun.install.products.UninstallUnit.install(UninstallUnit.java:575)
...

If you want to override the default installation directory path, you must specify a path beginning with the character "/".

Product Registry on Linux Platforms

Due to a known defect in the installation software, on Linux platforms previous versions of the Sun Studio software were sometimes installed without correctly updating the product registry.

If you attempt to install the Sun Studio 12 software on a Linux platform in the same directory in which previous versions of Sun Studio software were installed, the installer incorrectly proceeds silently with the installation, rather than alerting you to the collision.

Uninstalling Previous Versions of Sun Studio Software

The Sun Studio 12 batch installer, graphical user interface installer, and command-line installer do not remove previous versions of the Sun Studio software. For example, if you want to install the Sun Studio 12 software in the same installation directory in which the Sun Studio 11 sofware is installed, you must explicitly uninstall the Sun Studio 11 software.

To uninstall the Sun Studio 11 software using the batch uninstaller, type:

cd /var/sadm/prod/com.sun.studio_11
./batch_uninstall_all

To uninstall the Sun Studio 12 Early Access software using the batch uninstaller, type:

cd sun_studio_12_early_access_install_directory
java -cp . uninstall_Sun_Studio_12ea -nodisplay -noconsole

Sun Studio 12 Express releases do not need to be uninstalled, since they are installed from a tarfile containing an installed image and do not use the product registry. If you want to uninstall a Sun Studio 12 Express release, you can do so by removing the installation directory.

rm -rf sun_studio_12_express_install_directory

This method of uninstallation works only for Sun Studio Express releases. Do not use this method for any other release of Sun Studio software.

To uninstall a previous release of Sun Studio software, refer to the installation documentation for that release.

Multi-Zone Installation Issue

A known defect in the installer affects the installation of the Sun Studio 12 software on a multi-zone Solaris 10 1/06 system. If the Sun Studio 11 software is installed on the same system, and you attempt install the Sun Studio 12 software in all zones, the installer uninstalls the Sun Studio 11 software. This behavior is not correct.

Alternate Roots for Installation and Uninstallation Must Be the Same

When you are uninstalling the Sun Studio 12 software, the alternate root directory that you specify for uninstallation must match the alternate root directory that was specified for installation.

For example, if you installed the software with the following command:

./batch_installer --accept-sla -R /export/home/SunStudio

then the following command would be incorrect for uninstalling the software:

/usr/bin/java -cp . uninstall_Sun_Studio_12 -nodisplay

The correct command for uninstallation would be:

/usr/bin/java -cp . uninstall_Sun_Studio_12 -nodisplay -R /export/home/SunStudio

Effects of /usr/bin and /usr/share/man Symbolic Links, and Workarounds for Missing Links

When the installer creates symbolic links in the /usr/bin and /usr/share/man directories, it does not create links to certain binaries and man page sections. Here are the links that are not created and workarounds for accessing the unlinked binaries and man pages:

• man page sections unique to Sun Studio software

  Symbolic links to /usr/share/man/man3c++/* are not created. The man pages displayed for the sections in this directory do not contain up-to-date information. The man command does not by default search the following Sun Studio 12 man page sections:

  man3cc4
  man3f
  man3p
  man3pi
  man3x
  

  To see an up-to-date man page in any of these sections, use the -s option of the man command to specify the section. For example:

  man -s 3x rtc_api
  

• man page conflicts

  Some Sun Studio 12 man pages conflict with existing Solaris OS man pages. Symbolic links for the following man pages are not created; links to the Solaris versions are preserved.

  /usr/share/man/man1 symlinks not created: intro.1, ctags.1
  
  /usr/share/man/man3m symlinks not created: exp2.3m, feclearexcept.3m
     fegetenv.3m, fegetexceptflag.3m, fegetprec.3m, fegetround.3m,
     feholdexcept.3m, feraiseexcept.3m, fesetenv.3m, fesetexceptflag.3m,
     fesetprec.3m, fesetround.3m, fetestexcept.3m, feupdateenv.3m,
     fex_get_handling.3m, fex_get_log.3m, fex_get_log_depth.3m,
     fex_getexcepthandler.3m, fex_log_entry.3m, fex_merge_flags.3m'
     fex_set_handling.3m, fex_set_log.3m, fex_set_log_depth.3m,
     fex_setexcepthandler.3m, isinf.3m, isnormal.3m, log2.3m,
     signbit.3m, sincos.3m
  

  To access these Sun Studio man pages, use the -M path> option in the man command. For example:

  man -M /opt/SUNWspro/man exp2
  

• deprecated binaries

  /usr/bin/ptclean symlink is not created.
  /usr/share/man/man1/ptclean.1 symlink is not created. 
  

• symbolic links for editors

  Symbolic links for the gvim and xemacs are not created. The Sun Studio 12 IDE does not use these editors.

  /usr/bin symlinks not created: b2m, ellcc, etags, gnuattach,
      gnuclient, gnudoit, gvim, ootags, rcs-checkin, xemacs, xemacs-mule
  
  /usr/share/man/man1 symlinks not created: ctags.1, etags.1, gnuattach.1,
      gnuclient.1, gnudoit.1, gnuserv.1, gvim.1, xemacs-ctags.1, xemacs.1
  

Installing Sun Studio 12 Software in a Different Directory

If you have Forte Developer 6 software, Sun ONE Studio 7 software, Sun ONE Studio 8 software, Sun Studio 8 software, Sun Studio 9 software, Sun Studio 10 software, or Sun Studio 11 software installed, be sure to follow the installation instructions and install the Sun Studio 12 software in a different directory.

Installing on Solaris 10 System with NFS-mounted Filesystem Results in Incorrect pkginfo Data

If you run the batch installer on a system running the Solaris 10 OS to install the Sun Studio 12 software on a Solaris 9 NFS-mounted filesystem, then after installation the pkginfo file does not contain correct information. Install the Sun Studio 12 software with an NFS-mounted filesystem only when both the computer running the installer and the computer to which you are installing are running the same version of the Solaris OS.

E. Update Notification

The Update Notification feature periodically checks www.sun.com and communicates available changes related to your Sun Studio software, including patches and major software updates.

To view the current contents of the update file from the IDE, choose Help -> �View update information.

To initiate contact with the server and get updated information, choose Help -> �Check now for updates.

From the command line, you can view the update file at ~/.sunstudio/user_info/latest_updates.html.

If Update Notification is not able to check for updates and your system is on a network with a HTTP proxy server, you can set proxy server information by doing the following:

1. Choose Tools -> Options.
2. In the Options dialog box, select HTTP Proxy Server.
3. Type the proxy host name in the Proxy Host field and the port number in the Port field.
4. Click OK.

You can also set the proxy server information using the ALL_PROXY environment variable; for example, setenv ALL_PROXY myproxy:8080

Note: You must exit and restart the IDE for the proxy server information to be recognized by the IDE.

To disable Update Notification, set the SUNW_NO_UPDATE_NOTIFY environment variable to any value other than false.

Usage information is communicated during the Update Notification process. This information is used by Sun Microsystems to improve future Sun Studio software releases. This information is anonymous and cannot be associated to any individual or organization.

F. IDE Information

Before using the Sun Studio 12 Integrated Development Environment (IDE), read the Integrated Development Environment (IDE) readme, which is available through the documentation index page at /installation_directory/docs/index.html. The default installation directory is /opt/SUNWspro on Solaris platforms and /opt/sun/sunstudio12 on Linux platforms.

This document contains important information about setup tasks you might need to perform to ensure that the IDE operates correctly.

G. Fortran Information

Library Links on Linux Incorrect

The links for the library libfui.so on Linux are incorrect. To fix the links, remove the existing links for libfui.so from /installation-directory/sunstudio12/lib and from /installation-directory/sunstudio12/lib/amd64 and recreate the links in those directories with the command

ln -s libfui.so.1 libfui.so

If the links are not corrected, programs will link with the archive version of libfui. If programs are linked with the archive versions of some of the f95 run-time libraries and shared object versions of other of the f95 libraries, the resulting executables might fail when the shared objects are updated.

H. Third-Party Software Information

Sun Studio 12 software includes third-party technologies governed by the Sun Studio 12 THIRDPARTYLICENSEREADME (http://developers.sun.com/sunstudio/documentation/ss12/THIRDPARTYLICENSEREADME.html) and the NetBeans 5.5.1 THIRDPARTYLICENSEREADME (http://developers.sun.com/sunstudio/documentation/ss12/NetBeans551_THIRDPARTYLICENSEREADME.txt). For information on the location of the third-party source code that we provide, see the Sun Studio 12 Legal Information page (http://developers.sun.com/sunstudio/documentation/ss12/legal.html).

I. Features That Might Be Removed in a Future Release

The following features might not be supported in a future release of the Sun Studio software.

libcollector API

The libcollector API, used to provide backward compatibility for experiments collected by the Performance Analyzer, might be removed in a future release of the Sun Studio software.

J. Documentation Information

This section gives information about the documentation for this Sun Studio 12 release. Information in these release notes supersedes information in any of the other documentation.

Documentation Included With the Sun Studio 12 Release

• Online help. The online help available through the Help menu in the IDE provides task-oriented information on using all of the components of the IDE.
• Readmes. These documents describe the new features, performance enhancements, problems and workarounds, and software corrections in the Sun Studio 12 release. The release notes might contain additional information on problems and workarounds.

  You can access these documents in HTML on the SDN Sun Studio portal through the documentation index page at http://developers.sun.com/sunstudio/documentation/ss12/index.html.

• Man pages. These online reference manual pages describe user commands, libraries that are supplied with the compilers, and other types of commands. Man pages contain reference information, including command syntax, usage, and related commands.

  You can access these documents in HTML in the installed software on your local system or network through the documentation index page at file:/installation_directory/docs/index.html. You can also access these documents in HTML on the SDN Sun Studio portal through the documentation index page at http://developers.sun.com/sunstudio/documentation/ss12/index.html.

• Sun Studio 12 manuals.

  You can access the Sun Studio 12 manuals in PDF format or HTML format on docs.sun.com through the documentation index page on the SDN Sun Studio portal at http://developers.sun.com/sunstudio/documentation/ss12/index.html

Documentation Requirements

To view the documentation that is available in PDF format, you need Adobe® Acrobat Reader software. To download the software, go to http://www.adobe.com/products/acrobat/readstep.html.

Copyright © 2007 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A. All rights reserved.

U.S. Government Rights - Commercial software. Government users are subject to the Sun Microsystems, Inc. standard license agreement and applicable provisions of the FAR and its supplements. Use is subject to license terms.

This distribution may include materials developed by third parties.Parts of the product may be derived from Berkeley BSD systems, licensed from the University of California. UNIX is a registered trademark in the U.S. and in other countries, exclusively licensed through X/Open Company, Ltd.