"This module file was not generated by any release of this compiler" error during make using cmake.

[PellTheTabber1]

I managed to get NetCDF installed enough to get it to configure ok with NETCDF turned on but it errors out after 39% of the build on file w3ounfmetamd.F90 NETCDF USE NETCDF on line 177. I wonder if the fact that I'm now building with Intel's compiler is conflicting with how the libraries were built? Do I need to build the libraries from scratch due to changing from Gnu over to Intel's compilers? I can only build right now if I turn the NETCDF off in the build which means my runs of tests won't work right I would imagine. The build is building with Intel's fortran and C/CPP now so I'm half-way there. Just curious if anyone has a thought or has seen this before? I know we are going over to Intel per a discussion earlier this year so I need to keep my build as Intel moving forwards but it seems maybe the NETCDF I have is not Intel, but gfortran. I'm clueless what to do - do I build all these libraries from source code or is there a repository where they have them built with the correct compiler or am I missing the point of the title of my discussion? I realize it might be an ifort versus gfortran issue so I must check all environment variables but I distinctly remember the cmake -S . etc.. sequence using Intel's compiler.
In the meantime, I guess I will have to rebuild the libnet fortran part with a different compiler? I've rebuilt the C library (the one that has the utilities ncdump, ncgen, nccopy, etc.., now I still need to do the fortran.

[PellTheTabber1]

This afternoon, I went to unidata's website, downloaded the c zip for 4.9.2 and the fortran zip for 4.6.1 and built the C and Fortran NETCDF system from scratch, then reran the build using cmake and there is no errors this time so perhaps it was just the mismatch in compilers for NETCDF and me not setting some don't care flag - I don't know if one exists. So hopefully I can start testing now. Not there yet. In the meantime, I had accidentally blown my environment completely away by overloading my shell's copy and paste buffer, so I had to rerun the setvars.bat for Intel's compiler, after I mistakenly removed and reinstalled via the package manager. That's a new one.