[CMake] ccmake and fortran

[bpwlist at cox.net]

Thanks Bill that worked great!  I was missing the step about deleting the cache file.

The next problem that I ran into was various mod.proxy dependency issues.  I saw an earlier thread on this but no solution was reached.  I ended up commenting out the module dependency code under cmDependsFortran.cxx.  Everything compiled fine with that fix.  

I'm not an expert at fortran modules.  My code is legacy f77 as is my fortran knowledge base... but I wondering  if the way that cmDependsFortran is adding module dependencies is specific to the gnu fortran compiler.  I know the intel fortran compile that I'm using doesn't generate any mod.proxy files.  If there are any f90 module specific tests that I can run, I would be happy to do so with the intel compiler in order to investigate the problem further.

Thanks,

Bryan Walsh
 

---- "William A. Hoffman" <billlist at nycap.rr.com> wrote: 
> 
> 
> 
> >When I run ccmake and set CMAKE_Fortran_Compiler to ifort or ${Install Path}/ifort and then configure CMAKE_Fortran_Compiler resets back to the gnu compiler /usr/bin/f95.  I don't understand why this is happening.  Any ideas?
> >
> >I'm running on FC4, with CMAKE 2.4.3.  Running ifort from the command line works fine.
> 
> 
> Remove the CMakeCache.txt file.
> 
> Then set the environment variable FC to ifort.   Then re-run ccmake.
> 
> Cmake looks for fortran compilers in this order:
> 
>  SET(CMAKE_Fortran_COMPILER_LIST ifort ifc efc f95 pgf95
>           lf95 xlf95 fort gfortran f90  pgf90   xlf90   epcf90 fort77 frt pgf77  xlf  fl32 af77 g77 f77  )
> 
> 
> Are you sure that ifort is in your path when you run ccmake?
> But the environment variable FC should force cmake to pick ifort.
> 
> setenv FC /path/to/ifort
> or
> export FC=/path/to/ifort
> 
> 
> -Bill
>