As root (or with super-user/sudo):
sudo rpm -ivh gempak-7.4.0-1.x86_64.rpmto install to a custom directory (--prefix=/usr/local will install to /usr/local/GEMPAK7)
sudo rpm -ivh gempak-7.4.0-1.x86_64.rpm --prefix=/usr/local
OR, Install via Unidata AWIPS yum repository:
wget -O /etc/yum.repos.d/awips2.repo http://www.unidata.ucar.edu/software/awips2/doc/awips2.repo sudo yum clean all sudo yum install gempak
GEMPAK built against libpython2.7.so, which allows the use of the python-awips package to retrieve and display AWIPS data in GEMPAK programs.
As root (or with super-user/sudo):
sudo rpm -ivh gempak-python-7.4.0-1.x86_64.rpmInstall via Unidata AWIPS yum repository (incl. python packages installed to
sudo yum groupinstall gempak-pythonor (standalone, requires Python 2.7 be installed and available via LD_LIBRARY_PATH)
sudo yum install gempak-python
. GEMPAK7/Gemenviron.profileto your ~/.bashrc file.
yum install openmotif libX11 libXt libXext libXp libXft libXtst xorg-x11-xbitmaps -y
tar -xvzf gempak-7.4.0.tar.gz
ln -s GEMPAK7/ NAWIPS
cd GEMPAK7 . Gemenviron.profile make everything
. build_python.sh make everything
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/GEMPAK7 #
source the full path of Gemenviron in your
add the following to
Important environmental variable to be familiar with are:
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.
yum install gcc gcc-c++ gcc-gfortran libX11 libX11-devel libXt-devel \
libXext libXp libXp-devel libXft-devel libXtst-devel xorg-x11-xbitmaps flex \
byacc *fonts-ISO8859-* -y
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/GEMPAK7/include/ proto.h:28, > from /home/gempak/GEMPAK7/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.