Contents
1. Sun Studio Express –
February 2007 Early Access Release
2.
System and Hardware Requirements
3.
Installing This Sun Studio Express Build
4. Update
Notification
5. New and Changed
Features
6. Additional Notes
7. Usage Tracking Enabled
1. Sun Studio Express – February 2007 Early Access Release
Welcome to the Sun Studio Express Program: your opportunity to get
a window into our early development process and to shape future
decisions by giving us your feedback.
It is our top priority to hear what you have to say. Experiment with the
bits, participate in forums, and let us know what you think.
This is just one build in a continuous program and some functionality
is still missing or isn't fully implemented yet. Despite these
limitations we think that what's available is interesting enough to
make it worth downloading the bits. We encourage you to install and
try this Sun Studio Express build.
This README page will give you all the information you need about
what's new in this release. In addition, you can consult the Sun
Studio forums for last minute information, and you can post feedback.
On the forums you'll be able to get answers to your questions from our
engineers as well as the community. And, we'd also like to hear from you about what what worked and what didn't, and what we should improve.
Note that the man pages and other documentation in the
downloaded bits have not all been updated yet. The Sun Studio 11 documentation
page links to all the manuals, man pages, and readmes for Sun Studio 11, which was the last official software release.
2. System and Hardware Requirements
The minimum system and hardware requirements for this Sun Studio
Express build are:
Hardware
- Mininum on SPARC: Sun Ultra 60 (450 MHz, UltraSPARC
II processor)
- Mininum on x86/x64: Pentium III 500-MHz or any
AMD64 Opteron or Athlon system.
- Memory: 512 Mbytes
- Swap: 1 Gbyte
- Disk space:
- SPARC platforms: 1.4 GBytes
- x86 platforms: 750 MBytes
- Linux platforms: 460 MBytes
Operating Systems
- Solaris versions:
- Solaris 9
- Solaris 10 01/06 or later update
- Linux versions:
- SuSE Linux Enterprise Server 9 with Service Pack 3 (or later)
- Red Hat Enterprise Linux 4
If you want to try Sun Studio Express on OpenSolaris or on any Linux
distribution which minimally has the 2.6.X Linux kernel and 2.3.3+ glibc, we would very much like to receive your input.
3. Installing This Sun Studio Express Build
3.1 You can install the Sun Studio Express Feb 2007 release in one of two ways:
- Option 1: Install Using the Package Installer
This option provides the Sun Studio software as Solaris or Linux
packages, and the prerequisite software. It lets you check your system
for the prerequisite software, install any missing software, and then
install the Sun Studio software.
The Sun Studio team would greatly appreciate any feedback you can provide us on the package installer prior to the upcoming release of the product.
-
Option 2: Install the Product Tarfile
This option extracts the installed version of Sun Studio software from a tar file, without using Solaris or Linux packages. You can use this option when you do not have root access to your system, or when you need a backup alternative to the Package Installer.
It also provides the System Preparation tool, which lets you check
your system for the prerequisite software, and if you have root access,
install any missing software.
3.2 Downloading:
- Participants in the Early Access program access this Sun Studio Express release download by going to the
Build Info page
- Participants in the Sun Studio Express program access this Sun Studio Express release download by going to the Sun Studio Express page.
Both the Early Access program and the Sun Studio Express program use identical downloads.
3.3 Option 1: Download and Install Using the Package Installer
The Sun Studio 12 Quick Installation guide is a short document that provides the minimum information you need to prepare your system and install
Sun Studio software. We recommend you read this document prior to installation.
To install the Sun Studio software and prerequisite software on a single
user system using the graphical user interface installer:
- If you are not currently superuser (root), become superuser by typing:
$ su
Password: root-password
- In the download directory, start the installer by typing:
./installer
- Proceed through the remaining pages to complete the installation.
The Quick Install guide includes information on:
- installing the Sun Studio software on a server for use by client systems
- installing the Sun Studio software on a Solaris 10 system with zones
- running the installer on a remote system and displaying it locally
- using the command-line installer
- using the batch installer
- starting the Sun Studio IDE
- uninstalling the Sun Studio software
3.4 Option 2: Download and Install the Product Tarfile
Download both the product tarfile and System Preparation tool tarfile into a scratch directory, such as /var/tmp.
- Install Sun Studio Express by unpacking the product tarfile into the directory of your choice with the command:
$ bzcat DOWNLOAD-DIRECTORY/StudioExpress-OS-PLATFORM-DATE-ii.tar.bz2 | /bin/tar -xf -
WARNING: Do not install any Express builds over an installation of a production Sun Studio release or previous Express build. Typically, production installations of Sun Studio releases are installed in /opt/SUNWspro/ on Solaris OS, and /opt/sun/sunstudionn on Linux, where nn is the release number (for example
/opt/sun/sunstudio12). Be sure to install Express builds in an area separate from these installations.
- The System Preparation tool lets you check your system for the
prerequisite software, and if you have root access, install any missing
software.
Unpack the System Prepation file in a directory of your choice with the command:
$ bzcat DOWNLOAD-DIRECTORY/StudioExpressSysPrep-OS-PLATFORM-DATE-tar.bz2 | /bin/tar -xf -
Check whether your system contains the required software and patches by typing:
./prepare_system -C
The tool lists any software that is missing. To install the missing
software:
1. If you are not currently superuser (root), become superuser by typing:
$ su
Password: root-password
2. Install any missing software or patches with the command:
$ ./prepare_system -s missing_software_name missing_software_name
3.5: Update your paths
Now update your PATH and MANPATH shell variables to the installation and documentation directories or modify your home directory's .cshrc file (for C shell) or .profile file (for Bourne or Korn shells) to make these changes permanent.
If you use csh:
% setenv PATH installpath/bin:$PATH
% setenv MANPATH installpath/man:$MANPATH
If you use sh (or ksh):
% PATH=installpath/bin:$PATH; export PATH
% MANPATH=installpath/man:$MANPATH; export MANPATH
4. 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. In this
Sun Studio Express build, only usage information is communicated.
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.
To disable Update Notification, set the SUNW_NO_UPDATE_NOTIFY
environment variable to any value other than false.
5. New and Changed Features
Here is an overview of some of the new features in this Express
build of Sun Studio compilers and tools. Note that most of these
features may not yet be documented in the Sun Studio man pages in
this build.
New Integrated Development Environment (IDE)
The new Sun Studio IDE is based on NetBeans 5.5.1 and
adds many new features. It supports C and C++ projects, and includes
appropriate project templates for applications, dynamic and static
libraries, and projects with existing code. The IDE includes a C and
C++ class browser. The powerful language-aware built-in editor
supports code completion.
For details, see the IDE
README
C, C++, Fortran Compilers
For details on the new and changed features of the Sun Studio
compiler in this release, see the COMPILERS
README
dbx Debugger
Compilers now generate DWARF by default
The Sun compilers (C/C++/Fortran 95) all generate DWARF 2 symbolic information on all platforms. The old stabs format is still available on Solaris systems if you use the compiler option
-xdebugformat=stabs . stabs format is not supported on Linux systems.
The size of the executable file generated with DWARF will be larger than a comparable executable built using stabs. This is because most stabs data appear only in the *.o and *.a files, while all DWARF information always appears in the executable. The compiler option -xs copies all stabs data to the executable; it has no effect when the compiler is generating DWARF. Also, with DWARF, only the executable file is needed for debugging. Using stabs requires that the *.o and *.a files must available for debugging. Finally, the larger size of the executable has no effect on its runtime performance.
dmake - Distributed Make
dmake is integrated with the IDE. By default all projects are built with dmake,
which runs in parallel mode. Project properties let users specify the maximum
number of build jobs. By default dmake runs 2 jobs in parallel, which
means many projects will build twice as fast on multi-CPU systems.
Sun Performance Library
The Sun Performance Library is stable on x64
Linux, but some problems have been reported on x86 Linux.
In this build, there are major improvements in
the performance of the Fast Fourier Transform software for the one-
and two-dimensional cases on x86-64 and SPARC, and in the
three-dimensional case for SPARC.
Improved the performance of the Transpose
routines : CTRANS, DTRANS, STRANS, ZTRANS.
Improved the performance and scalability of the
Cholesky factorization routines: CPOTRF, DPOTRF, SPOTRF, ZPOTRF.
Lock_Lint Tool
lock_lint
is now available on Solaris x86/64. There is also a technical
article about how to use lock_lint.
The Thread Analyzer, THA
The Thread Analyzer is available on Linux
and Solaris SPARC/x86/x64 platforms.
»Preliminary Thread Analyzer documentation.
Performance Analyzer Tools
For details on the new and enhanced features of the Sun
Studio Analyzer and associated performance tools, see the ANALYZER
README.
6. Additional Notes
Using the -xipo command line flag
You must specifiy -xipo both at
compile time and link time. Failure to specify -xipo
at link time on Linux could result in significantly large executable
files.
Source Code for libelf and ld
Source code for libelf version 0.8.6 can
be found at the following
URL:
http://directory.fsf.org/libs/misc/libelf.html
Source
code for ld version 2.16.1 (part of binutils)
can be found at the following URL:
http://ftp.gnu.org/gnu/binutils/
Third-Party Technology Licenses
Sun Studio software includes third-party technologies
governed by a third
party license readme file. Similarly, NetBeans includes
third-party technologies governed by a NetBeans
third-party license readme file. NetBeans C/C++ Development Pack is governed by
its own NetBeans
C/C++ Development Pack third-party license readme file.
7. Usage Tracking Enabled for Early Access
|
|
Usage tracking provides a way for Sun software engineers to
collect information about how developers use Sun compilers and tools.
This information can then be used to improve future revisions of the
products.
Usage tracking is enabled in this Early Access release. Usage
tracking will not be enabled in the final release.
Usage tracking captures the compiler and tools command options
that you specify. Usage tracking also uses the uname -a
command to capture platform information and operating system
information from the runtime environment. No file names, directory
names, or macros are collected. For example, you might issue the
following command:
CC -DMACRO -L/directory1 -I/directory2 -Xa -O hello.cc
In this case, only the following information is reported back to
Sun:
CC -D -L -I -Xa -O
Each time a compiler or tool is invoked, the options that are used
are logged in the file /tmp/.UT... The log file is sent
to Sun software engineers if the file exceeds 10 Kbytes or is more than
24 hours old.
You can turn off usage tracking by defining the environment
variable UT_NO_USAGE_TRACKING before running any of the
Sun compilers and tools.
(with csh) % setenv UT_NO_USAGE_TRACKING
(with ksh) $ export UT_NO_USAGE_TRACKING
(with sh) $ set UT_NO_USAGE_TRACKING; export
UT_NO_USAGE_TRACKING
(Last updated March 14, 2007)
Print-friendly Version
