Running the xlc_install utility for a new installation

The xlc_install utility is located in the root directory of the installation image.

Note:
Because the xlc_install utility is written in Perl, you must ensure that Perl is installed on your system before you run the utility. See Verifying that the required GNU, Perl, and Java packages are installed.

When you run the xlc_install utility for a new installation, it does the following:

To run the xlc_install utility to install IBM XL C/C++ Advanced Edition V8.0 for Blue Gene:

  1. Assuming that the IBM XL C/C++ Advanced Edition V8.0 for Blue Gene CD is mounted at the /cdrom location in the system, issue the following commands:
      # cd /cdrom
      # ./xlc_install 
    For additional arguments that you can specify for xlc_install, see xlc_install options.

    If another instance of XL C/C++ for Blue Gene is detected on your system, you are prompted to uninstall it.

  2. Confirm that you want to proceed with the uninstallation. If you choose not to uninstall the existing instance of the compiler, the installation process will terminate.

    If other versions of the XL SMP and MASS packages are detected on your system, either alone or as part of an XL Fortran Advanced Edition V10.1 for Blue Gene installation, you are prompted to uninstall them.

  3. Confirm that you want to proceed with uninstalling the existing SMP and MASS packages. If you choose not to uninstall the previously installed components, the installation process will terminate.
    Note:
    xlc_install will uninstall these packages from their existing location and reinstall them to the default location, /opt/ibmcmp/. Therefore, if they were previously installed in a non-default location as part of an XL Fortran for Blue Gene installation, you will need to run xlf_configure to re-configure the XL Fortran compiler to point to the default location for these packages. For procedures, see "Running the xlf_configure utility directly" in the XL Fortran Advanced Edition V10.1 for Blue Gene Installation Guide.

    You are presented with the licensing agreement and licensing information.

  4. Accept the licensing agreement and licensing information.

    You are prompted to create symbolic links for the compiler invocations in the /usr/bin/ directory.

  5. Optionally, create the symbolic links.
    Note:
    An alternative to this step is to add the path that contains the compiler invocations to the PATH environment variable. See Setting the PATH environment variable to include the path to the XL C/C++ for Blue Gene invocations.

    If you chose to create symbolic links, the following links are created in the /usr/bin/ subdirectory:

    Note:
    Some command links are not created in /usr/bin/, either because they might delete user-defined, XL C/C++ for Linux or GCC-related invocations, or because they are not compiler invocation commands. These include:
    • c89, c89_r, c99, c99_r, cc, and cc_r
    • gxlc, gxlc++, gxlC, xlc, xlc++, xlC, xlc_r, xlc++_r, xlC_r
    • cleanpdf, mergepdf, new_install, resetpdf, showpdf, vac_configure

If all packages are successfully installed:

xlc_install options

The xlc_install utility provides the following options:

-h
Displays the installation utility help page.
-rpmloc rpmlocation_path
Explicitly specifies the path where all compiler packages are located. The default rpmlocation_path is ./platform/rpms, which is relative to the path of the installation tool. Therefore, the default rpmlocation_path is ./SLES9-BGL/rpms.
Note:
Normally, the -rpmloc rpmlocation_path option is not required in the installation invocation. If you use the utility directly from the CD, it will automatically determine the source location of the packages.
-U
Updates the compiler to the Version.Release.Modification-Fix level that the installation utility version supports. For more information, see Running the xlc_install utility to update a basic installation.
-v
Displays debugging information.
-vv
Displays more detailed debugging information.