This document is intended to guide the user through the process of downloading, configuring and installing GEMPAK v6.4.0 for most common systems (32 and 64-bit Linux and Solaris). Specific instructions for building on OS X are available as well.
Last Updated October 2011
The current release of GEMPAK (v6.4.0) is provided as a gzip/tarball archive and can found on the download page. GEMPAK can be installed by an individual user, and root / superuser permission is not required. It's assumed for this guide and throughout other online documentation that GEMPAK is installed for a gempak user account in the home directory.
Unpacking the archive in the gempak user home directory (assuming
tar -xvzf gempak_upc6.4.0.tar.gz
will create the directory
Creating a symbolic link
ln -s GEMPAK6.4.0/ NAWIPS
To build GEMPAK on your system, the environmental variable
If you unpacked GEMPAK in
If you unpacked and plan to install GEMPAK in an uncommon directory (such as
# Please configure the following definitions to reflect your system: # # Top level directory: setenv NAWIPS /home/gempak/GEMPAK6.4.0 #
source the full path of Gemenviron in your
add the following to
Important environmental variable to be familiar with are:
$NAWIPS as defined above $GEMPAK points to $NAWIPS/gempak $GEMTBL points to $GEMPAK/tables $OS_BIN points to $GEMPAK/os/$NA_OS/bin $OS_LIB points to $GEMPAK/os/$NA_OS/lib $GEMMAPS points to $GEMPAK/maps $GEMDATA points to /data/ldm/gempak $NA_OS is determined by Gemenviron (linux, linux64, x86, SunOS, Darwin, etc. )
The last definition,
If your system uses standard locations for its compilers, X11/Motif libraries and make utilities, you do not needto change any settings. It's assumed both an ansi compatible C compiler and a Fortran 77 compatible compiler are available.
To build locally from source, you must have the developer environments installed for X11, Open Motif and libXp.
Generally you have the option to build Open Motif locally from source (v2.3.3), but for Fedora Core 13 & 14 systems a source build is required.
To change the GCC compiler, edit the
# Uncomment the following lines for using GCC compilers (Solaris/HP only) # set USEGCC_SOL=1 # set USEGCC_HPUX=1 # set USE_GFORTRAN=1 #set USE_PGI=1 #set USE_G77=1
For most systems, GEMPAK will be built using either g77 or gfortran[4.1+]. Files located in
Bundled cc is not ansi compatible, so SunOS users should make sure
Ubuntu builds require the compiler flag
Mac OS X GEMPAK Installation Guide, Kevin Tyle, University of Albany.
This document will guide users through building GEMPAK on Intel Mac OS X 10.6 (Snow Leopard) with GCC 4.4 compilers. The same procedure should also work for 10.5 (Leopard), but earlier versions/CPU's of OS X remain untested.
GEMPAK and various bundled libearies are compiled from source by the Make tool, using the Fortran and C compilers specified in the above configuration files. From
make all >& make.out
The redirection command >& sends STDOUT to the log file
tail -f make.out
or attach an ampersand to send make to the background and tail the log instantly
make all >& make.out & tail -f make.out
This process allows you to examine the build as it runs but preserves the output in the event something goes horribly wrong. If seeking help from Unidata, attach some or all of this
make install; make clean
Executables are installed to
If your distribution is modified by patches or other edits and updates and you have to rebuild, the compilation time will be reduced as the libraries which took the majority of the time to build already exist.
In the event that core definitions change and libraries must be built from scratch, a the entire install for your system will need to be cleaned:
This full clean will delete all objects and executables as well as all libraries built for the current system.
This command will combine the steps of
build versions of programs which link directly to device drivers (eliminating the gplt/message queue interface). These are primarily used for projects where multiple scripts are run at scheduled times, as in the cron, and don't require user interaction.
Everything Okay? Continue on to LDM & GEMPAK Setup
Any error messages involving missing
Xm/XmAll.h: No such file or directory > In file included from /home/gempak/GEMPAK6.4.0/include/ proto.h:28, > from /home/gempak/GEMPAK6.4.0/include/ gemprm.h:647,
Indicate that openmotif and openmotif-devel were not found on your system. Either the motif libraries are not installed on your system, or the correct location has not been specified to the compiler. If the latter is the case, you will need to edit
The runtime error
> [GEMPLT -101] NOPROC - Nonexistent executable
indicates that your environmental variables are not sourced correctly (type command 'env' to see all envars and make sure the Gemenviron configuration file is edited and sourced as described above).
> Error in message send = 22 > itype, ichan, nwords,0,65536,3
This runtime error means the message queue is full, which typically occurs when executing GEMPAK programs in batch mode from scripts. To fix, exit GEMPAK and run
GEMPAK manual pages provide extensive documentation in the use of GEMPAK programs.
Configuring the LDM is available for GEMPAK decoding of IDD data.
GEMPAK display capability examples show what is possible for data analysis.