Is there a way to compile wgrib2 with GCC?
To get jpeg2000 support, you will either have to use OpenJPEG or compile Jasper with the gnu compiler. The makefile will automatically use gcc when trying to build the Jasper library when the Intel compilers are used. Compiling wgrib2 using the Intel compilers on Windows is possible but is not supported.
How big of A Grib file do I need for wgrib2?
Wgrib2 will work with a 32-bit long int but will limit a grib file to an unacceptable 2GB size. Cygwin’s gcc also supports POSIX which means that you don’t have to turn off features that require POSIX. You need to use compile with gcc and gfortran. The default MacOS installation has gcc pointing to clang.
Are there any problems with the wgrib2 utility?
The common problems are in related to experimental/alpha features and the following 3 problems. The jpeg2000 library (Jasper) could seg-fault with larger grids. This problem was fixed with an Ubuntu/Debian update to Jasper (fall 2015) which was incorporated into wgrib2 v2.0.3.
Is it possible to compile Climate Prediction center-wgrib2?
Answer: The Netcdf4/hdf5 libraries are very big and the end result is a long download time and a large executable. If you decide to compile with Netcdf4, the make will fail with the commands needed to download the netcdf4 and hdf5 libraries.
How big of A Grib file can wgrib2 compile?
The other Windows C compilers follow Microsoft’s lead where a “long int” is 32-bits on a 64 bit operating system. Wgrib2 will work with a 32-bit long int but will limit a grib file to an unacceptable 2GB size. Cygwin’s gcc also supports POSIX which means that you don’t have to turn off features that require POSIX.
What causes compiler to fail in Linux Mint?
Looks like your CFLAGS has a zero instead of capital O. That is invalid, and causing the compilation to fail. You can fix it, but really, look for a later version of the package which has been fixed. I was having this exact same problem trying to install tivodecode on a base build of Linux Mint 17.3.