# CMAQ 5.4 combine program fails to compile on gcc 13.3.0

**URL:** <https://forum.cmascenter.org/t/cmaq-5-4-combine-program-fails-to-compile-on-gcc-13-3-0/6323>\
**Category:** CMAQ\
**Created:** [November 18, 2026, 8:59pm UTC](https://forum.cmascenter.org/t/cmaq-5-4-combine-program-fails-to-compile-on-gcc-13-3-0/6323 "2026-11-18T20:59:25Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![anders.carlson](https://avatars.discourse-cdn.com/v4/letter/a/9de0a6/32.png) [@anders.carlson](https://forum.cmascenter.org/u/anders.carlson)\
**Post date:** [November 18, 2026, 8:59pm UTC](https://forum.cmascenter.org/t/cmaq-5-4-combine-program-fails-to-compile-on-gcc-13-3-0/6323/1 "2026-11-18T20:59:25Z")

</div>

Hi there:

I am attempting to compile the combine post-processing program for CMAQ 5.4, and have ran into an error. I am using gcc 13.3.0 on Ubuntu 24.04, which is running as a parallel cluster on Amazon Web Services. These are the modulefiles I am using:

1. openmpi/4.1.7
2. netcdf-4.8.1/gcc-9.5
3. ioapi-3.2/gcc-9.5-netcdf
4. libfabric-aws/2.4.0amzn1.0

I am able to generate a makefile, but the make command fails with this error:

 ![image](https://canada1.discourse-cdn.com/flex027/uploads/cmas/original/2X/2/20d3ccaa82b17d12957322b5577ff3220c1a80ea.png)

I have very little experiencing writing or compiling Fortran, so I can’t say for sure if there is a problem in the source files, but I did look up the particular error that it generated and found a UCAR forum post by someone talking about this exact error in regards to WRF ( [How to Fix: Rank mismatch between actual argument at (1) and actual argument at (2) (scalar and rank-1) | WRF & MPAS-A Support Forum](https://forum.mmm.ucar.edu/threads/how-to-fix-rank-mismatch-between-actual-argument-at-1-and-actual-argument-at-2-scalar-and-rank-1.14995/) ).

Apparently there are some Fortran commands that have been deprecated starting at gcc 9.0, and the post goes into the fixes one could do. I don’t know what datatypes VGTOP3D, VGLVS3D, or specValue are, but it stands to reason that if they are indeed different as the error message seems to suggest, those operations that were kosher in gcc \<9.0 can no longer compile. I’m wondering if there is any merit to the fixes suggested, and if so, which environment variables in config\_cmaq.csh need to be edited in order to make the compiler play nice. For further context, these are the bash commands that are suggested.

```bash
export fallow_argument=-fallow-argument-mismatch
export boz_argument=-fallow-invalid-boz

export FFLAGS="$fallow_argument $boz_argument -m64"
export FCFLAGS="$fallow_argument $boz_argument -m64"

```

---

<div class="post-metadata">

**Author:** ![hogrefe.christian](https://avatars.discourse-cdn.com/v4/letter/h/74df32/32.png) [@hogrefe.christian](https://forum.cmascenter.org/u/hogrefe.christian)\
**Post date:** [November 18, 2026, 10:00pm UTC](https://forum.cmascenter.org/t/cmaq-5-4-combine-program-fails-to-compile-on-gcc-13-3-0/6323/2 "2026-11-18T22:00:32Z")

</div>

Hello @anders.carlson ,

the combine post-processing program was updated in 2024 to address this issue by removing the portions of the code in module\_file.F that caused this issue since it was determined that these portions of the code were unused in the first place.

Please see [this commit message](https://github.com/USEPA/CMAQ/commit/61acc1abdd89539faac1d4f924c7aaf4e3f515ac#diff-f2e13ff2c5945149934ae4d02da8bd4e626b1179b2befeba95e77945b8031fbdR924-L925) in the public CMAQ code repository for a bit of extra discussion and update to the latest version of the `combine` code to solve this issue.

---

<div class="post-metadata">

**Author:** ![anders.carlson](https://avatars.discourse-cdn.com/v4/letter/a/9de0a6/32.png) [@anders.carlson](https://forum.cmascenter.org/u/anders.carlson)\
**Post date:** [November 19, 2026, 9:05pm UTC](https://forum.cmascenter.org/t/cmaq-5-4-combine-program-fails-to-compile-on-gcc-13-3-0/6323/3 "2026-11-19T21:05:00Z")

</div>

Thanks! I removed those lines manually and it compiled okay. The executable ran as well, so looks like that fixed everything.
