The PathScale compilers require the 32-bit version of this library. Make sure this is in your library search path. This is covered in the PathScale Compiler Suite and Subscription Manager Install Guide, Section "Using Shared Libraries".

If you are installing a non-root tar file, you must configure the dynamic linker by hand. There are two ways to do this, depending on whether or not you have root privileges.

If you do not have root privileges, (using a bash shell) type the following:

$ export LD_LIBRARY_PATH=<install_directory>/lib/<version>: <install_directory>/lib/<version>/32:$LD_LIBRARY_PATH

If you have root privileges, point to shared files after a non-root tar file installation by adding the following lines to /etc/ld.so.conf (the order in which they appear does not matter):

/<install_directory>/lib/<release> /<install_directory>/lib/<release>/32

After adding these lines, run the /sbin/ldconfig program to tell the dynamic linker about these new directories. You will need root privileges to do this.

# /sbin/ldconfig

• You do not have the 32-bit runtime environment installed.
  Our compiler is a 32-bit application. Some Linux distributions do not install the 32-bit glibc and libstdc++ runtime libraries by default. In those cases you will need to manually install them.
• You do not have the right versions of these libraries installed
  The PathsScale Compiler Suite is based on GCC 3.3 and the associated runtime libraries. Some of the newer Linux distributions provide the GCC 3.4 or 4.0 runtime libraries by default. These systems will need compatibility libraries installed. The compatibility libraries provide the necessary versions of the libraries for the GCC 3.3 compilers.

We do support the installation of individual language compilers.

Note: Installing the individual compilers only works with the RPM install.

The PathScale Compiler Suite has a number of supporting RPMs that must be installed for the compilers. This list includes the RPMs named:

You must install all of these RPMs, but you are free to select whichever language-specific RPM you need:

After you have installed the other RPMs, then install the appropriate package for the language you want. For example, to install the Fortran compiler you would type:

  # rpm -Uvh pathscale-f90-*

See Chapter 4 in the PathScale Compiler Suite and Subscription Manager Install Guide for more details on installing subsets of the PathScale Compiler Suite environment.

Yes, customers have tried to install the PathScale Compiler Suite on untested Linux distributions. The following is a list of the operating systems they have tried, the problems that they encountered, and any workarounds that they have reported to us.

Please remember that these are not supported distributions. Any problems encountered will only be corrected if they can be duplicated on a supported distribution.

Note: When using an unsupported distribution, be sure that gcc-3.3 is installed; gcc-3.3 must be installed for pathCC to work.

The subscription manager tracks the usage based on user name and machine name. In the current implementation this means that within the lease period if either the number of users exceeds the number of seats *or* the number of machines exceeds the number of seats, then the subscription manager will turn down the request.

The subscription daemon uses the following formula to determine if there are leases available:

     numseats = max(users, machines)

For example, if a site has 10 users and 20 machines, and the subscription specifies that the number of leases is 10, then up to 10 users can use the software on up to 10 machines (that is, up to 100 leases can be issued using combinations of the 10 users and machines).

Please see the PathScale Compiler Suite and Subscription Manager Install Guide for more information.

I installed the new subscription file in the /opt/pathscale/lib/ directory but the compiler still does not work. What's happening?

$ pathcc -O3 hello.c -o hello
*** Subscription: Your subscription for the PathScale 
compiler products has expired and you have exceeded 
the grace period. Your compiler will not operate
until you contact PathScale and formally renew the 
agreement. 
Compilation terminated

When installing a new subscription file, it is necessary to restart the subscription server. See the PathScale Compiler Suite and Subscription Manager Install Guide.

Double check the permissions on the subscription file. Make sure it is world readable:

  # cp pscsubscription-<product>-*.xml  \
      /opt/pathscale/lib/3.0
  # chmod ugo+r /opt/pathscale/lib/3.0/  \
      pscsubscription-<product>-*.xml

Additionally, you should ensure that any old subscription files are removed from the directory as they will interfere with more recent ones. Renaming is not sufficient. They must not be in the same directory.

We seem to have a problem with our PathScale compiler subscription. We get the following cryptic and unhelpful error message:

*** Subscription: You have exceeded the limits for which 
    you contracted in your PathScale subscription agreement 
    and have gone beyond any additional allowances provided 
    for unintentional or occasional use. Your usage will 
    be limited to the contracted levels until you contact 
    PathScale to increase your committed usage levels.
    Compilation terminated