PGI Workstation, PGI Server, PGI CDK Compilers and Tools Installation Guide

PGI Installation Guide
Version 2016
PGI Compilers and Tools
TABLE OF CONTENTS
Chapter 1. Introduction.........................................................................................................................................................1
1.1. Product Overview........................................................................................................................................................ 1
1.1.1. PGI Workstation and PGI Server Comparison....................................................................................................1
1.1.2. PGI CDK Cluster Development Kit......................................................................................................................1
1.2. Release Components.................................................................................................................................................. 2
1.2.1. Additional Components for PGI CDK.................................................................................................................. 2
1.2.2. MPI Support......................................................................................................................................................... 3
1.3. Terms and Definitions..................................................................................................................................................3
1.4. Supported Processors................................................................................................................................................. 3
1.4.1. Supported Processors......................................................................................................................................... 4
1.5. Supported Operating Systems.................................................................................................................................... 5
1.6. Hyperthreading and Numa.......................................................................................................................................... 6
1.7. Java Runtime Environment (JRE)...............................................................................................................................6
1.8. Product Support...........................................................................................................................................................6
Chapter 2. Installation Overview..........................................................................................................................................8
2.1. Before You Begin........................................................................................................................................................ 8
2.2. PGI Server and Network Installations.........................................................................................................................9
2.3. PGI Installations Preparation.....................................................................................................................................10
2.3.1. Linux Installations.............................................................................................................................................. 10
2.3.2. Windows.............................................................................................................................................................11
2.3.3. OS X.................................................................................................................................................................. 11
2.4. PGI CDK Installation Overview................................................................................................................................. 11
2.4.1. Cluster Configurations....................................................................................................................................... 11
2.4.2. Open Source Component Overview..................................................................................................................13
2.5. Further Considerations.............................................................................................................................................. 13
Chapter 3. Licensing........................................................................................................................................................... 15
3.1. Licensing Terminology............................................................................................................................................... 15
3.2. Licensing Keys.......................................................................................................................................................... 15
3.2.1. Licensing Key Options.......................................................................................................................................15
3.2.2. Licensing Key Capabilities.................................................................................................................................16
3.2.3. Licensing Key Comparisons.............................................................................................................................. 16
3.2.4. Licensing Key Dependencies............................................................................................................................ 17
3.3. PGI License Setup Tool............................................................................................................................................ 17
3.4. PGI Product Licensing...............................................................................................................................................17
3.5. PGI Licensing Considerations................................................................................................................................... 18
3.6. The FlexNet License Manager..................................................................................................................................19
3.7. License Support.........................................................................................................................................................19
Chapter 4. PGI Installations on Linux...............................................................................................................................20
4.1. Prepare to Install PGI Workstation or PGI Server on Linux..................................................................................... 20
4.2. Installation Steps for Linux........................................................................................................................................21
PGI Installation Guide
ii
4.3. End-user Environment Settings.................................................................................................................................29
4.3.1. PGI Workstation and PGI Server...................................................................................................................... 30
4.3.2. PGI CDK............................................................................................................................................................ 30
4.3.3. Open MPI access.............................................................................................................................................. 31
4.3.4. MVAPICH access...............................................................................................................................................31
Chapter 5. Installations on OS X.......................................................................................................................................32
5.1. Preparing to Install on Apple OS X.......................................................................................................................... 32
5.2. System Configuration to Enable Debugger ‘Attach’..................................................................................................34
5.3. Installation Steps for Apple OS X............................................................................................................................. 34
5.4. End-user Environment Settings on OS X................................................................................................................. 38
5.4.1. Use PGI Terminal Settings................................................................................................................................ 38
5.4.2. Initialize your Terminal Shell Manually.............................................................................................................. 38
5.4.3. Use MPICH........................................................................................................................................................ 39
Chapter 6. Installations on Microsoft Windows............................................................................................................... 40
6.1. Preparing to Install on Windows............................................................................................................................... 40
6.2. Installation Steps for Windows..................................................................................................................................41
6.3. Customizing the Command Window......................................................................................................................... 47
6.4. PGI Workstation Default Installation Directories....................................................................................................... 48
6.4.1. Default Installation Directories........................................................................................................................... 48
6.4.2. Tool Default Versions.........................................................................................................................................48
6.5. PGROUPD_LICENSE_FILE and FLEXLM_BATCH..................................................................................................48
6.5.1. PGROUPD_LICENSE_FILE.............................................................................................................................. 49
6.5.2. FLEXLM_BATCH................................................................................................................................................49
6.6. Windows Firewall and PGI Debugging..................................................................................................................... 49
6.6.1. Automatic Additions to Windows Firewall Exceptions List................................................................................ 49
6.7. Common Windows Installation Problems..................................................................................................................50
Chapter 7. Contact Information......................................................................................................................................... 52
PGI Installation Guide
iii
LIST OF FIGURES
Figure 1 PGI Installation Overview .......................................................................................................................................9
Figure 2 Welcome PGI Account Sample ........................................................................................................................... 25
Figure 3 OS X Installation Overview ..................................................................................................................................33
Figure 4 Welcome PGI Account Sample ........................................................................................................................... 36
Figure 5 PGI Welcome Screen .......................................................................................................................................... 43
Figure 6 Welcome PGI Account Sample ........................................................................................................................... 46
PGI Installation Guide
iv
LIST OF TABLES
Table 1 Processors Supported by PGI 2016 ....................................................................................................................... 4
Table 2 License Key Comparisons .....................................................................................................................................16
Table 3 Default Windows Installation Directories ............................................................................................................... 48
PGI Installation Guide
v
PGI Installation Guide
vi
Chapter 1.
INTRODUCTION
Welcome to Release 2016 of PGI Workstation™, PGI Server™, and PGI CDK®Cluster
Development Kit®, a set of compilers and development tools for 32–bit and 64–bit x86–
compatible processor–based workstations, servers, and clusters running versions of the Linux
operating system. PGI Workstation and PGI Server are also available on Apple OS X and
Microsoft Windows operating systems.
This installation information applies to all PGI products from The Portland Group.
1.1. Product Overview
PGI Workstation, PGI Server, and the PGI CDK include exactly the same PGI compilers and
tools software. The difference is the manner in which the license keys enable the software.
1.1.1. PGI Workstation and PGI Server Comparison
‣
‣
All PGI Workstation products include a node–locked single–user license, meaning one user
at a time can compile on the one system on which the PGI Workstation compilers and tools
are installed. The product and license server are on the same local machine.
PGI Server products are offered in configurations identical to PGI Workstation, but include
network floating multi–user licenses. This means that two 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 Server license keys are installed. There can be multiple
installations of the PGI Server 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. The license server manages seats sharing among compiler users.
1.1.2. PGI CDK Cluster Development Kit
A cluster is a collection of compatible computers connected by a network. The PGI CDK
supports parallel computation on clusters of 64–bit x86–compatible Intel or AMD processor–
based Linux workstations or servers interconnected by a TCP/IP–based network, such as Ethernet
or InfiniBand.
PGI Installation Guide
1
Introduction
Support for cluster programming does not extend to clusters combining 64–bit processor–based
Linux systems with 32–bit processor–based Linux systems.
Compilers and libraries can be installed on other platforms not in the user’s cluster, including other
clusters, as long as all platforms use a common floating license server.
The PGI CDK supports 64–bit x64 (Intel 64, AMD64) processor–based Linux systems, with
large array addressing in PGF77, PGF95, PGFORTRAN, PGC++, and PGCC. These systems can
utilize a 64–bit address space while retaining the ability to run legacy 32–bit x86 executables at
full speed.
1.2. Release Components
Release 2016 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.
PGPROF® OpenACC, CUDA, OpenMP, and multi-thread graphical profiler.
PGDBG® MPI, OpenMP, and multi-thread graphical debugger.
Open MPI libraries, version 1.10.1, for 64-bit Linux development environments with
support for NVIDIA GPUDirect; requires CUDA 7 or later. Note that 64-bit linux86-64 MPI
messages are limited to <2GB size each.
MPICH libraries, version 3.2, for 64-bit OS X development environments.
Microsoft HPC Pack 2012 MS-MPI Redistributable Pack (version 4.1) for 64-bit and 32-bit
development environments (Windows only).
BLAS and LAPACK library based on the customized OpenBLAS project source. This 64bit library is provided for Intel 64 or AMD CPU-based installations running Linux, OS X, or
Windows.
ScaLAPACK 2.0.2 linear algebra math library for distributed-memory systems for use with
MPICH, Open MPI, MVAPICH, and the PGI compilers on 64-bit Linux and OS X for Intel
64 or AMD64 CPU-based installations.
A UNIX-like shell environment for 32-bit and 64-bit Windows platforms.
FlexNet license utilities.
Documentation in man page format and online PDFs.
1.2.1. Additional Components for PGI CDK
The PGI CDK for Linux includes additional components available for download from the PGI
website, but not contained in the installation package:
‣
‣
MVAPICH2 MPI libraries, version 2.0, available for 64-bit development environments.
MPICH MPI libraries, version 3.2, available for 64-bit development environments.
PGI Installation Guide
2
Introduction
1.2.2. MPI Support
You can use PGI products to develop and debug MPI applications. The PGDBG® MPI debugger
included with PGI Workstation and PGI Server is limited to 16 local processes. The MPI
debugger included with the PGI CDK supports up to 64 or 256 remote processes, depending on
the purchased capabilities.
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 online glossary at
http://www.pgroup.com/support/definitions.htm
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™ designed to be binary compatible with 32-bit x86 processors,
and incorporating new 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 2016 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. Compilers in a 32–bit PGI installation
can produce 32–bit executables targeted to any 32–bit target, including 32–bit operating systems
and 64–bit operating systems (Linux, OS X, Windows).
Support for 32-bit development is deprecated in PGI 2016 and will no longer be available as of the PGI
2017 release. PGI 2017 will only be available for 64-bit operating systems and will not include the ability to
compile 32-bit applications for execution on either 32- or 64-bit operating systems.
PGI Installation Guide
3
Introduction
PGI products have the capability to generate binaries optimized for specific Intel or AMD
processors. The PGI 2016 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 2016
Brand
CPU
Target Processor
(-tp <target> [,target...])
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
Haswell
haswell
Ivy Bridge
ivybridge
Sandy Bridge
sandybridge
Core i7 - Nehalem
nehalem
Penryn
penryn
Pentium 4
p7
Generic
px
AMD
Intel
Generic
PGI Installation Guide
4
Introduction
The -tp flag interacts with the -m32 and -m64 flags to select a target processor and 32-bit
or 64-bit code. For example, specifying -tp shanghai -m32 compiles 32-bit code that is
optimized for the AMD shanghai processor.
Support for 32-bit development is deprecated in PGI 2016 and will no longer be available as of the PGI
2017 release. PGI 2017 will only be available for 64-bit operating systems and will not include the ability to
compile 32-bit applications for execution on either 32- or 64-bit operating systems.
1.5. Supported Operating Systems
PGI supports Linux, OS X and Windows operating systems.
Linux
Most Linux operating systems with GLIBC 2.5 and above:
‣
‣
‣
‣
‣
‣
CentOS 5+, including CentOS 7
Fedora 6+, including Fedora 23
RHEL 5+, including RHEL 7.2
SLES 11+, including SLES 12 SP 1
SuSE 11+, including openSuSE 13.2
Ubuntu 12.04+, including Ubuntu 15.10
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.
OS X
Supported versions are OS X versions 10.7 (Lion) and newer, including 10.11 (El Capitan).
Windows
‣
‣
‣
‣
‣
‣
Windows Server 2008 R2
Windows 7
Windows 8
Windows 8.1
Windows 10
Windows Server 2012
www.pgroup.com/support/install.htm 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.
PGI Installation Guide
5
Introduction
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
PGDBG 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. On 64–bit systems the tools use a 64-bit JRE; on 32–bit
systems they use a 32–bit JRE. The correct JRE is important because the tools make calls to
native code, which must be of compatible "bitness" to function properly.
The tools are compatible with Java 1.6 and later versions. The PGI 16.3 release includes the
JRE version 1.8 update 45. On Linux and OS X, 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 Subscription Service during the money-back guarantee
period.
The PGI Subscription Service provides support and other benefits including:
‣
Ongoing technical support by email. Support requests may be sent in a number of ways:
‣
‣
‣
By email to [email protected]
Faxed to +1-503-682-2637
By using the online support request form available at
www.pgroup.com/support/support_request.php
‣
Phone support is not currently available.
Release upgrades for licensed product(s) at no additional cost, except for any administrative
fee that may apply.
PGI Installation Guide
6
Introduction
‣
‣
‣
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 Service Subscription. Extensions are available in yearly increments.
Contact [email protected] if you would like information regarding the subscription service for
the PGI products you have purchased.
PGI Installation Guide
7
Chapter 2.
INSTALLATION OVERVIEW
This chapter provides an overview of the steps required to successfully install PGI Workstation,
PGI Server, or the PGI CDK. 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 Workstation, PGI Server or PGI CDK 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 OS X describes how to install
on an Apple OS X 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.
PGI Installation Guide
8
Installation Overview
Figure 1 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 Server and Network Installations
Linux
On Linux, PGI Server 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 OS X and Windows
On Apple OS X and Windows, PGI Server must be installed locally on each machine. A network
installation using a shared file system is not supported.
PGI Installation Guide
9
Installation Overview
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.
‣
‣
64–bit PGI installations require support for 64–bit executables in gcc which is only
available on 64–bit Linux systems.
32–bit PGI installations require support for 32–bit executables in gcc. These are
available on both 32–bit Linux systems and 64–bit Linux systems, though on 64–bit
Linux systems, 32–bit is not usually installed by default.
Any changes to your gcc compilers requires you to reinstall your PGI compilers.
To determine if 32–bit or 64–bit 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.
For 64–bit gcc support:
% 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
For 32–bit gcc support:
% gcc -m32 -o ./hello_32 ./hello.c ! create a 32-bit executable
% file ./hello_32 ! does the file exist, and is it 32-bit?
PGI Installation Guide
10
Installation Overview
Output should look similar to the following:
hello_32: ELF 32-bit LSB executable, Intel 80386, 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. Download the Windows SDK at www.pgroup.com/microsoft-sdk.
PGI's compilers leverage the latest 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.
Download and install this update here: support.microsoft.com/en-us/kb/2999226. 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. OS X
OS X 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. PGI CDK Installation Overview
The following sections contain the information needed for you to successfully prepare to install
the PGI CDK software.
Recall that a cluster is a collection of compatible computers connected by a network. The PGI
CDK software is installed on a working cluster. It is not the purpose of this product to create a
cluster nor to troubleshoot one. The PGI CDK release 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, the
PGI CDK includes a 64–bit set of Open MPI libraries. These libraries implement the MPI inter–
process communication standard.
Additional MPI libraries are available for PGI CDK from the PGI website at 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 Installation Guide
11
Installation Overview
The PGI CDK is always installed by users on the master node, and the compilers and tools are
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 PGI CDK open source components — MPICH, MVAPICH2 and/or Open MPI — are
best suited for CDK development. 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 Installation Guide
12
Installation Overview
PGI Installations on Linux describes how to install the PGI Fortran, C and C++ compilers and
tools on Linux using the installcdk 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 trial or permanent license keys.
2.4.2. Open Source Component Overview
The PGI Compiler User’s Guide describes basic usage of the open source components of the PGI
CDK, 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 The Portland Group. Support for these products is generally provided
by their respective user communities, which you can learn more about at the following URLs:
‣
‣
MPICH3 — www.mpich.org
MVAPICH2 — www.mvapich.cse.ohio-state.edu/overview/mvapich contains a wealth of
information, including online documentation, tutorials, FAQ files, patch distributions, and
information on how to submit bug reports to its developers.
To use the PGI CDK version of MVAPICH2, the prerequisite OpenFabrics (OFED) software must be
installed. For details on OFED, refer to www.openfabrics.org.
‣
‣
Open MPI — www.open-mpi.org is a source for Open MPI information about building and
using the library.
ScaLAPACK — www.netlib.org/scalapack contains FAQ files and current distributions of
ScaLAPACK, which is in the PGI CDK.
2.5. Further Considerations
There are a number of additional things you might consider prior to installation.
‣
A PGI Account
All users installing the compilers benefit by having an account at www.pgroup.com. Go to
www.pgroup.com/register to create an account.
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 all non-temporary licenses, as described in
Licensing.
‣
Downloading the proper package
When ready, you can download the proper package(s) at 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.
PGI Installation Guide
13
Installation Overview
‣
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 PGI Workstation 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.
PGI Installation Guide
14
Chapter 3.
LICENSING
The PGI compilers and tools are license-managed. 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 offers licenses for either x64+GPU or x64 only platforms. PGI Accelerator products, the
x64+GPU platform products, include support for the directive-based OpenACC programming
model, CUDA Fortran and PGI CUDA-x86. PGI Accelerator compilers are supported on all Intel
PGI Installation Guide
15
Licensing
and AMD x64 processor-based systems with CUDA-enabled NVIDIA GPUs running Linux, OS
X, or Windows.
There are four types of license key options: starter, trial, developer, and permanent.
Starter License Keys
When you first register for a PGI web account, your account activation email includes starter
license keys. Starter keys are valid for 30 days from the date the account activation email is
sent. Starter license keys are not FlexNet managed.
Trial License Keys
If you already have a PGI web account, you can use it to generate trial license keys. Trial
license keys are valid for 15 days from the date they are generated.
Developer License
Free PGI for OS X includes a permanent developer license that is not FlexNet managed.
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.
3.2.2. Licensing Key Capabilities
At the conclusion of the starter license key or trial 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 or trial license keys must be recompiled once either a developer or permanent license
is in place.
Executable files generated using developer licenses are restricted to running only on the same
system as they were compiled. Developer licenses may not be moved between machines.
Executable files generated using 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
Trial
Developer
Permanent
Node-locked
No
Yes
Yes
Yes
Limited duration
Yes - 30 days
Yes - 15 days
No
No
Limited functionality
Yes
Yes
Yes
No
PGI Installation Guide
16
Licensing
3.2.4. Licensing Key Dependencies
When using trial or 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 license keys do not have this dependency.
Important If you change the configuration of your system by adding or removing hardware, your license
keys may become invalid. Please contact [email protected] if you expect to reconfigure your system to
ensure that you do not temporarily lose the use of your PGI compilers and tools.
3.3. PGI License Setup Tool
PGI 2016 includes the PGI License Setup Tool to help automate your license retrieval and
installation process. You can use this tool to obtain both trial and permanent license keys.
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. PGI Product Licensing
PGI Workstation
PGI Workstation is node-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.
PGI Server
PGI Server supports multi-user, network floating licenses. Multiple users can use the PGI
compilers and tools simultaneously from multiple systems on a network when those systems have
a properly configured version of PGI Server installed. The number of seats purchased for the
license determines the limitation on the number of concurrent users.
The license server for PGI Server can run on either Linux or Windows.
PGI CDK
The PGI CDK supports multi-user, network floating licenses. Multiple users can use the PGI
compilers and tools concurrently from multiple systems on a network when those systems have
PGI Installation Guide
17
Licensing
a properly configured version of the PGI CDK installed. The number of seats purchased for the
license determines the limitation on the number of concurrent users.
We recommend that the license server run on the cluster master node.
3.5. 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
OS X, 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 Workstation licenses are limited to allow the compilers to work only on the machine
running the license service. This is a node-locked license.
PGI Server and PGI CDK licenses allow any machine that can communicate with the license
server in a timely manner (i.e. distance relative) to run the compilers. This is a floating
license.
The PGI CDK package 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 CDK floating license by having all of the master nodes
communicate with the license service. The PGI CDK license allows the PGDBG debugger
and PGPROF 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.
PGI Installation Guide
18
Licensing
‣
‣
‣
‣
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 OS X, 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 OS X, 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, OS X). If you're having
licensing problems, check this file for information.
3.6. 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 OS X, 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.7. License Support
All new PGI licenses include free PGI Subscription Service during the money-back guarantee
period. For more information about this service and how to extend it, refer to Product Support.
PGI Installation Guide
19
Chapter 4.
PGI INSTALLATIONS ON LINUX
This section describes how to install PGI Workstation, PGI Server, or PGI CDK in a generic
manner on a Linux system. It covers local and network installations and is applicable for
permanent or trial installations.
‣
‣
For installations of PGI compilers to create 32-bit executables on either 32-bit or 64-bit
Linux systems, a download file for 32-bit PGI compiler installation is provided.
For installations of 64-bit PGI compilers on 64-bit x86-64 systems, a download file for 64-bit
PGI compiler installation is provided.
The 32-bit and 64-bit compilers, tools, and supporting components have the same command
names, and the environment you target by default (linux86-64 or linux86) depends on the version
of the compiler that comes first in your $PATH settings.
4.1. Prepare to Install PGI Workstation or PGI Server on Linux
Preparation for installing PGI Workstation or PGI Server on Linux requires:
‣
‣
‣
‣
For 32-bit PGI compilers, support for compiling and linking 32-bit executables with gcc
must be in your $PATH. This is available on 32-bit and 64-bit Linux systems.
For 64-bit PGI compilers, support for compiling and linking 64-bit executables with gcc
must be in your $PATH. This is only supported on 64-bit Linux systems.
For PGI licensing to work properly, Linux Standard Base (lsb) must be installed on your
system.
For PGI CDK 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.
PGI Installation Guide
20
PGI Installations on Linux
‣
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. nonshared) 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:
‣
Download the PGI compilers at www.pgroup.com/support/downloads.php.
‣
To download you must either register or log in. Then, under the Target option, choose 64-bit
only or 32-bit only. If you need both packages, download them each separately.
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 platform requires up to 450 MB of free disk space, depending on the
number of packages installed.
‣ 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.
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 on the PGI website at www.pgroup.com/
login. 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.
PGI Installation Guide
21
PGI Installations on Linux
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. If you are installing both 32-bit and 64-bit compilers, you may install them in
either order.
For PGI CDK, after the compilers are installed, install the additional CDK components by
running the installcdk 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 PGI Server or PGI CDK, determine whether to perform a local
installation or a network installation.
Determine whether to install the optional components:
‣
‣
NVIDIA CUDA components
AMD OpenCL 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.
‣
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 Installation Guide
22
PGI Installations on Linux
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 PGDBG debugger and PGPROF 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.
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.
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.
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/16.3/bin $path)
setenv MANPATH "$MANPATH":/opt/pgi/linux86-64/16.3/man
setenv LM_LICENSE_FILE /opt/pgi/license.dat:"$LM_LICENSE_FILE"
In bash, sh, or ksh, use these commands:
$
$
$
$
export
export
export
export
PGI=/opt/pgi;
PATH=/opt/pgi/linux86-64/16.3/bin:$PATH;
MANPATH=$MANPATH:/opt/pgi/linux86-64/16.3/man;
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.
PGI Installation Guide
23
PGI Installations on Linux
In csh, use these commands:
%
%
%
%
setenv PGI /opt/pgi
set path=(/opt/pgi/linux86/16.3/bin $path)
setenv MANPATH "$MANPATH":/opt/pgi/linux86/16.3/man
setenv LM_LICENSE_FILE "$LM_LICENSE_FILE":/opt/pgi/license.dat
In bash, sh, or ksh, use these commands:
$
$
$
$
export
export
export
export
PGI=/opt/pgi;
PATH=/opt/pgi/linux86/16.3/bin:$PATH;
MANPATH=$MANPATH:/opt/pgi/linux86/16.3/man;
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 16.3.
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
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.
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.
All PGI compilers and tools are license-managed using FlexNet licensing. This system
requires that you possess a valid license for the licensed product. You get the license from the
PGI website, www.pgroup.com/login.
Other components, such as Open MPI, are open source products that are not license-managed.
To obtain license keys, you need the following information:
‣
An account on the PGI website.
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.
PGI Installation Guide
24
PGI Installations on Linux
‣
‣
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 [email protected] .
‣ If you don’t have an account, you can create one at: 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.
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.
% lmutil lmhostid -hostname
Generate License Keys
Once you have logged on at www.pgroup.com/login using your registered PGI web-user email
and password, you see a screen similar to the following:
Figure 2 Welcome PGI Account Sample
Generate a Permanent License Key
1. Click Create permanent keys.
2. Click the PIN associated with the product for which you wish to generate license keys. If
you don't see any PINs listed, you first need to tie one to your account:
a. Obtain your PIN code from your original PGI order confirmation email, in the
section labeled: "SHARING ADMINISTRATION" or contact [email protected].
b. Click the link: Tie a PIN to this account.
PGI Installation Guide
25
PGI Installations on Linux
c. Enter the 16-digit PIN code and follow the instructions provided.
3. Click License keys to generate the keys.
Generate a Trial License Key
1. Click Create trial keys.
2. Accept the terms of the agreement.
3. Enter any one of the FlexNet hostids detected, exactly as it appears in the message that is
displayed during installation or when you issue the command: lmutil lmhostid
4. Click the Generate License keys button.
Install License Keys
Once you have generated your trial or permanent license keys, copy and paste them 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
Workstation installation:
SERVER <hostname> 0123456789ab 27000
DAEMON pgroupd
PACKAGE PGI2015-<PGI_PIN> pgroupd <subscription end date>
<...>
6167 7015 3F05 9C37 2315 ACDF 1B73 DAA9 FBAE"
A13AB920D570 \
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.
For example, if your subscription date for your PGI PIN (Product Identification Number)
is August 1, 2015, then the date in your file is 2015.0801. For information on how to
renew your subscription, refer to Product Support.
The six digits immediately following the VENDOR_STRING = in the feature line
component represent the PIN for this installation.
You have a similar unique PIN for your installation.
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 used the installation script to do this or if you are evaluating PGI software with trial
license keys, you do not need to perform this step and can proceed to Step 7.
PGI Installation Guide
26
PGI Installations on Linux
Installations in a directory other than the default /opt/pgi
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/16.3/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/16.3/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/16.3/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.
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/16.3/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
PGI Installation Guide
27
PGI Installations on Linux
To start the license server and pgroupd license daemon each time your system is booted:
1. Log in as root.
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/16.3/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/16.3/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 2016 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 2016 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>/16.3/bin/lmgrd
## Command to stop lmgrd
#Commented out previous path to 13.8:
#LMUTIL=$PGI/<target>/13.8/bin/lmutil
LMUTIL=$PGI/<target>/16.3/bin/lmutil
7. Review documentation.
PGI Installation Guide
28
PGI Installations on Linux
All documentation for PGI compilers and tools is available online at http://www.pgroup.com/
resources/docs.htm
8. Complete network installation tasks.
Skip this step if you are not installing PGI Server 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/16.3 is the
common local directory, then run the following commands on each system on the network.
/opt/pgi/linux86/16.3/bin/makelocalrc -x /opt/pgi/linux86/16.3 \
-net /usr/pgi/shared/16.3
/opt/pgi/linux86-64/16.3/bin/makelocalrc -x /opt/pgi/linux86-64/16.3 \
-net /usr/pgi/shared/16.3
These commands create a system-dependent file localrc.machinename in both of these
directories: /opt/pgi/linux86/16.3/bin and /opt/pgi/linux86-64/16.3/
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/16.3/lib
/usr/pgi/shared/16.3/liblf
/usr/pgi/shared/16.3/lib64
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, send email to [email protected].
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
PGI Installation Guide
29
PGI Installations on Linux
4.3.1. PGI Workstation and PGI Server
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.
Each user must issue the following sequence of commands to initialize the shell environment before using
the PGI compilers and tools.
64-bit as default
To make the 64-bit PGI compilers and tools the default:
In csh, use these commands:
%
%
%
%
setenv PGI /opt/pgi
setenv MANPATH "$MANPATH":$PGI/linux86-64/16.3/man
setenv LM_LICENSE_FILE $PGI/license.dat
set path = ($PGI/linux86-64/16.3/bin $path)
Once the 64-bit compilers are the defaults, you can make the Open MPI commands and Open
MPI man pages accessible using these csh commands:
% set path = ($PGI/linux86-64/16.3/mpi/openmpi/bin $path)
% setenv MANPATH "$MANPATH":$PGI/linux86-64/16.3/mpi/openmpi/man
In bash, sh, or ksh, use these commands:
$
$
$
$
PGI=/opt/pgi; export PGI
MANPATH=$MANPATH:$PGI/linux86-64/16.3/man; export MANPATH
LM_LICENSE_FILE=$PGI/license.dat; export LM_LICENSE_FILE
PATH=$PGI/linux86-64/16.3/bin:$PATH; export PATH
Once the 64-bit compilers are the defaults, you can make the Open MPI commands and Open
MPI man pages accessible using these commands.
$ export PATH=$PGI/linux86-64/16.3/mpi/openmpi/bin:$PATH
$ export MANPATH=$MANPATH:$PGI/linux86-64/16.3/mpi/openmpi/man
32-bit as default
To make the 32-bit PGI compilers and tools the default:
In csh, use these commands:
%
%
%
%
setenv PGI /opt/pgi
setenv MANPATH "$MANPATH":$PGI/linux86/16.3/man
setenv LM_LICENSE_FILE $PGI/license.dat
set path = ($PGI/linux86/16.3/bin $path)
4.3.2. PGI CDK
With either the trial or permanent license keys in place, choose the applicable commands from the
following lists and execute them to make the products you have purchased accessible.
Important
Each user must issue the appropriate following sequence of commands to initialize their shell environment
before using the PGI compilers and tools.
PGI Installation Guide
30
PGI Installations on Linux
For the following path settings, the installation is in the default directory: /opt/pgi
Set Environment Variables for Licensing
Execute the following commands to initialize your environment for use of FlexNet licensing.
In csh, use these commands:
% setenv PGI /opt/pgi
% setenv LM_LICENSE_FILE "$LM_LICENSE_FILE":/opt/pgi/license.dat
In bash, sh or ksh, use these commands:
$ PGI=/opt/pgi; export PGI
$ LM_LICENSE_FILE=$LM_LICENSE_FILE:$PGI/license.dat; export LM_LICENSE_FILE
Set End-User PATH Variables
This section describes the commands required to access Open MPI as well as its associated man
pages.
If you install only the linux86 versions of the compilers or wish to target linux86 as the default, use a setup
similar to the x64 linux86-64 one shown here, substituting linux86 in place of linux86-64 in all path settings.
4.3.3. Open MPI access
To access Open MPI and the Open MPI man pages for x64 linux86-64, execute these commands:
In csh, use these commands:
% set path = (/opt/pgi/linux86-64/16.3/bin \
/opt/pgi/linux86-64/16.3/mpi/openmpi/bin $path)
% setenv MANPATH "$MANPATH":/opt/pgi/linux86-64/16.3/mpi/openmpi/man
In bash, sh or ksh, use these commands:
$ export PATH=/opt/pgi/linux86-64/16.3/bin: \
/opt/pgi/linux86-64/16.3/mpi/openmpi/bin:$PATH
$ export MANPATH=$MANPATH:/opt/pgi/linux86-64/16.3/mpi/openmpi/man
4.3.4. MVAPICH access
To access MVAPICH2 and the MVAPICH2 man pages for x64 linux86-64, execute these
commands:
In csh, use these commands:
% set path = (/opt/pgi/linux86-64/16.3/bin
/opt/pgi/linux86-64/16.3/mpi/mvapich/bin $path)
% setenv MANPATH "$MANPATH":/opt/pgi/linux86-64/16.3/mpi/mvapich/man
In bash, sh or ksh, use these commands:
$ export PATH=/opt/pgi/linux86-64/16.3/bin:
/opt/pgi/linux86-64/16.3/mpi/mvapich/bin:$PATH
$ export MANPATH=$MANPATH:/opt/pgi/linux86-64/16.3/mpi/mvapich/man
PGI Installation Guide
31
Chapter 5.
INSTALLATIONS ON OS X
This section describes how to install PGI software on an Apple computer running Apple OS X. It
covers local installs, and is applicable to permanent or trial installations.
PGI products for Apple OS X are supported on Intel processor-based Macintosh computers running OS
X version 10.6.0 or greater with Apple Xcode 3.2 through 7.x installed. Xcode is available from http://
developer.apple.com.
The default installation base directory is /opt/pgi.
‣
‣
For installations on 32-bit x86 systems, the PGI installation process installs only the osx86
versions of the PGI compilers and tools.
For installations on 64-bit x64 systems running an osx86-64 execution and development
environment, the PGI installation process installs the osx86-64 version of the PGI compilers
and tools.
The 32-bit and 64-bit compilers, tools, and supporting components have the same command
names, and the environment you target by default, either osx86-64 or osx86, depends on the
version of the compiler that comes first in your path settings.
5.1. Preparing to Install on Apple OS X
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 3.2 or greater (through 7.x) is installed.
‣
‣
If you know how to run Xcode, start Xcode and click About Xcode to verify the version
is 3.2 or greater (through 7.x).
If you do not know how to run Xcode or are uncertain if it is installed on your system,
do the following:
PGI Installation Guide
32
Installations on OS X
1.
2.
3.
4.
5.
From the Apple Menu, select About This Mac.
Click More Info.
Select System profiler | Software | Applications.
Scroll through the alphabetical list and verify Xcode is in it.
Verify the version is 3.2 or greater.
PGI software for OS X 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 PGDBG debugger and PGPROF profiler have their own GUIs.
In preparation for installing PGI software on OS X, first review Figure 3, an overview of the
installation process.
Figure 3 OS X Installation Overview
PGI Installation Guide
33
Installations on OS X
5.2. System Configuration to Enable Debugger ‘Attach’
The PGDBG debugger can debug programs that are launched by the debugger, either by
specifying the program on the PGDBG command line, using the debug or load commands, or
by specifying a program in the Connections tab of the PGDBG GUI.
OS X security features prevent PGDBG from attaching to a running program unless some
configuration is performed. Users who need to attach PGDBG 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 Apple OS X
Once you have prepared for the installation, follow these instructions to install the software:
1. Access the installation package.
Download the software from www.pgroup.com or another electronic distribution site. If it
does not mount automatically, open this file to mount it.
2. Install the software.
Double-click the PGI Workstation 16.3.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 3.2 or greater (through 7.x) and gcc.
2. Select the drive and, if you want, also select an installation directory other than 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 2016 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 2016.
For more information on configuring to make either 32-bit or 64-bit compilers the default,
refer to End-user Environment Settings.
4. Verify the release number of the installed software. It should say 16.3.
PGI Installation Guide
34
Installations on OS X
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
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.
All PGI compilers and tools are license-managed using FlexNet licensing. This system
requires that you possess a valid license for the licensed product. You get the license from the
PGI website, www.pgroup.com/login.
Other components, such as Open MPI, are open source products that are not license-managed.
To obtain license keys, you need the following information:
‣
An account on the PGI website.
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 [email protected] .
‣ If you don’t have an account, you can create one at: 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.
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
PGI Installation Guide
35
Installations on OS X
are configured. Then, to reduce potential license problems, choose the hostid that occurs in all your
environments.
% lmutil lmhostid -hostname
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 at www.pgroup.com/login using your registered PGI web-user email
and password, you see a screen similar to the following:
Figure 4 Welcome PGI Account Sample
Generate a Permanent License Key
1. Click Create permanent keys.
2. Click the PIN associated with the product for which you wish to generate license keys. If
you don't see any PINs listed, you first need to tie one to your account:
a. Obtain your PIN code from your original PGI order confirmation email, in the
section labeled: "SHARING ADMINISTRATION" or contact [email protected].
b. Click the link: Tie a PIN to this account.
c. Enter the 16-digit PIN code and follow the instructions provided.
3. Click License keys to generate the keys.
Generate a Trial License Key
1. Click Create trial keys.
2. Accept the terms of the agreement.
3. Enter any one of the FlexNet hostids detected, exactly as it appears in the message that is
displayed during installation or when you issue the command: lmutil lmhostid
4. Click the Generate License keys button.
Install License Keys
Once you have generated your starter, trial or permanent license keys, copy and paste them
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.
PGI Installation Guide
36
Installations on OS X
For example, if you have purchased PGI Workstation for OS X and generated a permanent
licence key as previously described, the license.dat file should look similar to the
following:
SERVER <hostname> 0123456789ab 27000
DAEMON pgroupd
PACKAGE PGI2015-<PGI_PIN> pgroupd <subscription end date>
<...>
6167 7015 3F05 9C37 2315 ACDF 1B73 DAA9 FBAE"
A13AB920D570 \
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.
For example, if your subscription date for your PGI PIN (Product Identification Number)
is August 1, 2015, then the date in your file is 2015.0801. For information on how to
renew your subscription, refer to Product Support.
The six digits immediately following the VENDOR_STRING = in the feature line
component represent the PIN for this installation.
You have a similar unique PIN for your installation.
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 evaluating PGI Workstation with starter or trial keys, 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:
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. 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
PGI Installation Guide
37
Installations on OS X
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, send email to [email protected].
7. Review documentation.
The documentation is in PDF format and located online at http://www.pgroup.com/resources/
docs.htm
5.4. End-user Environment Settings on OS X
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 doubleclicking the PGI2016.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 | PGI2016 or New Tab | PGI2016. 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, for either 32-bit or 64-bit environments, 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 32-bit compilers the default
Launch the Terminal application located in the Applications | Utilities folder and
enter the following commands to make the 32-bit compilers the default.
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/16.3/bin:$PATH; export PATH
PGI Installation Guide
38
Installations on OS X
In csh, use these commands:
% setenv PGI /opt/pgi
% setenv LM_LICENSE_FILE $PGI/license.dat
% set path = ($PGI/osx86/16.3/bin $path)
Make 64-bit compilers the default
Launch the Terminal application located in the Applications | Utilities folder and
enter the following commands to make the 64-bit PGI compilers and tools the default.
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/16.3/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/16.3/bin $path)
5.4.3. Use MPICH
To use the version of MPICH that comes with PGI Workstation, use these commands:
For 32-bit compilers:
In bash, sh, or ksh, use these commands:
$ PATH=$PGI/osx86/2016/mpi/mpich/bin:$PATH
$ export PATH
In csh, use this command:
% set path = ($PGI/osx86/2016/mpi/mpich/bin $path)
For 64-bit compilers:
In bash, sh, or ksh, use these commands:
$ PATH=$PGI/osx86-64/2016/mpi/mpich/bin:$PATH
$ export PATH
In csh, use this command:
% set path = ($PGI/osx86-64/2016/mpi/mpich/bin $path)
PGI Installation Guide
39
Chapter 6.
INSTALLATIONS ON MICROSOFT WINDOWS
This section describes how to install PGI Workstation on a system running a Microsoft Windows
operating system. These instructions are valid for both 64-bit and 32-bit platforms, though
supported platforms vary by product. Further, this installation information is applicable to both
permanent and trial installations.
For installations on 64-bit x64 systems running a 64-bit operating system, the PGI installer
installs the 64-bit and 32-bit versions of the PGI compilers and tools. For installations on 32-bit
x86 systems, the PGI installer installs only the 32-bit versions of the PGI compilers and tools.
6.1. Preparing to Install on Windows
Prerequisite: Microsoft Windows SDK
The Microsoft Windows Software Development Kit (SDK) is a prerequisite for all Windows
installs. Download the Windows SDK at www.pgroup.com/microsoft-sdk.
Prerequisite: Microsoft Update for Universal C Runtime
PGI's compilers leverage the latest 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.
Download and install this update here: support.microsoft.com/en-us/kb/2999226. 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.
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.
PGI Installation Guide
40
Installations on Microsoft Windows
6.2. Installation Steps for Windows
Download the software from www.pgroup.com or another electronic distribution site. Select the
install package appropriate for your OS.
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.
The installation executables are:
pgiws32-163.exe
32-bit Windows 2008r2/7/8/8.1/10/2012
pgiws64-163.exe
64-bit Windows 2008r2/7/8/8.1/10/2012
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. 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 Workstation
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. It prompts you for your PGI username and password as
well as the type of license you wish to install, such as a trial license or a permanent license.
The tool also informs you of any problems it experiences with installation and provides
instructions on how to proceed.
If the PGI Licensing Setup tool reports a successful license installation, then skip to step 7.
3. Make PGI products accessible and prepare for licensing.
PGI Installation Guide
41
Installations on Microsoft Windows
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 Workstation desktop icon.
4. Verify release number.
Verify the release number of the products you have installed. Open PGI Workstation 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
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.
5. Generate and install license keys.
All of the PGI compilers and tools are license-managed and require installation of license keys
to make the PGI software operational.
To obtain license keys, you need the following information:
‣
An account on the PGI website.
You probably created this account when you downloaded the PGI software.
‣
‣
‣
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 [email protected] .
If you don’t have an account, you can create one at: 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.
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.
% lmutil lmhostid -hostname
After you have installed the PGI software, you can obtain your FlexNet hostid by
double-left-clicking on the PGI Workstation desktop icon to open a PGI Workstation
command window, and typing these commands:
PGI$
PGI$
cd $PGI
cat license.info
You should see information similar to the following:
PGI Installation Guide
42
Installations on Microsoft Windows
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: 2016
You can also obtain evaluation license keys by logging in at www.pgroup.com/login with your
existing PGI user account or by creating a new account if you have not previously registered.
Generate License Keys
Log in to your PGI web account at www.pgroup.com/login. You should see a screen similar to
the following:
Figure 5 PGI Welcome Screen
To generate permanent license keys:
1. Click Create permanent keys.
2. Click the PIN associated with the product for which you wish to generate license keys. If
you don’t see any PINs listed, you first need to tie one to your account.
a. Obtain your PIN code from your original PGI order confirmation email, in the
section labeled: ‘SHARING ADMINISTRATION’ or contact [email protected].
b. Click the link: Tie a PIN to this account.
c. Enter the 16-digit PIN code and follow the instructions provided.
3. Click License keys to generate the keys.
To generate trial license keys:
1. Click Create trial keys.
2. Accept the terms of the agreement.
3. Enter the hostid exactly as it appears in the message that is displayed during installation
or when you issue the command:
PGI$
PGI$
cd $PGI
cat license.info
4. Click the Generate license key button.
Install License Keys
Once you have generated your trial or permanent license keys, cut and paste them into your
license.dat file. In a typical configuration, where C:\ is the system drive and you
PGI Installation Guide
43
Installations on Microsoft Windows
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.
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.
While you may combine a license from PGI with other FlexNet-based licenses from another vendors,
only one PGI license per license server is allowed.
6. Start the PGI license server.
If you are evaluating a PGI product using trial or starter keys, 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.
The PGI License Server service starts automatically on system reboot, provided that the
license.dat file contains valid keys.
7. Get a license.
All PGI compilers and tools are license-managed using FlexNet licensing. This system
requires that you possess a valid license for the licensed product. You get the license from the
PGI website, www.pgroup.com/login.
Other components, such as Open MPI, are open source products that are not license-managed.
To obtain license keys, you need the following information:
PGI Installation Guide
44
Installations on Microsoft Windows
‣
An account on the PGI website.
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 [email protected] .
‣ If you don’t have an account, you can create one at: 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.
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.
% lmutil lmhostid -hostname
After you have installed the PGI software, you can obtain your FlexNet hostid by double-leftclicking on the PGI Workstation desktop icon to open a PGI Workstation command window,
and typing these commands:
PGI$
PGI$
cd $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: 2016
You can also obtain evaluation license keys by logging in at www.pgroup.com/login with your
existing PGI user account or by creating a new account if you have not previously registered.
Generate License Keys
Once you have logged on at www.pgroup.com/login using your registered PGI web-user email
and password, you see a screen similar to the following:
PGI Installation Guide
45
Installations on Microsoft Windows
Figure 6 Welcome PGI Account Sample
Generate a Permanent License Key
1. Click Create permanent keys.
2. Click the PIN associated with the product for which you wish to generate license keys. If
you don't see any PINs listed, you first need to tie one to your account:
a. Obtain your PIN code from your original PGI order confirmation email, in the
section labeled: "SHARING ADMINISTRATION" or contact [email protected].
b. Click the link: Tie a PIN to this account.
c. Enter the 16-digit PIN code and follow the instructions provided.
3. Click License keys to generate the keys.
Generate a Trial License Key
1. Click Create trial keys.
2. Accept the terms of the agreement.
3. Enter any one of the FlexNet hostids detected, exactly as it appears in the message that is
displayed during installation or when you issue the command: lmutil lmhostid
4. Click the Generate License keys button.
8. File Your License Key.
Once you have generated your starter, trial or permanent license keys, you must store it with
Administrator privileges in the license file on your system, a file called license.dat. In a
typical installation configuration, where C: is the system drive, and you installed the software
using the default location, put the license in this file:
C:\Program Files\PGI\license.dat
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.
‣
If you have not previously received license keys from PGI and the license.dat file
exists, replace the contents of the license.dat file created during installation with the
license keys you generated using the preceding steps. Otherwise, you must create the file.
PGI Installation Guide
46
Installations on Microsoft Windows
‣
‣
‣
If the license keys in the file are for a previous release of the same product, overwrite the
keys.
If your license.dat file already exists and contains PGI license keys, then append the
PGI keys to the keys already in this file.
If you have not previously received a license from PGI, you must create this file.
While you may combine a license from PGI with other FlexNet-based license from other vendors, only
one PGI license per license server is allowed.
9. Start the PGI License Service.
The software installation creates a Windows Service called PGI License Service. The actions
related to this service depend on the type of license you are using:
‣
‣
Trial or starter — If you have obtained a trial or starter license, then no action is
required.
Permanent — If you have obtained a permanent license, the FLEX license system
requires that a license server be running. Thus you must now start the PGI License Server.
As soon as a valid license.dat file is in place, you can start the PGI License Server.
1. Open the Services dialog from the Control Panel: Control Panel | Administrative Tools |
Services
2. Scroll through the list and 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.
The PGI License Server service starts automatically on system reboot provided that the
license.dat file contains valid keys.
10.Review documentation.
You can view the online documentation by pointing your web browser to the following URL:
www.pgroup.com/resources/docs.htm
Tip You may want to bookmark this location for easy future reference to the online manuals.
11.Customize PGI Workstation
Optionally, you can customize the setup as described in Customizing the Command Window
and PGI Workstation Default Installation Directories below.
6.3. Customizing the Command Window
By default, when you double-click on the PGI Workstation desktop icon, a standard blackbackground command window appears on your screen. This window is pre-initialized with
PGI Installation Guide
47
Installations on Microsoft Windows
environment and path settings for use of the PGI Workstation 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 Workstation command window.
To customize your window, right-click the PGI Workstation desktop icon, and select “Properties”
from the pop-up menu. In the PGI Workstation Properties dialog box, select the tabs for the
features you want to customize, and make the desired modifications.
6.4. PGI Workstation 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
Platform
or tool
32-bit
64-bit
Default Installation Directory
%SYSTEMDRIVE%\Program Files\PGI
%SYSTEMDRIVE%\Program Files\PGI
%SYSTEMDRIVE%\Program Files (x86)\PGI
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:
Cygwin FAQ: http://cygwin.com/faq.html
Cygwin Users Guide: http://cygwin.com/cygwin-ug-net.html
Cygwin mailing lists and archives: http://cygwin.com/lists.html
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
PGI Installation Guide
48
Installations on Microsoft Windows
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 2016 (32-bit)
PGI Debugger 2016 (64-bit) - not added to the Exceptions list on 32-bit systems.
PGI Installation Guide
49
Installations on Microsoft Windows
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 using PGDBG to Debug
If PGDBG is not listed in the Exceptions list and Windows Firewall is enabled when you use
PGDBG 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.
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.
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.
PGI Installation Guide
50
Installations on Microsoft Windows
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, send email to [email protected].
PGI Installation Guide
51
Chapter 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:
Fax: +1-503-682-2637
Sales: [email protected]
Support: [email protected]
WWW: http://www.pgroup.com
The PGI User Forum is monitored by members of the PGI engineering and support teams as
well as other PGI customers. The forum newsgroups may contain answers to commonly asked
questions. Log in to the PGI website to access the forum:
http://www.pgroup.com/userforum/index.php
Many questions and problems can be resolved by following instructions and the information
available at our frequently asked questions (FAQ) site:
http://www.pgroup.com/support/faq.htm
All technical support is by email or submissions using an online form at:
http://www.pgroup.com/support
Phone support is not currently available.
PGI documentation is available at http://www.pgroup.com/resources/docs.htm.
PGI Installation Guide
52
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
PGI Workstation, PGI Server, PGI Accelerator, PGF95, PGF90, PGFORTRAN, and PGI Unified
Binary are trademarks; and PGI, PGHPF, PGF77, PGCC, PGC++, PGI Visual Fortran, PVF, PGI CDK,
Cluster Development Kit, PGPROF, PGDBG, and The Portland Group are 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.
Copyright
© 2013-2016 NVIDIA Corporation. All rights reserved.
">