...
If you are familiar with compiling and installing software on linux systems, you will be used to the following steps. Grib_api uses the GNU configure tool to ease building and compilation. It is tested on different platforms and compilers and should not cause any problems. If however, you do have a problem installing grib_api, please email: Software.Services@ecmwfSupport@ecmwf.int.
The configure command is contained in the grib_api directory you have just unpacked. We will use the command with a few options to suit OpenIFS and assume we'll use the gcc & gfortran compilers. If you use different compilers, see below.
...
--disable-jpeg OpenIFS does not need to support bitmaps in GRIB so this is disabledJPEG and PNG for data compression. This removes the need to link OpenIFS against the Jasper library (libjasper.a).
...
Once configure has completed it will create a 'Makefile' in the directory. To compile grib_api do:
| Code Block |
|---|
make >&| tee make.out |
which will send all the output from the make command to the file for make.out as well as the terminal. This is recommended as the output is lengthy.For non-bash Shell users, this command might fail in which case do: make 2>&1 make.out.
Next, to verify grib_api works correctly run:
| Code Block |
|---|
make check | >&tee check.out |
Verify that all the grib_api tests have passed. If not, go back and check your configure options. In case of difficulty, contact Software.Services@ecmwfSupport@ecmwf.int.
| Info | ||
|---|---|---|
| ||
Some HPC systems use a different architecture for their login or frontend node but their compilation system is targeted at the batch nodes. If this is the case you may see failures in the 'make check' stage because the checks, although compiled for the backend batch nodes are being run on the frontend nodes and will therefore may not correctly. If this is the case on your system, we recommend running the 'make check' step in a small batch job to verify grib_api was installed correctly. |
Finally 
, to install grib_api do:
| Code Block |
|---|
make install | >&tee install.out |
At the end of this step, in the directory we are using in this example, oifs/grib_api, you should now have a directory called install which contains the following:
...