1. Introduction

Welcome to Release 2017 of PGI compilers and development tools for 64-bit x86-compatible processor-based workstations, servers, and clusters running versions of the Linux, Apple macOS, and Microsoft Windows operating systems.

This installation information applies to all PGI products.

1.1. Node-locked and Network Floating License Comparison

  • With a PGI node-locked single-user license, one user at a time can compile on the one system on which the PGI compilers and tools are installed. The product and license server are on the same local machine.
  • PGI network floating products are offered in configurations identical to PGI node-locked products, but include network-floating licenses. This means that one or more users can use the PGI compilers and tools concurrently on any compatible system networked to the license server, that is, the system on which the PGI network floating license keys are installed. There can be multiple installations of the PGI compilers and tools on machines connected to the license server; and the users can use the product concurrently, provided they are issued a license seat by the license server.

1.2. Release Components

Release 2017 includes the following components:

  • PGFORTRAN™ native OpenMP and OpenACC Fortran 2003 compiler.
  • PGCC® native OpenMP and OpenACC ANSI C11 and K&R C compiler.
  • PGC++® native OpenMP and OpenACC ANSI C++14 compiler.
  • PGI Profiler® OpenACC, CUDA, OpenMP, and multi-thread graphical profiler.
  • PGI Debugger® MPI, OpenMP, and multi-thread graphical debugger.
  • Open MPI version 1.10.2 for 64-bit Linux including support for NVIDIA GPUDirect. GPUDirect requires CUDA 7.5 or later. Note that 64-bit linux86-64 MPI messages are limited to < 2 GB size each. As NVIDIA GPUDirect depends on InfiniBand support, Open MPI is also configured to use InfiniBand hardware if it is available on the system. InfiniBand support requires OFED 3.18 or later.
  • MPICH libraries, version 3.2, for 64-bit macOS development environments.
  • ScaLAPACK 2.0.2 linear algebra math library for distributed-memory systems for use with Open MPI, MPICH or MVAPICH, and the PGI compilers on 64-bit Linux and macOS for Intel 64 or AMD64 CPU-based installations.
  • Microsoft HPC Pack 2012 MS-MPI Redistributable Pack (version 4.1) for 64-bit development environments (Windows only).
  • BLAS and LAPACK library based on the customized OpenBLAS project source.
  • A UNIX-like shell environment for 64-bit Windows platforms.
  • FlexNet license utilities.
  • Documentation in man page format and online PDFs.

1.2.1. Additional Components for PGI Network Floating Licenses

PGI floating licenses for Linux (formerly the PGI CDK Cluster Development Kit) include additional components available for download from the PGI website, but not contained in the installation package including:

  • MVAPICH2 MPI libraries, version 2.0.
  • MPICH MPI libraries, version 3.2.

1.2.2. MPI Support

You can use PGI products to develop and debug MPI applications. The PGI debugger is MPI-enabled. PGI node-locked licenses support MPI debugging up to 16 local processes. PGI network floating licenses support MPI debugging up to 256 remote processes.

1.3. Terms and Definitions

This document contains a number of terms and definitions with which you may or may not be familiar. If you encounter an unfamiliar term in these notes, please refer to the PGI online glossary.

These two terms are used throughout the documentation to reflect groups of processors:

Intel 64
A 64-bit Intel Architecture processor with Extended Memory 64-bit Technology extensions designed to be binary compatible with AMD64 processors. This includes Intel Pentium 4, Intel Xeon, Intel Core 2, Intel Core 2 Duo (Penryn), Intel Core (i3, i5, i7), both first generation (Nehalem) and second generation (Sandy Bridge) processors, as well as Ivy Bridge and Haswell processors.
AMD64
A 64-bit processor from AMD™ incorporating features such as additional registers and 64-bit addressing support for improved performance and greatly increased memory range. This term includes the AMD Athlon64™, AMD Opteron™, AMD Turion™, AMD Barcelona, AMD Shanghai, AMD Istanbul, AMD Bulldozer, and AMD Piledriver processors.

1.4. Supported Processors

The following table lists the processors on which Release 2017 of the PGI compilers and tools is supported. The table also includes the CPUs available and supported in multi-core versions.

The -⁠tp <target> command-line option generates executables that utilize features and optimizations specific to a given CPU and operating system environment. Compilers in a 64-bit PGI installation can produce executables targeted to any 64-bit target, including cross-targeting for AMD64 and Intel 64-bit compatible CPUs.

Note: PGI 2017 supports 64-bit operating systems only. Compiling 32-bit applications for execution on either 32-bit or 64-bit operating systems is no longer supported on any platform.

PGI products have the capability to generate binaries optimized for specific Intel or AMD processors. The PGI 2017 compilers can produce PGI Unified Binary™ object or executable files containing code streams fully optimized and supported for both Intel and AMD x64 CPUs and NVIDIA GPUs.

Tip:

To determine what CPU you have, use one of the following commands:

pgfortran -⁠V

or

pgcc -⁠V

To produce PGI Unified Binary files, use one of the following -⁠tp command-line options, where <target> is any of the valid values in the supported processors table.

-⁠tp x64

or

-⁠tp <target1>,<target2>,<target3> ...

1.4.1. Supported Processors

Table 1. Processors Supported by PGI 2017
Brand CPU Target Processor
(-tp <target> [,target...])
AMD    
Opteron Piledriver piledriver
Opteron Bulldozer bulldozer
Opteron Six-core Istanbul istanbul
Opteron Quad-core Shanghai shanghai
Opteron Quad-core Barcelona barcelona
Opteron Quad-core k8
Opteron Rev E, Turion k8-64e
Intel    
Haswell haswell
Ivy Bridge ivybridge
Sandy Bridge sandybridge
Core i7 - Nehalem nehalem
Penryn penryn
Pentium 4 p7
Generic    
Generic px

1.5. Supported Operating Systems

PGI supports Linux, macOS and Windows operating systems.

Linux

Most Linux operating systems with GLIBC 2.5 and above:

  • CentOS 5+, including CentOS 7
  • Fedora 6+, including Fedora 25
  • OpenSUSE 11+, including OpenSUSE Leap 42.2
  • RHEL 5.11, RHEL 6.0 through 6.9, and RHEL 7.0 through 7.3
  • SLES 11+, including SLES 12 SP 2
  • Ubuntu 12.04+, including Ubuntu 17.04

Version differences in some operating system components may cause difficulties, but often these can be overcome with minor adjustments to the PGI software installation or operating system environment.

Apple macOS (formerly OS X)

The compilers, debugger, and profiler are supported on macOS versions 10.9 (Mavericks) through 10.12 (Sierra).

Windows

  • Windows Server 2008 R2
  • Windows 7
  • Windows 8
  • Windows 8.1
  • Windows 10
  • Windows Server 2012
  • Windows Server 2016
Note: The PGI compatibility page lists any new operating system distributions that may be explicitly supported by the PGI compilers. If your operating system is newer than any of the operating systems in the preceding list, the installation may still be successful.

1.6. Hyperthreading and Numa

Most modern operating systems include support for Intel Hyper-threading (HT). Further, most modern Linux distributions support the Native Posix Threads Library (NPTL). Parallel executables generated using the OpenMP and auto-parallelization features of the PGI compilers will automatically make use of NPTL on distributions where it is available. In addition, the PGI debugger is capable of debugging executables built using either NPTL or earlier pthread implementations.

Many modern multi-socket AMD Opteron processor-based servers use a NUMA (Non-Uniform Memory Access) architecture in which the memory latency from a given processor to a given portion of memory can vary. Newer Linux distributions, including SuSE 11/13 and SLES 10/11, include NUMA libraries that can be leveraged by a compiler and associated runtime libraries to optimize placement of data in memory.

1.7. Java Runtime Environment (JRE)

The PGI debugger and profiler use Java. To use these tools, a version of the Java Runtime Environment (JRE) must be installed.

The tools are compatible with Java 1.6 and later versions. The PGI 17.9 release includes the JRE version 1.8 update 112. On Linux and macOS, this version of the JRE is installed in the same location as the compilers and does not affect the default Java. On Windows, the JRE is installed to Java’s default install location.

One can opt out of the JRE installation on both Linux and Windows. Without Java, the debugger and profiler are only available in command-line mode.

1.8. Product Support

All new PGI licenses include free PGI Support Service during the money-back guarantee period.

The PGI Support Service provides access to techincal support and other benefits including:

  • Technical support requests may be sent in a number of ways:

    Phone support is not currently available.

  • Release upgrades for licensed product(s) at no additional cost, except for any administrative fee that may apply.
  • Notification by email when maintenance releases occur and are available for download and installation.
  • Full license fee credits on Product upgrades, except for any administrative fee that may apply. "Product upgrades" refer to exchanging one Product license for a more expensive Product license, and is not the same as a Version or Release upgrade previously referenced.
  • Full license fee credits on user-count upgrades, except for any administrative fee that may apply.
Important: To continue receiving these benefits after the money-back guarantee period days, you can purchase an extension to your PGI Support Service. Extensions are available in yearly increments.

Contact sales@pgroup.com if you would like information regarding the support service for the PGI products you have purchased.

2. Installation Overview

This chapter provides an overview of the steps required to successfully install PGI compilers and tools. The remaining chapters provide the details of each of the steps. Specifically, the Licensing section describes licensing. PGI Installations on Linux describes how to install PGI in a generic manner on Linux, including how to install and run a FlexNet license daemon on Linux. Installations on Microsoft Windows describes how to install on a Windows system, and Installations on macOS describes how to install on an Apple macOS system.

2.1. Before You Begin

Before you begin the installation, it is advantageous to understand the flow of the installation process. There are three stages of the process:

  • Prepare to install—verifying that you have all the required information, that the correct PGI software is downloaded, and any other non-PGI software that is needed is available and/or installed.
  • Install the software—installing the software appropriate for your operating system.
  • License the software—generating of license keys using the PGI website, installation of the license keys, and starting the license server.

The following illustration provides a high-level overview of the PGI installation process.

Figure 1. PGI Installation Overview
PGI Installation Overview.

For more complete information on these steps and the specific actions to take for your operating system, refer to the remainder of this document.

2.2. PGI Network Installations

Linux

On Linux, a PGI network floating license may be installed locally on each machine on a network or it may be installed once on a shared file system available to each machine. If you select the second method, then after the first installation you can run a simple script on each machine in the group to add each new platform to the family of machines using the common compiler installation.

For more information on network installations, refer to PGI Installations on Linux.

Apple macOS and Windows

On Apple macOS and Windows, PGI software must be installed locally on each machine. A network installation using a shared file system is not supported.

2.3. PGI Installations Preparation

PGI compilers need various components installed prior to installing the PGI products. The operating system determines which components must be present before installation.

2.3.1. Linux Installations

  • Linux Standard Base, lsb, must be present for the license utilities to work properly. Enter the command lsb_release to see if you have lsb, and, if so, which version. PGI installations require version 3.0 or newer. To install lsb, try running one of the following commands:
    • On Debian/Ubuntu: [sudo] apt-get install lsb
    • On RedHat/Fedora/CentOS: [sudo] yum install redhat-lsb
    • On SLES/OpenSUSE: [sudo] yast --install lsb
  • After lsb has been installed, verify you have a version of gcc installed in your $PATH.
    Note: Any changes to your gcc compilers requires you to reinstall your PGI compilers.

    To determine if gcc compilers are installed on your system, do the following:

    1. Create a hello.c program.
      #include <stdio.h>
      int main()
      {
      printf(" hello\n");
      } 
    2. Execute these commands to determine if you have gcc support in your path.
      % gcc -m64 -o ./hello_64 ./hello.c ! create a 64-bit executable
      % file ./hello_64 ! does the file exist, and is it 64-bit?

      Output should look similar to the following:

      hello_64: ELF 64-bit LSB executable, AMD x86-64, version 1 (SYSV), for
      GNU/Linux 2.6.9, dynamically linked (uses shared libs), for GNU/Linux
      2.6.9, not stripped

2.3.2. Windows

The Microsoft Windows Software Development Kit (SDK) is a prerequisite for all Windows installs. You can find links to download the Windows SDK on the PGI Microsoft SDK webpage.

The PGI Community Edition on Windows requires that Microsoft Visual Studio 2015 with Visual C++ be installed first. For configuration information, see the PGI Community Edition webpage.

The PGI compilers for Windows rely on the Microsoft tool chain. To use these tools on operating systems older than Windows 10, first download and install Microsoft’s Update for Universal C Runtime. Depending on the configuration details of your system, this update may have already been installed as part of the automatic Windows Updates applied to your system.

2.3.3. Apple macOS

Apple macOS installations require these components:

  • An installation of Xcode must be present, including the Xcode Command Line Tools. You must also first assent to any Xcode license agreements before using your PGI product.
  • Enable remote login in the Sharing System Preference to enable the license server to operate.

2.4. Cluster Installation Overview

The following sections contain the information needed for you to successfully prepare to install the PGI software for operation in a cluster environment.

Recall that a cluster is a collection of compatible computers connected by a network. The PGI software can be installed on a single node, and the node can be treated as if it is a cluster.

Support for cluster programming is limited to clusters combining Intel 64 or AMD64 CPU-based systems.

For multi-process programming of message-passing applications that execute on a cluster, PGI includes a 64-bit set of Open MPI libraries. These libraries implement the MPI inter-process communication standard.

Additional MPI libraries are available from the PGI website at https://www.pgroup.com/support/downloads.php.

2.4.1. Cluster Configurations

Clusters are typically configured with two types of nodes:

  • One "master" node from which jobs are launched
  • One or more "slave" nodes that are used only for computation

PGI compilers and tools should be installed on the master node, and installed to run from the master node only.

Typically, the master node is accessible from the general-purpose or "public" network and shares a file system with the other computers on your network using NFS. The master node and all of the slave nodes are interconnected using a second "private" network that is only accessible from computers that are part of the cluster.

There are two common cluster configurations:

  1. The master node is used only for compilation and job submission, and only the slave nodes are used for computation.
  2. All nodes are used for computation, including the master node.

One way to use MPICH in the first configuration is to manage job scheduling. By default, the mpirun command uses the master node as one of the computation nodes. It is possible to exclude the master node as a computation node in the second configuration if mpirun is invoked with the -⁠nolocal option. For more information, refer to the man page for mpirun.

Typically, a master node has two network cards to allow communication to the outside network as well as to the cluster nodes themselves, which may be on their own subnet. The installation script will prompt you for the name of the master node. If your cluster has two network cards, then you should enter the name of the network card that is connected to the same network as the cluster nodes.

For MPICH to run correctly, access from each node to every other node must be available via the rsh or ssh command. For example, if a three-node cluster consists of a master, named master, and two slaves named node1 and node2, then from node1 as a user you should be able to issue the commands:

% rsh master date
% rsh node2 date 

or

% ssh master date
% ssh node2 date 

You can issue similar commands from node2 using master and node1.

By default, all of the PGI compilers and tools will be installed on your system. You will select which of the open-source components to install.

At this point, before you start the installation, you must determine:

  • Which open-source components—MPICH, MVAPICH2 and/or Open MPI—are best suited for cluster. All three are available.
  • The hostnames of all the nodes that will be included in your cluster. You need a list of these during the installation.
  • The type of cluster configuration—that is, whether the master node will participate as a compute node or will be strictly a front-end for compilation, job launching, and so on.
  • Whether the compute nodes can share files with the master node, which is strongly recommended.
  • The location of a commonly mounted disk that all nodes can access via the same pathname. This disk is very helpful for installing runtime libraries and storing executables created.

PGI Installations on Linux describes how to install the PGI Fortran, C and C++ compilers and tools on Linux using the install_cdk script from PGI.

The PGI compilers and tools are license-managed, which is described in Licensing. Further, Installation Steps for Linux provides specific information about how to use your personalized account to generate permanent license keys.

2.4.2. Open Source Component Overview

The PGI Compiler User's Guide describes basic usage of the PGI open-source components, including the MPICH and ScaLAPACK libraries, and the example benchmark programs and tutorials.

MPICH, MVAPICH, Open MPI, and ScaLAPACK are all open-source software packages that are not formally supported by PGI. Support for these products is generally provided by their respective user communities, which you can learn more about at the following URLs:

2.5. Further Considerations

There are a number of additional things you might consider prior to installation.

  • A PGI Account
    PGI recommends that everyone installing or using the compilers create an account on the PGI website. An account is required to manage your license, download PGI software, post on the PGI userforum, submit technical support requests, view some web content and other activities.

    Once you have a web account, your account should be tied to any PIN that you will use to license the compilers. A PIN is connected to permanent license, as described in Licensing.

  • Downloading the proper package
    When ready, you can download the proper package(s) at https://www.pgroup.com/support/downloads.php. The file sizes can be large. To help avoid problems, a checksum is displayed for all downloaded files. After downloading file.tar.gz, use the command md5sum file.tar.gz to display the checksum value. The two values should match.

  • Permissions
    You will need root, sudo, or Administrator access to install the compilers and/or to set up the license service for auto restart. File ownership or permission issues are a common source of unexpected behavior.

  • Firewall Issues
    Systems with firewalls may encounter two problems. First, the hostname used in the license file may not be mapped properly to the IP address of your machine. Second, the license server (lmgrd) and license daemon (pgroupd) each need an assigned port to allow them access through the firewall. For lmgrd, the default port is 27000. For pgroupd, there is no default port assigned. With a firewall, you may need to change and/or specifically assign another port number.

  • Laptop Installations
    For laptop installations, consider using localhost as the hostname, mapped to the loopback interface 127.0.0.1. Test this by pinging localhost. Also consider looking for hostids (lmutil lmhostid) in all three laptop environments (network, wi-fi, on none), and look for hostids persistent in all three environments.

3. Licensing

The PGI compilers and tools are license-managed. PGI software licensing uses the FlexNet Publisher (FNP) license management system from Flexera Software.

PGI software licensing uses the FlexNet Publisher (FNP) license management system from Flexera Software.

3.1. Licensing Terminology

Before discussing licensing, it is useful to have common terminology.

License
A legal agreement between NVIDIA and PGI end-users, to which users assent upon installation of any PGI product. The terms of the License are kept up-to-date in documents on pgroup.com and in the $PGI/<platform>/<rel_number> directory of every PGI software installation.
License keys
ASCII text strings that enable use of the PGI software and are intended to enforce the terms of the License. License keys are typically stored in a file called license.dat that is accessible to the systems for which the PGI software is licensed.
PIN
Product Identification Number, a unique 6-digit number associated with a purchased license. This PIN is included in your PGI order confirmation. The PIN can also be found in your PGI license file after VENDOR_STRING=.
License PIN code
A unique 16-digit number associated with each PIN that enables users to "tie" that PIN to their pgroup.com user account. This code is provided by PIN owners to others whom they wish tied to their PIN(s).

3.2. Licensing Keys

3.2.1. Licensing Key Options

PGI products on x86-64 use Flexera’s FlexNet license management software, and may require FlexNet license daemons running on your local system or a separate license server.

There are four types of license key options: starter, developer, community, and permanent.

Starter License Keys
Time-limited evaluation license keys provided on request by PGI. Starter license keys do not use FlexNet daemons.
Developer License Keys
A PGI developer license key is valid for one year from the date of issue.
Community License Keys
A PGI Community license key is included with PGI Community Edition releases, is valid only for that release and for one year from the date of release. Community license keys do not use FlexNet daemons.
Permanent License Keys
Purchased PGI licenses come with permanent license keys. Permanent license keys are perpetual, meaning they remain valid indefinitely with eligible versions of PGI software. Permanent license keys require FlexNet license daemons either locally or on a separate license server system.

3.2.2. Licensing Key Capabilities

At the conclusion of the starter license key evaluation interval, the PGI compilers and tools, along with any executable files generated with them will cease to function. To retain functionality, any executables, object files, or libraries created using the PGI compilers with starter license keys must be recompiled with either a developer, community or permanent license key.

Executable files generated using developer license keys are restricted to running only on the same system as they were compiled. Developer license keys may not be moved between machines.

Executable files generated using community or permanent license keys are unconstrained, and run on any compatible system regardless of whether the PGI compilers are installed.

3.2.3. Licensing Key Comparisons

Table 2. License Key Comparisons
License Key Type Starter Developer Community Permanent
Limited duration Yes - 30 days Yes - 1 year Yes - 1 year No
Limited functionality Yes Yes No No

3.2.4. Licensing Key Dependencies

When using permanent license keys, you must install the PGI software before obtaining your license keys. The license key generation process requires information generated during software installation. Starter and community license keys do not have this dependency.

Important: If you change the configuration of your system by adding or removing hardware, permanent license keys may become invalid. You will need to obtain new license keys from www.pgroup.com or using the license setup tool described below.

3.3. PGI License Setup Tool

PGI 2017 for Linux x86-64 and Windows includes the PGI License Setup Tool to help automate your permanent license key retrieval and installation process. For Linux, this tool is normally installed at $PGI/<platform>/<rel_number>/bin/pgi_license_tool.

For more information on using the PGI License Setup Tool on Windows, refer to Installation Steps for Windows.

3.4. Bundled License Key

Installation may place a temporary license key in a file named license.dat in the PGI installation directory if no such file already exists.

If you use a separate license server, for example LM_LICENSE_FILE=port@server.domain.com, that supports this version, it is recommended that you remove or rename the license key file in the installation directory.

3.5. PGI Product Licensing

Node-locked

PGI node-locked licenses are locked to a single system in a way that allows any user of the system to use the PGI compilers and tools. However, only a single user is allowed to run any of the PGI compilers or tools at a given time.

Network Floating

PGI multi-user network floating licenses allow multiple users to use the PGI compilers and tools simultaneously from multiple systems on a network. The number of seats purchased for the license determines the limitation on the number of concurrent users.

The license server for network floating licenses can run on either Linux or Windows.

3.6. PGI Licensing Considerations

PGI licensing is the common method used by all PGI products to control access. The License Service is made up of two components:

  • The lmgrd daemon is the common license manager component used by all FlexNet licenses. It oversees the distribution of license seats.
  • The pgroupd daemon is unique to PGI and reads and decodes the PGI license file.

A license is created using the hostname and the hostid of the license server. These rules apply:

  • Only one copy of lmgrd runs on the license server, and is used by all FlexNet-type licenses. For both floating or node-locked licenses, only a single license server is required.
  • Only one PGI license per license server. You may have FlexNet licenses for other non-PGI software packages, but you may only have one PGI license per server. More than one causes the license server to malfunction.
  • The hostname used in the license file should be understood by all of the systems using the compilers. Entering the command ping hostname should result in the same IP address on all of the systems, including the license server itself.
  • The hostid is usually the MAC (inet address) of a device (/sbin/ifconfig on Linux and macOS, ipconfig /all on Windows), which can be detected by the FlexNet utilities. It is usually best to choose the MAC associated with the IP address of the server.
  • PGI node-locked licenses are limited to allow the compilers to work only on the machine running the license service.
  • PGI network floating licenses allow any machine that can communicate with the license server in a timely manner (i.e. distance relative) to run the compilers.
  • On clusters, the PGI installer does not install compilers on the ‘slave’ nodes. The ‘master’ node usually is on both the private and public networks, so the master node is the only node that needs access to the license service. The master node may even be the license server. Multiple clusters can share a single PGI floating license by having all of the master nodes communicate with the license service. A PGI network floating license allows the PGI debugger and the PGI profiler to run distributed across all of the cluster nodes.
  • There is a sequence in which the PGI compilers look for environment variables.
    • The PGI compilers look first at the environment variable $PGROUPD_LICENSE_FILE for the location of the PGI license. This variable is set in the registry on Windows machines, and is specific to PGI products.
    • The PGI compilers next look at the environment variable $LM_LICENSE_FILE for the location of the PGI license. This is a generic variable used by every FlexNet licensed product.
    • The PGI compilers then look at the default location for $PGI/license.dat.
  • On the license server itself, $PGROUPD_LICENSE_FILE and/or $LM_LICENSE_FILE must be the full license pathname, as in /opt/pgi/license.dat on Linux and macOS, or C:\Program Files\PGI\license.dat on Windows.
  • On machines other than the license server, $PGROUPD_LICENSE_FILE and/or $LM_LICENSE_FILE can either be a full pathname to the license file, or port@host such as 27000@hostname.
  • When changing a license file, take care to ensure the license software can read the new license. On Windows and macOS, this means having Admin privileges or sudo capability to copy the license file to its destination. If the license service is already running, you may need to STOP and START it again to make sure the new file is read and not the old file that is stored in cache.
  • When the FlexNet license service detects a problem or an event, it records it in either the flexlm.log file (Linux) or the License.log file (Windows, macOS). If you're having licensing problems, check this file for information.

3.7. The FlexNet License Manager

PGI is licensed using the FlexNet software license management system from Flexera Software.

As part of the installation process, you install and configure the FlexNet license management software. There are two permanent licensing options using FlexNet-style licensing.

  • Node-locked allows any user on a single system to run the software, with access restricted to that prespecified machine.
  • Network floating license supports a more flexible licensing system.
    • There is one license server on a network and any system on that network with a properly configured version of PGI Software installed can run the software.
    • Multiple users can use PGI Software simultaneously from multiple systems on the network.
    • The limitation on the number of users is determined by the number of seats that were purchased with the license.

The instructions in the following sections of this guide describe how to configure license daemons for Linux, Windows, or macOS, including installation and start-up of the license services, and proper initialization of the LM_LICENSE_FILE and, for Windows, FLEXLM_BATCH environment variables.

3.8. License Support

All new PGI licenses include free PGI Support Service during the money-back guarantee period. For more information about this service and how to extend it, refer to Product Support.

4. PGI Installations on Linux

This section describes how to install PGI products in a generic manner on a Linux system. It covers local and network installations.

4.1. Prepare to Install on Linux

Preparation for installing on Linux requires:

  • Support for compiling and linking 64-bit executables requires that gcc be in your $PATH.
  • For C++ compiling and linking, g++ should be installed prior to installing PGI.
  • For cluster installations, access to all the nodes is required. In addition, you should be able to connect between nodes using rsh or ssh, including to/from the same node you are on. The hostnames for each node should be the same as those in the cluster machine list for the system (machines.LINUX file).

In a typical local installation, the default installation base directory is /opt/pgi.

If you choose to perform a network installation, you should specify:

  • A shared file system for the installation base directory. All systems using the compilers should use a common pathname.
  • A second directory name that is local to each of the systems where the PGI compilers and tools are used. This local directory contains the libraries to use when compiling and running on that machine. Use the same pathname on every system, and point to a private (i.e. non-shared) directory location.

This directory selection approach allows a network installation to support a network of machines running different versions of Linux. If all the platforms are identical, the shared installation location can perform a standard installation that all can use.

To Prepare for the Installation:

  • After downloading the PGI installation package, bring up a shell command window on your system.

    The installation instructions assume you are using csh, sh, ksh, bash, or some compatible shell. If you are using a shell that is not compatible with one of these shells, appropriate modifications are necessary when setting environment variables.

  • Verify you have enough free disk space for the PGI installation.

    • The uncompressed installation packages require 1.2 GB of total free disk space.
    • The linux86-64 platform requires up to 1.54 GB of free disk space, depending on the number of packages installed.
  • If you plan to create a permanent license, your computer must be able to access the Internet. You also need to know your IP address and whatever hostname is mapped to that IPaddress.

    Note: If this computer is behind a firewall at your site, make sure it can access the Internet.

    If a proxy server is used, you need this additional information:

    • The address (URL) of the proxy server.
    • Whether the proxy server requires authentication and if so, the username and password.
  • To generate license keys, log in to your account. From this page, you may also create an account or reset your password.

4.2. Installation Steps for Linux

Follow these instructions to install the software:

  1. Unpack the PGI software. In the instructions that follow, replace <tarfile> with the name of the file that you downloaded. Use the following command sequence to unpack the tar file before installation.
    % tar xpfz <tarfile>.tar.gz
  2. Run the installation script(s). Install the compilers by running [sudo] ./install from the directory where you unpacked the tar file. For PGI CDK, after the compilers are installed, install the additional CDK components by running the install_cdk script. While you do not need root-level access permission to install the PGI CDK, you must have permissions to create and copy files on the cluster nodes.
    Important: The installation script must run to completion to properly install the software.
    To successfully run this script to completion, be prepared to do the following:
    • Consent to the PGI End-User License Agreement (EULA) available to preview at install_components/common/LICENSE.txt.
    • If you are installing a PGI network floating license, determine whether to perform a local installation or a network installation.
    • Determine whether to install the optional components:

      • NVIDIA CUDA components
      • Open MPI library
    • Define where to place the installation directory. The default is /opt/pgi.
    • Determine whether to use the built-in utility to generate license keys.
    Note: Linux users now have the option of automating the installation of the PGI compiler suite without interacting with the usual prompts. This may be useful in a large institutional setting, for example, where automated installation of PGI compilers over many systems could be efficiently done with a script.
    To enable the silent installation feature, set the appropriate environment variables prior to running the installation script. These variables are as follows:
    PGI_SILENT (required) Set this variable to "true" to enable silent installation.
    PGI_ACCEPT_EULA (required) Set this variable to "accept" to indicate that the user has accepted the PGI EULA and all applicable third-party EULAs; these EULAs are located in the install_components/common/ subdirectory in the directory where the PGI installation tar file was uncompressed and untarred.
    PGI_INSTALL_DIR (required) Set this variable to a string containing the desired installation location, e.g. /opt/pgi.
    PGI_INSTALL_TYPE (required) Set this variable to select the type of install. The accepted values are "single" for a single system install or "network" for a network install.
    PGI_INSTALL_LOCAL_DIR (required for network install) Set this variable to a string containing the path to a local file system when choosing a network install.
    PGI_INSTALL_NVIDIA (optional) Set this variable to "true" to enable the installation of the optional NVIDIA components, such as CUDA.
    PGI_INSTALL_AMD (optional) Set this variable to "true" to enable the installation of the optional AMD components.
    PGI_INSTALL_JAVA (optional) Set this variable to "true" to enable the installation of the Java Runtime Environment. The JRE is required for the PGI debugger and PGI profiler. If a JRE is already present on the system, it is not necessary to reinstall.
    PGI_INSTALL_MPI (optional) Set this variable to "true" to enable the installation of the Open MPI environment.
    PGI_MPI_GPU_SUPPORT (optional) Set this variable to "true" to enable NVIDIA GPU support in the Open MPI environment.
    The PGI installation scripts install all of the binaries for the PGI compilers, tools, and libraries in the appropriate subdirectories within the specified installation directory. This main directory is defined during installation as $PGI and the $PGI environment variable should be set to the path of this directory before using the compilers.
    Important: If you choose not to generate license keys at installation time, record the FlexNet hostid and hostname that are echoed to the screen. This information is also saved to the file /opt/pgi/license.info, where /opt/pgi is the installation directory.
    The PGI installation script asks if you wish to enable NVIDIA GPU support in Open MPI. If you choose to disable GPU support in Open MPI at installation time, then the installation script writes the following environment variable setting to /opt/pgi/linux86-64/2017/mpi/openmpi-1.10.2/bin/env.sh, where /opt/pgi is the installation directory: export OMPI_MCA_mpi_cuda_support=0 Should you decide at a later time to enable NVIDIA GPU support in Open MPI, you may do so by simply commenting out this line in the file by inserting a # character at the beginning of the line.
  3. Make PGI products accessible.

    When the installation script has completed, execute the following commands to make the PGI products accessible and to initialize your environment for use by FlexNet.

    Note: Each user must issue the following sequence of commands to initialize the shell environment prior to using the PGI compilers and tools.

    For linux86-64:

    To use the linux86-64 version of the compilers and tools, execute the following commands, assuming you have installed in the default /opt/pgi directory.

    In csh, use these commands:

    % setenv PGI /opt/pgi
    % set path=(/opt/pgi/linux86-64/17.9/bin $path)
    % setenv MANPATH "$MANPATH":/opt/pgi/linux86-64/17.9/man
    % setenv LM_LICENSE_FILE /opt/pgi/license.dat:"$LM_LICENSE_FILE" 

    In bash, sh, or ksh, use these commands:

    $ export PGI=/opt/pgi;
    $ export PATH=/opt/pgi/linux86-64/17.9/bin:$PATH;
    $ export MANPATH=$MANPATH:/opt/pgi/linux86-64/17.9/man;
    $ export LM_LICENSE_FILE=$LM_LICENSE_FILE:/opt/pgi/license.dat; 

    For linux86:

    To use only the linux86 version of the compilers and tools, or to target linux86 as the default, use a setup similar to the previous one, changing the path settings as illustrated in the following commands. Again, the following commands are for installations located in the default /opt/pgi directory.

    In csh, use these commands:

    % setenv PGI /opt/pgi
    % set path=(/opt/pgi/linux86/17.9/bin $path)
    % setenv MANPATH "$MANPATH":/opt/pgi/linux86/17.9/man
    % setenv LM_LICENSE_FILE "$LM_LICENSE_FILE":/opt/pgi/license.dat 

    In bash, sh, or ksh, use these commands:

    $ export PGI=/opt/pgi;
    $ export PATH=/opt/pgi/linux86/17.9/bin:$PATH;
    $ export MANPATH=$MANPATH:/opt/pgi/linux86/17.9/man;
    $ export LM_LICENSE_FILE=$LM_LICENSE_FILE:/opt/pgi/license.dat; 
    Tip: You should add these commands to your shell startup files to ensure that you have access to the PGI products in future login sessions.
  4. Verify the release number of the installed software. It should say 17.9.

    To verify the release number of the products you have installed, use the -⁠V option on any of the compiler commands, as illustrated in the following examples. If you use -⁠v instead, you can also see the sequence of steps the compiler uses to compile and link programs for execution on your system.

    For Fortran 77, use: pgf77 -V x.f
    For Fortran 2003, use: pgfortran -V x.f
    For C++, use: pgc++ -V x.cpp
    For ANSI C, use: pgcc -V x.c
    Note: These commands can be successfully executed even if the files x.f or x.c do not exist and you have not completed the licensing phase of the installation. Use them to check that you have installed the proper version of the compilers and have initialized your environment to enable access to that version.
  5. Generate and install license keys.
    Note: This step is necessary only if you chose not to allow the installation script to perform these tasks for you. Alternatively, you may use the PGI License Setup Tool, normally installed at $PGI/<platform>/<rel_number>/bin/pgi_license_tool.

    Most PGI products are license-managed using FlexNet licensing. This system requires that you possess a valid license key file for the licensed product to operate. Most PGI products include temporary license keys with the installation package. Permanent license keys are available from the PGI website.

    Other components, such as Open MPI, are open-source products that are not license-managed.

    Any temporary license keys included with your package will be installed automatically. You can verify this by confirming the existance of the license.dat file in your PGI installation directory. If so, you may skip to the next section.

    To obtain your permanent license key, you need the following information:

    • An account on the PGI website. You probably created this account when you downloaded the PGI software.

      Tip: The username (email address) and password required to connect to the pgroup.com website are the same ones you used to download the installation software from the web site.
      • If you purchased a license without creating an account, one was created for you when your order was processed. Please check for an activation email from accounts-noreply@pgroup.com.
      • If you don’t have an account, you can create one at: https://www.pgroup.com/register.
    • The FlexNet hostid and hostname of the computer on which the software is installed. The installer echoes this information to your screen.

    You can also obtain your FlexNet hostid by using the following command after you have installed the products and initialized the environment variables:
    % lmutil lmhostid

    You should see a message similar to the following message with one or more hostids displayed.

    The FlexNet host ID of this machine is "12345678abcd edcba9876543".

    In this example, you can use either 12345678abcd or edcba9876543, but not both, as the hostid.

    Note: Hostids come from configured network cards. If you use your computer in multiple network environments, you may need to run the following command in each environment to see which hostids are configured. Then, to reduce potential license problems, choose the hostid that occurs in all your environments.

    Install License Keys

    Once you have generated your permanent license key, copy and paste it into the file: /opt/pgi/license.dat, substituting the appropriate installation directory path if you have not installed in the default /opt/pgi directory.

    The license.dat depends on the product you are installing. However, each license.dat file looks somewhat similar to the following sample file from a PGI installation:
    SERVER <hostname> <hostid> 27000
    DAEMON pgroupd
    PACKAGE PGI2017-<PGI_PIN> pgroupd <support end date> \
    <...>
    6167 7015 3F05 9C37 2315 ACDF 1B73 DAA9 FBAE"

    In your license file:

    • <hostid> should match the hostid you submitted above when you generated your license keys. You should see it on the SERVER line.
    • If necessary, you can enter or edit the <hostname> entry manually, but you cannot edit the <hostid> entry or you will invalidate the license keys.
    • <support end date> represents the date your support expires. For example, if your support end date for your PGI PIN (Product Identification Number) is August 1, 2017, then the date in your file is 2017.0801. For information on how to renew your support contract, refer to Product Support.

    • <PGI_PIN> represents the six-digit product identification number for this license.

    Note: Please include your PIN when contacting PGI for technical support for the products you have purchased. This PIN is also in your order confirmation email.
  6. Start the license manager daemon.
    Important: If you are using a PGI Community Edition license key, evaluating PGI software with a starter license key, or if you used the PGI installation script, you do not need to perform this step and can proceed to Step 7.

    Installations in a directory other than the default /opt/pgi

    Note: The following refers to the shell script template for linux86-64. If you have installed only linux86, please substitute linux86 for linux86-64.

    Perform the following steps if you installed the compilers in a directory other than /opt/pgi:

    1. Edit the shell script template $PGI/linux86-64/17.9/bin/lmgrd.rc.
    2. Substitute the correct installation directory for /opt/pgi in the section of the script entitled Where to find the PGI Software.
    3. Save the file and exit the editor.

    Issue the following command to start the license server and pgroupd license daemon running on your system:

    % cd $PGI/linux86-64/17.9/bin/
    % ./lmgrd.rc start
    Tip: To use the more restrictive access of invoking lmgrd with the -⁠local switch, refer to the lmgrd.rc file for a description of the -⁠local switch and how to use it.

    If you wish to stop the license server and pgroupd license daemon at a later time, you can do so with the command:

    % cd $PGI/linux86-64/17.9/bin/
    % ./lmgrd.rc stop

    Start license server upon reboot:

    To start the license server and pgroupd license daemon each time your system is booted:

    1. Log in as root.

      Note: You must be logged in as root to successfully execute these commands.
    2. Verify you have set the PGI environment variable as described in Step 3 of this installation process.
    3. Execute the following two commands:
      % cp $PGI/linux86/17.9/bin/lmgrd.rc  /etc/init.d/lmgrd
      % ln -s /etc/init.d/lmgrd  /etc/rc.d/rc3.d/S90lmgrd

    There are two values in this example that may be different on your system:

    • Your rc files may be in a directory other than the one in the example: /etc/init.d. If the rc files are in a directory such as /etc/rc.d/init.d, then substitute that location in the example.
    • Your system’s default runlevel may be something other than ‘3’, the level used in this example. You can run /sbin/runlevel to check the system’s runlevel. If the runlevel on your system is different, then you must set the correct subdirectory; use your system’s runlevel in place of the ‘3’ in the preceding example.

    Start license server upon reboot on Ubuntu

    To start the license server and pgroupd license daemon each time your system is booted:

    1. Log in as root.

      Note:

      You must be logged in as root to successfully execute these commands.

    2. Verify you have set the PGI environment variable as described in Step 3 of this installation process.
    3. Execute the following two commands:
      % cp $PGI/linux86/17.9/bin/lmgrd.rc  /etc/init.d/lmgrd
      % ln -s /etc/init.d/lmgrd  /etc/rc.d/rc3.d/S90lmgrd

    There are two values in this example that may be different on your system:

    • Your rc files may be in a directory other than the one in the example: /etc/init.d. If the rc files are in a directory such as /etc/rc.d/init.d, then substitute that location in the example.
    • Your system’s default runlevel may be something other than ‘3’, the level used in this example. You can run /sbin/runlevel to check the system’s runlevel. If the runlevel on your system is different, then you must set the correct subdirectory; use your system’s runlevel in place of the ‘3’ in the preceding example.

    chkconfig(8) Utility

    Most Linux distributions include the chkconfig(8) utility which manages the runlevel scripts. If your system has this tool and you wish to use it, then run the following commands:

    % cp $PGI/linux86/17.9/bin/lmgrd.rc /etc/init.d/
    % /sbin/chkconfig --add lmgrd

    These commands create the appropriate links in the /etc/init.d directory hierarchy. For more information on chkconfig, please refer to the manual page.

    Important:

    You can co-install Release 2017 with Release 2015, 2014, 2013, 2012, 2011, 2010, 9.x, 8.x, 7.x, 6.x and/or 5.2; and you can use any of these versions of the compilers and tools with the latest versions of lmgrd and pgroupd and a single Release 2017 license file.

    If you use the lmgrd.rc file to start lmgrd automatically after a reboot of your system, you need to modify your lmgrd script in the /etc/rc.d or /etc/init.d directory to use the latest lmgrd daemon.

    For example, your lmgrd script may look like this, where <target> is replaced appropriately with linux86 or linux86-64.

       ## Path to master daemon lmgrd
       # Commented out previous path to 13.8:
       #LMGRD=$PGI/<target>/13.8/bin/lmgrd
       LMGRD=$PGI/<target>/17.9/bin/lmgrd
    
       ## Command to stop lmgrd
       #Commented out previous path to 13.8:
       #LMUTIL=$PGI/<target>/13.8/bin/lmutil
       LMUTIL=$PGI/<target>/17.9/bin/lmutil
  7. Review documentation.

    PGI documentation is available online in both HTML and PDF formats.

  8. Complete network installation tasks.
    Note: Skip this step if you are not installing PGI network floating license using a network installation.

    For a network installation, you must run the local installation script on each system on the network where the compilers and tools will be available for use.

    If your installation base directory is /opt/pgi and /usr/pgi/shared/17.9 is the common local directory, then run the following commands on each system on the network.
    /opt/pgi/linux86-64/17.9/bin/makelocalrc  -x /opt/pgi/linux86-64/17.9 \
         -net /usr/pgi/shared/17.9

    These commands create a system-dependent file localrc.machinename in both of these directories: /opt/pgi/linux86/17.9/bin and /opt/pgi/linux86-64/17.9/bin. The commands also create the following three directories containing libraries and shared objects specific to the operating system and system libraries on that machine:

    • /usr/pgi/shared/17.9/lib
    • /usr/pgi/shared/17.9/liblf
    • /usr/pgi/shared/17.9/lib64
    Note: The makelocalrc command does allow the flexibility of having local directories with different names on different machines. However, using the same directory on different machines allows users to easily move executables between systems that use PGI-supplied shared libraries.


    Installation of the PGI products for Linux is now complete. For assistance with difficulties related to the installation, please contact the PGI technical reporting service.

    The following two sections contain information detailing the directory structure of the PGI installation, and instructions for PGI end-users to initialize environment and path settings to use the PGI compilers and tools.

4.3. End-user Environment Settings

4.3.1. PGI Compilers and Tools

After software installation is complete, each user’s shell environment must be initialized to use the PGI compilers and tools. Assume the license file is in /opt/pgi/license.dat, and the lmgrd license manager is running.

Note:

Each user must issue the following sequence of commands to initialize the shell environment before using the PGI compilers and tools.

To make the PGI compilers and tools available:

In csh, use these commands:

% setenv PGI /opt/pgi
% setenv MANPATH "$MANPATH":$PGI/linux86-64/17.9/man
% setenv LM_LICENSE_FILE $PGI/license.dat
% set path = ($PGI/linux86-64/17.9/bin $path)

Once the compilers are available, you can make the Open MPI commands and Open MPI man pages accessible using these csh commands:

% set path = ($PGI/linux86-64/17.9/mpi/openmpi/bin $path)
% setenv MANPATH "$MANPATH":$PGI/linux86-64/17.9/mpi/openmpi/man

In bash, sh, or ksh, use these commands:

$ PGI=/opt/pgi; export PGI 
$ MANPATH=$MANPATH:$PGI/linux86-64/17.9/man; export MANPATH 
$ LM_LICENSE_FILE=$PGI/license.dat; export LM_LICENSE_FILE 
$ PATH=$PGI/linux86-64/17.9/bin:$PATH; export PATH

Once the 64-bit compilers are available, you can make the Open MPI commands and Open MPI man pages accessible using these commands.

$ export PATH=$PGI/linux86-64/17.9/mpi/openmpi/bin:$PATH
$ export MANPATH=$MANPATH:$PGI/linux86-64/17.9/mpi/openmpi/man

4.3.2. Open MPI access

To access Open MPI and the Open MPI man pages for x86-64 linux86-64, execute these commands:

In csh, use these commands:

% set path = (/opt/pgi/linux86-64/17.9/bin  \
		/opt/pgi/linux86-64/17.9/mpi/openmpi/bin $path)
% setenv MANPATH  "$MANPATH":/opt/pgi/linux86-64/17.9/mpi/openmpi/man

In bash, sh or ksh, use these commands:

$ export PATH=/opt/pgi/linux86-64/17.9/bin: \
		/opt/pgi/linux86-64/17.9/mpi/openmpi/bin:$PATH
$ export MANPATH=$MANPATH:/opt/pgi/linux86-64/17.9/mpi/openmpi/man

4.3.3. MVAPICH access

To access MVAPICH2 and the MVAPICH2 man pages for x86-64 linux86-64, execute these commands:

In csh, use these commands:

% set path = (/opt/pgi/linux86-64/17.9/bin
		    /opt/pgi/linux86-64/17.9/mpi/mvapich/bin $path)
% setenv MANPATH  "$MANPATH":/opt/pgi/linux86-64/17.9/mpi/mvapich/man

In bash, sh or ksh, use these commands:

$ export PATH=/opt/pgi/linux86-64/17.9/bin:
		    /opt/pgi/linux86-64/17.9/mpi/mvapich/bin:$PATH
$ export MANPATH=$MANPATH:/opt/pgi/linux86-64/17.9/mpi/mvapich/man

5. Installations on macOS

This section describes how to install PGI software on an Apple computer running Apple macOS.

Note: PGI products for Apple macOS are supported on Intel processor-based computers running OS X version 10.9 or greater; the PGI debugger is not currently supported on 10.12. PGI products are compatible with Apple Xcode 5.1.1 through 8.x installed. Xcode is available from the Apple App Store.

The default installation base directory is /opt/pgi.

5.1. Preparing to Install on Apple macOS

To prepare for the installation:

  • Verify you have enough free disk space.

    • On the osx86 platform, PGI installation requires 650 MB of free disk space.
    • On the osx86-64 platform, PGI installation requires 1.75 GB of free disk space.

    In addition, the download file requires approximately 600 MB.

  • Verify that Xcode 5.1.1 or greater (through 8.x) is installed.

    • If you know how to run Xcode, start Xcode and click About Xcode to verify the version is 5.1.1 or greater (through 8.x).
    • If you do not know how to run Xcode or are uncertain if it is installed on your system, try searching for it using Spotlight, which can be found by clicking the magnifying glass in the upper-right corner of the menu bar.
Note: PGI software for macOS requires the Xcode application, which provides several components of the tool chain, including the system assembler, linker, and runtime libraries. However, PGI software runs in Terminal, not in the Xcode IDE, and the PGI debugger and PGI profiler have their own GUIs.

In preparation for installing PGI software on macOS, first review Figure 2, an overview of the installation process.

Figure 2. Apple macOS Installation Overview
png for PDF.

5.2. System Configuration to Enable Debugger ‘Attach’

The PGI debugger can debug programs that are launched by the debugger, either by specifying the program on the debugger's command line, using the debug or load commands, or by specifying a program in the Connections tab of the debugger GUI.

Apple macOS security features prevent the PGI debugger from attaching to a running program unless some configuration is performed. Users who need to attach to a running program must be able to enter the authentication credentials for a user that is a member of the _developer group. Users can be added to a group using the following command:

sudo dseditgroup -o edit -a usernametoadd -t user _developer

5.3. Installation Steps for macOS

Once you have prepared for the installation, follow these instructions to install the software:

  1. Access the installation package. Download the software from the PGI download page or another electronic distribution site. If it does not mount automatically, open the download package to mount it.
  2. Install the software. Double-click the PGI 17.9.pkg icon, which is part of the mounted disk. Follow the installation instructions.
    1. When you see the initial system check dialog, click continue to allow the installation script to check that your system has the required components for installing the software, such as Xcode 5.1.1 or greater (through 8.x) and gcc.
    2. Select the installation drive. The compilers will be automatically be installed into the default directory: /opt/pgi.

    After the software is installed, the installation script performs some system-specific customization and then initializes for licensing.

  3. Make PGI products accessible and prepare for licensing. To initialize the PGI compilers and tools, import the PGI 2017 terminal settings file located in the PGI installation directory using Terminal's Shell | Import command. You can access the installation directory in the Open file dialog by typing Command-Shift-G and entering the path, for example /opt/pgi. Once initialized, you can open a Terminal session preconfigured with the PGI environment directly from within Terminal. To do this, bring up a PGI window by using either the Shell | New Window or Shell | New Tab menu commands; and then select PGI 2017. For more configuration information, refer to End-user Environment Settings.
  4. Verify the release number of the installed software. It should say 17.9.

    To verify the release number of the products you have installed, use the -⁠V option on any of the compiler commands, as illustrated in the following examples. If you use -⁠v instead, you can also see the sequence of steps the compiler uses to compile and link programs for execution on your system.

    For Fortran 77, use: pgf77 -V x.f
    For Fortran 2003, use: pgfortran -V x.f
    For C++, use: pgc++ -V x.cpp
    For ANSI C, use: pgcc -V x.c
    Note: These commands can be successfully executed even if the files x.f or x.c do not exist and you have not completed the licensing phase of the installation. Use them to check that you have installed the proper version of the compilers and have initialized your environment to enable access to that version.
  5. Generate and install license keys.

    Most PGI products are license-managed using FlexNet licensing. This system requires that you possess a valid license key file for the licensed product to operate. Most PGI products include temporary license keys with the installation package. Permanent license keys are available from the PGI website.

    Other components, such as Open MPI, are open-source products that are not license-managed.

    Any temporary license keys included with your package will be installed automatically. You can verify this by confirming the existance of the license.dat file in your PGI installation directory. If so, you may skip to the next section.

    To obtain your permanent license key, you need the following information:

    • An account on the PGI website. You probably created this account when you downloaded the PGI software.

      Tip: The username (email address) and password required to connect to the pgroup.com website are the same ones you used to download the installation software from the web site.
      • If you purchased a license without creating an account, one was created for you when your order was processed. Please check for an activation email from accounts-noreply@pgroup.com.
      • If you don’t have an account, you can create one at: https://www.pgroup.com/register.
    • The FlexNet hostid and hostname of the computer on which the software is installed. The installer echoes this information to your screen.

    You can also obtain your FlexNet hostid by using the following command after you have installed the products and initialized the environment variables:
    % lmutil lmhostid

    You should see a message similar to the following message with one or more hostids displayed.

    The FlexNet host ID of this machine is "12345678abcd edcba9876543".

    In this example, you can use either 12345678abcd or edcba9876543, but not both, as the hostid.

    Note: Hostids come from configured network cards. If you use your computer in multiple network environments, you may need to run the following command in each environment to see which hostids are configured. Then, to reduce potential license problems, choose the hostid that occurs in all your environments.

    The preceding command returns output in the form: HOSTNAME=xxxxx. However, when you create a license, use only the actual hostname, that is xxxxx in the hostname field. For example, if the information displayed is HOSTNAME=abcd1234, then use only abcd1234. The goal is to have the hostname map to the IP address of the license server. Every system on the network should be able to ping hostname and get the correct IP address.

    Generate License Keys

    Once you have logged on using your registered PGI email and password, you should see a screen similar to the following:

    Figure 3. Welcome PGI Account Sample
    png for PDF

    Install License Keys

    Once you have generated your permanent license key, copy and paste it into the file /opt/pgi/license.dat, or substitute the appropriate installation directory path if you have not installed in the default /opt/pgi directory.

    For example, if you have purchased and generated a permanent licence key as previously described, the license.dat file should look similar to the following:

    SERVER <hostname> <hostid> 27000
    DAEMON pgroupd
    PACKAGE PGI2016-<PGI_PIN> pgroupd <support end date> \
    <...>
    6167 7015 3F05 9C37 2315 ACDF 1B73 DAA9 FBAE"

    In your license file:

    • <hostid> should match the hostid you submitted above when you generated your license keys. You should see it on the SERVER line.
    • If necessary, you can enter or edit the <hostname> entry manually, but you cannot edit the <hostid> entry or you will invalidate the license keys.
    • <support end date> represents the date your support expires. For example, if your support end date for your PGI PIN (Product Identification Number) is August 1, 2017, then the date in your file is 2017.0801. For information on how to renew your support contract, refer to Product Support.

    • <PGI_PIN> represents the six-digit product identification number for this license.

    Note: Please include your PIN when contacting PGI for technical support for the products you have purchased. This PIN is also in your order confirmation email.
  6. Start the license manager daemon.
    Important: If you are using a PGI Community Edition license key or evaluating PGI software with a starter license key, you do not need to perform this step.

    If this is your first installation of PGI software, you need to configure and start up the license server. This is not a requirement for subsequent installations.

    Follow these steps to start the license server and pgroupd license daemon running on your system:

    Note: Please make sure that com.pgroup.flexlm.plist is owned and readable by root only
    1. In Terminal, use the sudo command to get a root bash shell; enter your password:
      % sudo bash
      <password>
    2. From the PGI bin directory, copy the PGI license configuration files:
      % sudo cp com.pgroup.flexlm.plist /Library/LaunchDaemons
    3. Change the file ownership:
      % sudo chown root:wheel /Library/LaunchDaemons/com.pgroup.flexlm.plist
    4. Change file access permissions:
      % sudo chmod 0644 /Library/LaunchDaemons/com.pgroup.flexlm.plist
    5. Start the license server:
      % sudo launchctl load /Library/LaunchDaemons/com.pgroup.flexlm.plist

    The license server should now be running. Enable remote login under the Sharing option in your System Preferences to have the license server restart automatically whenever you reboot.

    Installation of your FlexNet licensing is now complete. For assistance with difficulties related to the installation, please contact the PGI technical reporting service.

  7. Review documentation.

    PGI documentation is available online in both HTML and PDF formats.

5.4. End-user Environment Settings on macOS

Once software installation is complete, each user must initialize their environment to use the compilers successfully. You can either use the PGI Terminal settings or you can initialize your Terminal shell manually.

5.4.1. Use PGI Terminal Settings

There are two methods to use the PGI Terminal Settings:

  • Use the PGI Terminal Settings by bringing up a PGI command window and double-clicking the PGI2017.terminal file. PGI compilers and tools are accessible and your environment is pre-initialized.
  • Use the PGI Terminal Settings by launching the Terminal application located in the Applications | Utilities folder. Under the Shell menu, select either New Window | PGI2017 or New Tab | PGI2017. Both commands open a bash shell that is preconfigured with the PGI environment.

5.4.2. Initialize your Terminal Shell Manually

To initialize your Terminal shell manually, you launch the Terminal application located in the Applications | Utilities folder and enter the commands described for the desired compilers.

Each of the following commands assume this:

  • The license file is in /opt/pgi/license.dat.
  • The lmgrd license manager is running.

Make the PGI compilers available

Launch the Terminal application located in the Applications | Utilities folder and enter the following commands to make the PGI compilers and tools available.

In bash, sh, or ksh, use these commands:

$ PGI=/opt/pgi; export PGI 
$ LM_LICENSE_FILE=$PGI/license.dat; export LM_LICENSE_FILE
$ PATH=$PGI/osx86-64/17.9/bin:$PATH; export PATH 

In csh, use these commands:

% setenv PGI /opt/pgi
% setenv LM_LICENSE_FILE $PGI/license.dat
% set path = ($PGI/osx86-64/17.9/bin $path)

5.4.3. Use MPICH

To use the bundled version of MPICH, use these commands:

In bash, sh, or ksh, use these commands:

$ PATH=$PGI/osx86-64/2017/mpi/mpich/bin:$PATH 
$ export PATH 

In csh, use this command:

% set path = ($PGI/osx86-64/2017/mpi/mpich/bin $path)

6. Installations on Microsoft Windows

This section describes how to install PGI compilers and tools on a system running a Microsoft Windows operating system.

6.1. Preparing to Install on Windows: Prerequisites

All Products: Microsoft Windows SDK

The Microsoft Windows Software Development Kit (SDK) is a prerequisite for all PGI Windows installations.

All Products: Microsoft Update for Universal C Runtime

PGI compilers leverage the Microsoft tool chain. To use these tools on operating systems older than Windows 10, you must first install Microsoft's Update for Universal C Runtime. Depending on the configuration details of your system, this update may have already been installed as part of the automatic Windows Updates applied to your system.

PGI Community Edition: Microsoft Visual Studio 2015

Microsoft Visual Studio 2015 with Visual C++ is a prerequisite for the PGI Community Edition on Windows. For configuration information, see the PGI Community Edition webpage.

Note: Verify you have enough free disk space. PGI software requires 750 MB of free disk space during the installation. This does not include the space needed for the download file itself.

6.2. Installation Steps for Windows

Download the software from the PGI download page or another electronic distribution site. Select the install package appropriate for your OS.

Note:

If you are using Internet Explorer 9, be sure to set the compatibility mode option when reading the download page, as it may look blank otherwise.

Once you have prepared for the installation, follow these instructions to install the software:

  1. Run the installation executables as Administrator. Administrator privileges are required to install PGI software.
  2. If you have installed the PGI Community Edition, skip to step 8.
  3. Run PGI Licensing.

    At the conclusion of the installation process, the installer will ask you if you would like to run the PGI Licensing Setup tool. This tool automates steps three (3) through six (6) in this process.

    To use the PGI Licensing Setup tool, your computer must meet these requirements:

    • Be connected to the Internet.
    • Have Microsoft .NET Framework 4.0 installed.
    • Have Internet Explorer Version 6.0 or higher installed and configured.

    If your computer does not meet these prerequisites, then you can either make any necessary changes to your system and run the PGI Licensing Setup tool later, or follow steps three through six in this process.

    Important: If you choose to run the PGI Licensing Setup tool later, you can find it in the PGI folder under the Start menu or as an icon on the Start screen.
    Important: If you choose to run the PGI Licensing Setup tool later, you can find it in the PGI folder under the Start menu or as an icon on the Start screen.

    When you run the program, the PGI Licensing Setup tool walks you through the license generation and installation process. You will be prompted for your PGI username and password. The tool also informs you of any problems it experiences with installation and provides instructions on how to proceed.

    Note: If the PGI Licensing Setup tool reports a successful license installation, installation is complete.
  4. Make PGI products accessible and prepare for licensing. Once software installation is complete, PGI compilers and tools are accessible and your environment is pre-initialized whenever you bring up a PGI command window. To bring up a PGI command window, double-click on the PGI desktop icon.
  5. Verify release number.

    Verify the release number of the products you have installed. Open the PGI command window from your desktop by double-clicking the PGI icon and entering one of the following commands. The release number is in the first line displayed in the BASH shell window.

    For Fortran 77, use: pgf77 -V
    For Fortran 95, use: pgfortran -V
    For ANSI C, use: pgcc -V
    Note: These commands can be successfully executed even if you have not completed the licensing phase of the installation. Use it to check that you have installed the proper version of the compilers and have initialized your environment to enable access to that version.
  6. Generate and install license keys.

    Most PGI products are license-managed using FlexNet licensing. This system requires that you possess a valid license key file for the licensed product to operate. Most PGI products include temporary license keys with the installation package. Permanent license keys are available from the PGI website.

    Other components, such as Open MPI, are open-source products that are not license-managed.

    Any temporary license keys included with your package will be installed automatically. You can verify this by confirming the existance of the license.dat file in your PGI installation directory. If so, you may skip to the next section.

    To obtain your permanent license key, you need the following information:

    • An account on the PGI website. You probably created this account when you downloaded the PGI software.

      Tip: The username (email address) and password required to connect to the pgroup.com website are the same ones you used to download the installation software from the web site.
      • If you purchased a license without creating an account, one was created for you when your order was processed. Please check for an activation email from accounts-noreply@pgroup.com.
      • If you don’t have an account, you can create one at: https://www.pgroup.com/register.
    • The FlexNet hostid and hostname of the computer on which the software is installed. The installer echoes this information to your screen.

    After you have installed the PGI software, you can obtain your FlexNet hostid by double-left-clicking on the PGI desktop icon to open a PGI command window, and typing these commands:

    PGI$  cd $PGI
    PGI$  cat license.info

    You should see information similar to the following:

    For a permanent license, please read the order acknowledgment that you received. Connect to www.pgroup.com/login with the registered email and password in your order acknowledgment.

       FlexNet Host ID:  0123456789ab
       Installation: C:\Program Files\PGI\
       PGI Release: 2017

    Install License Keys

    Once you have generated your permanent license key, cut and paste it into your license.dat file. In a typical configuration, where C:\ is the system drive and you installed the software using the default location, this file would be found in C:\Program Files\PGI\license.dat.

    • If you have not previously received license keys from PGI, replace the contents of the license.dat file created during installation with the license keys you generated using the preceding steps.

      Note: You must have Administrator privileges to modify or replace the license.dat file.
    • If your license.dat file already contains keys that you previously received from PGI, first make a copy of the existing license.dat file in case you encounter a problem with the new license. Then do one of the following:

      • If the license keys in the file are for a previous release of the same product, overwrite the keys.
      • If the license keys in the file are for different PGI products, append the new keys to the keys already in this file.
  7. Start the PGI License Service.
    Note: If you are using a PGI Community Edition license key or evaluating a PGI product using a starter license key, you do not need to start the license server.

    The PGI License Server is a Windows Service. To start it, follow these steps:

    1. Open the Services dialog from the Control Panel:

      Control Panel | Administrative Tools | Services

    2. Select PGI License Server.
    3. Select Start, if the PGI service is stopped. If the PGI service is running, STOP and then START it. This process guarantees that the new PGI license is served and that the older, cached PGI license is no longer active.
    Note: The PGI License Server service starts automatically on system reboot, provided that the license.dat file contains valid keys.
  8. Review documentation.

    PGI documentation is available online in both HTML and PDF formats.

  9. Customize PGI Settings

    Optionally, you can customize the setup as described in Customizing the Command Window and PGI Default Installation Directories below.

6.3. Customizing the Command Window

By default, when you double-click on the PGI desktop icon, a standard black-background command window appears on your screen. This window is pre-initialized with environment and path settings for use of the PGI compilers and tools. If you prefer different background or text colors, font style, window size, or scrolling capability, you can customize the “shortcut” that creates the PGI command window.

To customize your window, right-click the PGI desktop icon, and select “Properties” from the pop-up menu. In the PGI Properties dialog box, select the tabs for the features you want to customize, and make the desired modifications.

6.4. PGI Default Installation Directories

This section contains information about the default installation directories. The default installation directory depends on your platform.

The following table lists the default installation directories, indicating the related platform or tool.

6.4.1. Default Installation Directories

Table 3. Default Windows Installation Directories
Product Default Installation Directory
PGI %SYSTEMDRIVE%\Program Files\PGI
PGI CE %SYSTEMDRIVE%\Program Files\PGICE
Cygwin %SYSTEMDRIVE%\cygwin

6.4.2. Tool Default Versions

PGI ships a subset of Cygwin with its products on Windows. Beginning with PGI release 14.4, the version of Cygwin bundled with PGI is Cygwin 1.7.27. This was the version of Cygwin current as of January 2014. In general, PGI users should not notice significant differences in Cygwin behavior from the previous version, which was Cygwin 1.7.16. For information about configuring and troubleshooting Cygwin, you can visit the following websites:

6.5. PGROUPD_LICENSE_FILE and FLEXLM_BATCH

This section describes two environment variables that you can use with FlexNet:

  • PGROUPD_LICENSE_FILE
  • FLEXLM_BATCH

6.5.1. PGROUPD_LICENSE_FILE

The recommended installation location is the default C:\Program Files\PGI folder; the recommended location for storing your license keys is as the file C:\Program Files\PGI\license.dat.

The system environment variable PGROUPD_LICENSE_FILE is not required by PGI products on Windows but you can use it to override the default location that is searched for the license.dat file.

To use the system environment variable PGROUPD_LICENSE_FILE, set it to the full path of the license key file. To do this, follow these steps:

  1. Open the System Properties dialog from the Control Panel's System option.
  2. Select the Advanced tab.
  3. Click the Environment Variables button.
    • If PGROUPD_LICENSE_FILE is not already an environment variable, create a new system variable for it. Set its value to the full path of your license.dat file.
    • If PGROUPD_LICENSE_FILE already exists as an environment variable, append the path to the license file in the variable's current value using a semi-colon to separate entries.

6.5.2. FLEXLM_BATCH

By default, on Windows, the license server creates interactive pop-up messages to issue warnings and errors. This behavior is controlled by the environment variable FLEXLM_BATCH.

Although it is not recommended, you can prevent interactive pop-ups from appearing. To do this, set the environment variable FLEXLM_BATCH to 1.

6.6. Windows Firewall and PGI Debugging

Microsoft Windows Firewall runs by default on some Windows systems. Unless the PGI debugger is included in the Windows Firewall Exceptions list, Windows Firewall may try to block the PGI debugger engine when you debug a program.

6.6.1. Automatic Additions to Windows Firewall Exceptions List

When PGI software is installed

If Windows Firewall is enabled when PGI software is installed, certain components are automatically added to the Exceptions list. These components appear as follows:

  • PGI Debugger 2017

When PGI software is uninstalled

If Windows Firewall is enabled when PGI software is uninstalled, the components previously listed are automatically removed from the Exceptions list.

When Starting the Debugger

If the PGI debugger is not listed in the Exceptions list and Windows Firewall is enabled when you use the PGI debugger to debug, the Firewall displays a dialog that allows you to Unblock the application named pgdebug. If you choose the Unblock option, Windows Firewall adds the debugger (pgdebug) to its list of Exceptions and you do not see the pop-up dialog again unless you reinstall.

Note: On rare occasions, this pop-up may prevent the debug session from starting correctly. If this occurs, use the Task Manager to end the debug session.
Note:

You can manually add these components to the Windows Firewall list of Exceptions.

6.7. Common Windows Installation Problems

The most common installation problems on Windows are related to licensing.

To troubleshoot your installation, first check that the license.dat file you are using contains valid license keys. Second, check that the PGI License Server, a Windows Service, has been started (Control Panel > Admin Tools > Services > PGI).

Typical FlexNet errors encountered may include the following:

  • When using a PGI compiler or tool, a FlexNet License Manager dialog appears that states: ‘LICENSE MANAGER PROBLEM: No such feature exists.’

    This message may appear because the license.dat file accessed by the FlexNet License Manager does not contain valid license keys. Possible reasons for an invalid license key include:

    • Bad format license file—if you stored it from Word, make sure it was stored in plain text format.
    • License does not support this release or this operating system—Make sure your license covers the release you are installing, and is a Windows license.
  • When using a PGI compiler or tool, you may see one of the following FlexNet License Manager dialog messages: ‘LICENSE MANAGER PROBLEM: Cannot connect to license server system.’ or ‘LICENSE MANAGER PROBLEM: Failed to checkout license’

    This message may appear as a result of one of the following conditions:

    • The PGI License Server is not running.
    • Firewall problems exist.
    • The hostname in the license is not one the license server can locate.

      Refer to the information earlier in this section on restarting the license server.

      The hostname must map to the IP address of the license server. You should be able to ping hostname and find that it is mapped to the IP address of the license service. If not, double-check the hostname of the license server and/or your network configuration.

      Every machine using the license server, including the server itself, should be able to successfully ping the hostname and get back the IP address of the server. If your system is using a Firewall, you need to enable two ports for the licensing daemons lmgrd and pgroupd to communicate with the PGI compilers and tools. Edit or add these ports to the license.dat file.

      • On the SERVER line, change the default port 27000 to the lmgrd port.
      • On the DAEMON line, append PORT=### just after pgroupd, replacing ### with the port number pgroupd is allowed to use.
  • By default, on Windows, the license server generates interactive pop-up messages to issue warning and errors. You can use the environment variable FLEXLM_BATCH to prevent interactive pop-up windows.

    To do this, set the environment variable FLEXLM_BATCH to 1.

For assistance with difficulties related to the installation, please contact the PGI technical reporting service.

7. Contact Information

You can contact PGI at:

  • 20400 NW Amberwood Drive Suite 100
  • Beaverton, OR 97006

Or electronically using any of the following means:

The PGI User Forum is monitored by members of the PGI engineering and support teams as well as other PGI customers. The forums contain answers to many commonly asked questions. Log in to the PGI website to access the forums.

Many questions and problems can be resolved by following instructions and the information available in the PGI frequently asked questions (FAQ).

Submit support requests using the PGI Technical Support Request form.

Notices

Notice

ALL NVIDIA DESIGN SPECIFICATIONS, REFERENCE BOARDS, FILES, DRAWINGS, DIAGNOSTICS, LISTS, AND OTHER DOCUMENTS (TOGETHER AND SEPARATELY, "MATERIALS") ARE BEING PROVIDED "AS IS." NVIDIA MAKES NO WARRANTIES, EXPRESSED, IMPLIED, STATUTORY, OR OTHERWISE WITH RESPECT TO THE MATERIALS, AND EXPRESSLY DISCLAIMS ALL IMPLIED WARRANTIES OF NONINFRINGEMENT, MERCHANTABILITY, AND FITNESS FOR A PARTICULAR PURPOSE.

Information furnished is believed to be accurate and reliable. However, NVIDIA Corporation assumes no responsibility for the consequences of use of such information or for any infringement of patents or other rights of third parties that may result from its use. No license is granted by implication of otherwise under any patent rights of NVIDIA Corporation. Specifications mentioned in this publication are subject to change without notice. This publication supersedes and replaces all other information previously supplied. NVIDIA Corporation products are not authorized as critical components in life support devices or systems without express written approval of NVIDIA Corporation.

Trademarks

NVIDIA, the NVIDIA logo, Cluster Development Kit, PGC++, PGCC, PGDBG, PGF77, PGF90, PGF95, PGFORTRAN, PGHPF, PGI, PGI Accelerator, PGI CDK, PGI Server, PGI Unified Binary, PGI Visual Fortran, PGI Workstation, PGPROF, PGROUP, PVF, and The Portland Group are trademarks and/or registered trademarks of NVIDIA Corporation in the U.S. and other countries. Other company and product names may be trademarks of the respective companies with which they are associated.