...
Info | ||
---|---|---|
| ||
OpenIFS support: openifs-support@ecmwf.int. |
Cray
Note | ||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||
Possible issues with the Cray systems (using cce or gnu compilers) are related to building shared libraries and linking with supporting netcdf and python libraries. 1. If problems occur, first try using the option "--disable-shared" (configure) or "-DBUILD_SHARED_LIBS=OFF") to only build statically linked libraries. 2. If linking problems still occur, try unloading the Cray ATP module which has been known to cause problems.
3. -llibm link error. If the following occurs:
set the environment variable CRAYPE_LINK_TYPE=dynamic (or add the compiler option '-dynamic'). 4. Missing python library If this error occurs when compiling _gribapi_swig.so:
it means the directory path of the python library is not on the linkers list of directories to search. Make sure the python module is loaded. Then check any PYTHON environment variables set by the module and confirm the location of the libpython (or other version) library. Set the environment variable LIBRARY_PATH to the correct directory so that the linker can find it:
|
Intel compiler
Note | ||
---|---|---|
| ||
We currently recommend not using a higher optimization level than -O1 with the Intel compiler. Failures have been seen with grib_api and the Intel compiler when compiled with -O2. Some versions of the Intel compiler (v14.0.x) can produce an error "unknown option -soname" when using 'configure. If this occurs try using "--disable-shared" or try the cmake command instead. |
IBM compiler
Note | ||
---|---|---|
| ||
For the IBM xlc compiler we recommend disabling the creation of 'shared libraries' which is known to cause problems with some versions of grib_api. In this example, note the use of the '_r' form of the IBM compiler to ensure grib_api is compiled 'thread-safe'. |
...