Binary packages for Linux ( deb and rpm formats), Mac OS X, Solaris and Windows are made available by the PCP development team.  The latest version can always be found in the download section of the PCP project web pages.  Its also worth noting that many Linux distributions now ship PCP - these include Debian, Fedora, Slackware, SuSE and Ubuntu.

PCP GUI runs natively on Mac OS X, X11 (Linux/Unix) and Windows, and binary packages for these platforms are available in the same location.  The installation instructions for each differ significantly - below we discuss each in turn, and finally cover building the tools from source.

The typical PCP installation is conceptually divided into two major components - collectors and monitors .  There are usually multiple systems of each type in any given deployment.

For server-focussed systems (Linux in particular) PCP is literally divided into multiple packages along these lines, with separate PCP and PCP GUI packages (primarily due to dependencies on graphical libraries which are unlikely to be installed on a Linux server).  On the other platforms, like Mac OS X and Windows, this is less of an issue and so a single PCP package is shipped which covers both needs.

PCP GUI has a runtime dependency on the Qt4 shared libraries.  These are usually available from a package named qt4 .  Versions before Qt4.4 of the Qt libraries will not work .

Linux using rpm format (Fedora, RHEL, SuSE)

If using packages from your distribution , in a command shell enter:

# yum install pcp pcp-gui

If using packages downloaded from , in a command shell enter:

# rpm -Uvh *pcp*.rpm

Linux using deb format (Debian, Ubuntu)

If using packages from your distribution , in a command shell enter:

# apt-get install pcp pcp-gui

If using packages downloaded from , in a command shell enter:

# apt-get install ./*pcp*.deb

Mac OS X Installation

After downloading the dmg file for your platform, double-click on the PCP dmg icon, and follow the installation instructions presented by the Installer.

Solaris Installation

After downloading (and gunzip'ing) the binary package, to perform a fresh install:

# pkgadd -d pcp-X.Y.Z
  Say 'y' to all the questions
# svcadm enable pmcd

Or to update to a newer version:

# pkgrm pcp-X.Y.OLD
# pkgadd -d pcp X.Y.Z
# svcadm enable pmcd

Windows Installation

After downloading the PCP Glider msi file, right-click on the command prompt icon, select Run As Administrator , and enter:

# msiexec /i pcp-glider-*.msi
# cd C:\Glider\scripts
# postinst.bat

Before upgrading or removing PCP Glider, run:

# cd C:\Glider\scripts
# prerm.bat

The command line utilities can now be accessed from a Windows shell or the provided (POSIX) shell.  The graphical tools can be accessed via the Windows Start menu.

Building from source

The best way to build PCP is to use the git source code management (SCM) tools. This SCM is freely available and runs natively on many different platforms.

First, get the current version of the source code:

$ git clone

Then build and install:

$ cd pcp
$ ./configure --prefix=/usr --sysconfdir=/etc --localstatedir=/var
$ make
# make install

When building from source, you'll need to ensure you have the following tools and libraries installed: a C compiler (for core PCP), a C++ compiler (for PCP GUI), autoconf , lex , yacc , and the Qt4 development tools (including qmake ), libraries and headers.  On Mac OS X, the Apple Xcode development environment is also required, as it is used by the Qt application build process. Inkscape - a Scalable Vector Graphics (SVG) editor - can be used to modify the icons, but is not required during the build process.

If you encounter difficulties building PCP, consult the contacts page which contains contact information for people who can provide additional assistance.