...
These errors occur if emoslib was built without GRIB_API ecCodes support. When you build emoslib, you're given the option to build it with GRIB_API supportecCodes support, as which point you should say 'yes' and tell it where to find the GRIB_API librariesecCodes libraries. Once you've rebuilt emoslib with this option, Metview should be able to link correctly with it.
...
where [ifort8.1path] is replaced by the path to where the Intel fortran libraries are.
How should I build GRIB_API for ecCodes for Metview?
See the answers to the next two questions.
...
I get error messages saying that I need the -fPIC option
By default, EmosLib and GRIB_API are ecCodes are built without this option. It is, however, needed on some systems. The flag can be added to the GRIB_API build ecCodes build options, for example like this:
...
I get the following error message when I try to read GRIB data in Metview: “GRIB_API ERROR “ecCodes ERROR : Unable to find boot.def”
It is possible to check a GRIB_API installation ecCodes installation from the command line by finding a GRIB file and typing:
...
If this error message appears, then GRIB_API is ecCodes is not properly installed, and there are two ways to solve the problem.
To rebuild, GRIB_API should ecCodes should be configured with the --prefix option before it can find its resource files, for example:
...
Another option, which does not require a rebuild of GRIB_APIecCodes, is to change the value of the environment variable GRIB_DEFINITION_PATH. The command grib_info will tell you the current value. Normally, it should be set to /usr/local/share/grib_apieccodes/definitions, but you should first check that this directory exists.
...