New Cray package provides more integrated programming environment

by Tom Parker

Introduction

Cray Research is now packaging the compilers, libraries (CrayLibs), and performance tools (CrayTools) into a "programming environment" (PrgEnv). The new package provides a more integrated environment and simplifies testing of new versions. The PrgEnv is located in /opt/ctl (rather than scattered in /bin, /usr/bin, /lib, or /usr/lib).

What does this mean to you?

Using PrgEnv under UNICOS 8 (currently on shavano, paiute, antero, and aztec): Using PrgEnv under UNICOS 8 is optional but strongly recommended. It is optional because older versions of the compilers, libraries, and performance tools are still available without the use of PrgEnv. However, we recommend using PrgEnv under UNICOS 8 because you will get the latest and greatest versions of the software and because using PrgEnv will eventually be required (starting with UNICOS 9).
Using PrgEnv under UNICOS 9 (currently on echo and st-elmo): You must use PrgEnv under UNICOS 9 to use the compilers, libraries, and performance tools.
Initializing: To use the PrgEnv, you must initialize it in your .cshrc or .profile. See "Initializing the PrgEnv," below, for details.
Testing software:The PrgEnv makes it easier to test new versions of software. See "Maintaining the PrgEnv," below.

Major components of PrgEnv

Compilers:
- CC (c++)
CrayLibs:
- Application libraries:
  - Libraries: libf, libu
  - Man page: man intro_applibs
  - Manual: Application Programmer's Library Reference Manual, SR- 2165
- Math library routines:
  - Libraries: libm, libmv2
  - Man pages: (see man pages for individual routines)
  - Manual: Math Library Reference Manual, SR-2138
- Scientific library routines:
  - Library: libsci
  - Man page: man intro_libsci
  - Manual: Scientific Libraries Reference Manual, SR-2081.
CrayTools:
- totalview/debugview
- viewtools (flowview, jumpview/jt perfview, procview, profview/prof)
- xbrowse
- xhelp

Initializing the PrgEnv

To use the PrgEnv, you must first initialize it. This is done with the "module" interface. This interface does the necessary setting up of paths, manpaths, and environment variables.
csh/tcsh users should put these lines in their .cshrc file:
   # Initialize modules
      source /opt/modules/modules/init/csh
      module load modules PrgEnv
ksh/sh users should put these lines in their .profile file:
   # Initialize modules
      . /opt/modules/modules/init/ksh
      module load modules PrgEnv
Important notes

The above statements should follow all other path setting statements.

csh users should note that because their .login file is executed after .cshrc, they will also need to move any path or manpath code from .login to .cshrc.

Maintaining the PrgEnv

If you wish to see which levels of compilers, Craylibs, and Craytools are currently loaded, type module list. For example:
```
 % module list
    Currently Loaded Modulefiles:
        1) modules  2) craylibs  3) craytools  4) cf90  5) PrgEnv
```

If you wish to see all the product levels that are available, type module avail. For example:

 % module avail

    --------- /opt/modules/modules/modulefiles ---------
    PrgEnv             cf90.2.0.0.0       craylibs.2.0.0.0   modules
    PrgEnv.new         cf90.2.0.0.2       craytools
    cf90               craylibs           craytools.2.0.0.0

To switch from one product level to another, use module switch. For example:

 % f90 -V
    Cray CF90 Version 2.0.0.0 06/18/96 17:01:33

 % module switch cf90 cf90.2.0.0.2
    Switching 'cf90' to 'cf90.2.0.0.2'...ok.

 % f90 -V
    Cray CF90 Version 2.0.0.2 06/18/96 17:03:50

 % module list
    Currently Loaded Modulefiles:
       1) modules  2) craylibs  3) craytools  4) cf90.2.0.0.2  5) PrgEnv

 % module switch cf90.2.0.0.2 cf90   # Restore previous default version

To remove the PrgEnv entirely:
```
 % module rm PrgEnv
```
To restore the PrgEnv after you have removed it:
```
 % module load PrgEnv
```

For more information

See the various files in /usr/news. For example:
- SCC40.news
For more information about the module command, type man module.
"Accessing Programming Environment Software" is in /opt/ctl/doc/README (ascii) and in /opt/ctl/doc/README.ps (postscript).
A paper discussing the PrgEnv entitled "Modules: Providing a Flexible User Environment" is available in /opt/modules/modules/doc/Modules-Paper.ps.

Back to contents