Home

PMIx Reference RunTime Environment (PRRTE) (Pronounced: purr-tay)

===========================================================================

PRRTE is the PMIx Reference Run Time Environment - a runtime environment containing the reference implementation and capable of operating within a host environment. PRRTE provides an easy way of exploring PMIx capabilities and testing PMIx-based applications outside of a PMIx-enabled environment by providing a “shim” between the application and the host environment that includes full support for the PMIx Standard. The intent of PRRTE is not to replace any existing production environment, but rather to enable developers to work on systems that do not yet feature a PMIx-enabled host environment or one that lacks a PMIx feature of interest. Instructions for downloading, installing, and using PRRTE are available on the community’s web site here

NOTE: The project is formally referred to in documentation by "PRRTE", and the GitHub repository is "prrte". However, we have found that most users do not like typing the two consecutive "r"s in the name. Hence, all of the internal API symbols, environment variables, MCA frameworks, and CLI executables all use the abbreviated "prte" (one "r", not two) for convenience.

===========================================================================

When submitting questions and problems, be sure to include as much extra information as possible.

 https://github.com/openpmix/prrte

The best way to report bugs, send comments, or ask questions is to post them on the PRRTE GitHub issue tracker:

 https://github.com/openpmix/prrte/issues

Thanks for your time.

===========================================================================

General notes

• Systems that have been tested are:

  • Linux (various flavors/distros), 32 bit, with gcc
  • Linux (various flavors/distros), 64 bit (x86), with gcc, Intel, and Portland (*)
  • OS X (10.7 and above), 32 and 64 bit (x86_64), with gcc (*)

• PRRTE has taken some steps towards Reproducible Builds (https://reproducible-builds.org/). Specifically, PRRTE's "configure" and "make" process, by default, records the build date and some system-specific information such as the hostname where PRRTE was built and the username who built it. If you desire a Reproducible Build, set the $SOURCE_DATE_EPOCH, $USER and $HOSTNAME environment variables before invoking "configure" and "make", and PRRTE will use those values instead of invoking "whoami" and/or "hostname", respectively. See https://reproducible-builds.org/docs/source-date-epoch/ for information on the expected format and content of the $SOURCE_DATE_EPOCH variable.

===========================================================================

Quick start

In many cases, PRRTE can be built and installed by simply indicating the installation directory on the command line:

$ tar xf prrte-.tar.bz2 $ cd prrte- $ ./configure --prefix= |& tee config.out ...lots of output... $ make -j 8 |& tee make.out ...lots of output... $ make install |& tee install.out ...lots of output...

Note that there are many, many configuration options to the "./configure" step. Some of them may be needed for your particular environmnet; see below for desciptions of the options available.

If your installation prefix path is not writable by a regular user, you may need to use sudo or su to run the "make install" step. For example:

$ sudo make install |& tee install.out [sudo] password for jsquyres: ...lots of output...

Finally, note that VPATH builds are fully supported. For example:

$ tar xf prrte-.tar.bz2 $ cd prrte- $ mkdir build $ cd build $ ../configure --prefix= |& tee config.out ...etc.

===========================================================================

Make today a PRRTE day!