Scheduled Downtime
On Friday 21 April 2023 @ 5pm MT, this website will be down for maintenance and expected to return online the morning of 24 April 2023 at the latest

(RESOLVED) catastrophic error: cannot open source file "jasper/jasper.h"

This post was from a previous version of the WRF&MPAS-A Support Forum. New replies have been disabled and if you have follow up questions related to this post, then please start a new thread from the forum home page.


I have now compiled the WRF with "./comple em_real" with the 16th compiler option.
I have now added that line to configure.wps and the previous problem is resolved.
But I got a new problem with Jasper,
dec_jpeg2000.c(5): catastrophic error: cannot open source file "jasper/jasper.h"
#include "jasper/jasper.h"
Attached please kindly find my log file for the wps.
Any idea about this?

I loaded the following module and built the libpng and zlib following the instructions on the tutorial.
module load intel/19.0.3
module load intelmpi/2018.0.128
module load netcdf/
module load mvapich2/2.3.2
export NETCDF=/share/apps/netcdf/
module load jasper/1.900.1

Thanks in advance!


  • log2.wps
    95.4 KB · Views: 63
Can you check whether you actually do have the jasper.h file where your jasper module is built? It's likely in the include/ or include/jasper.
Thanks a lot.

Yes. I loaded this from a cluster by
$ module load jasper/1.900.1
$ ls /share/apps/jasper/1.900.1/include/jasper/jasper.h
In your configure.wps file, you should see these 2 lines:
COMPRESSION_LIBS    = -L/glade/u/home/wrfhelp/UNGRIB_LIBRARIES/lib -ljasper -lpng -lz
COMPRESSION_INC     = -I/glade/u/home/wrfhelp/UNGRIB_LIBRARIES/include

That means that the WPS program is looking for your ungrib libraries in those paths, which obviously don't exist for you (they are default WRF support paths). You will need to make sure that you have the libraries set up as they should be (see the compiling tutorial web page:, and then modify the configure.wps file to point to the correct location. Before rebuilding WPS, issue a 'clean -a' and then reconfigure. Then modify the configure.wps file, save that file, and then recompile.
I saw that you responded, but had a new question. We like to keep the topics separate on the forum to help future users who are searching for a specific problem. I have moved your new question here: