Free membership is required to download software from DSPP |
 |
|
|
- Existing members: If you are an existing member, please sign in. If after you sign-in you still cannot access software downloads and you see a "Join DSPP" link on the right side of the DSPP home page, you are an HP Passport member but not yet a DSPP member. Click on the "Join DSPP" link and complete your DSPP registration.
- Non-members: To become a DSPP member, please register.
- For additional details, visit troubleshooting tips or learn more about DSPP membership.
|
|
|
|
The GCC packages for HP-UX are available for HP-UX 11.11 or later running on HP PA-RISC and for HP-UX 11.23 or later running on the Itanium?-based processor family platform. Note: There is no official support for GCC from HP. However,
for GCC-related questions and issues, please email:
gcc-help@cup.hp.com. IMPORTANT: The GCC packages for HP-UX have undergone a significant makeover. In order to clearly separate the old and new packages, we have prefixed the new packages with 'hp-' so that the package name starts with "hp-gcc" as opposed to just "gcc". We continue to refer to the package as GCC (without the prefix). Below a list of changes with an explanation of how it may affect you: - The new GCC packages are not installed under /usr/local. Both the HP-UX and Linux file system hierarchies have designated /opt as the location for packages and have designated /usr/local for use by the site's local use. By changing the installation location, we conform to adopted standards.
The consequence of this change is that installing the new GCC package will not overwrite the old GCC package. Please remove the old GCC package and corresponding binutils package manually.
Especially important to note is that when the old package is not removed, it may inadvertently be used. We do not require that the old package be removed, but make sure that the correct one is being used.
- The GNU binutils package is not provided as a separate package anymore. Instead, it has been bundled in the GCC package. The reason for this change is that it allows us to bundle a version of binutils that we know works with that version of GCC, even if that means using unreleased sources. It greatly increases the overall stability and quality that we can guarantee. This consequently makes it possible to install different versions of GCC on a system without the versions affecting each other.
- There are two separate GCC packages for PA-RISC, one that generates ILP32 code, and another that generates LP64 code. The 32-bit version is installed in the /opt/hp-gcc directory, and the 64-bit version is installed in /opt/hp-gcc64.
- It is now possible to install multiple versions of the GCC package at the same time. As such, a new version will not overwrite an older version or make it obsolete. An upgrade now implies that a new version is installed first and an older version be removed next. The reason for this change is to provide customers with a more controlled upgrade process. A new version of GCC can be tried and tested before an older version is removed. By default the latest version is always called "gcc", but each version is also know by a name that includes the version number, allowing it to be run explicitly.
- On PA 11.11 systems, the linker patch PHSS_33033 is required to compile C++ programs.
- In case of any problems with installing and/or using these packages, please send emails to gcc-help@cup.hp.com.
Installation Instructions If you have a version of GCC already installed in /usr/local on your machine, you should use swremove to remove it before you install the new version. Note: swinstall cannot handle gzipped depot files. You must gunzip them first. - Select the appropriate download. You will then see a "Save as" dialog box appear on your screen.
- In the "Selection" field define the path where you wish to save the downloadable file and press "OK".
- Once the file has been saved onto your system, run swinstall as "root".
swinstall -s <FILE_NAME> <PRODUCT_NAME> where <FILE_NAME> is the complete path of the saved downloadable file and <PRODUCT_NAME> is the name of the product to install. NOTE: Some browsers may save the file with a different extension such as .tar. Continue with the following instructions and use the extension of the file saved. For example, if the downloadable file was saved in "/tmp" and the product name is "foo" the command to install would be: swinstall -s /tmp/foo-1.2-11.00.depot foo or swinstall -s /tmp/foo-1.2-11.00.tar foo NOTE: Refer to the man page swinstall(1M) for more information. - If the install does not complete correctly or you have problems you can access the log file at:
/var/adm/sw/swagent.log
|
