[MOAB-dev] r3036 - in MOAB/trunk: . tools/iMesh/python

[Jason Kraftcheck]

Jed Brown wrote:

> 
> This was with r3036 (today).  With your latest (r3041) the Fortran
> compiler is not printed (which makes sense because it's not being used)
> but the autoconf output clearly shows that it is searching for a Fortran
> compiler and finding gfortran (after looking for a bunch of others).  I
> do get the correct compilers when I configure without the nofortran
> argument, so maybe this is harmless?  

I think this is fixed (difficult to say as I can't reproduce it.)  The issue
is entirely cosmetic (if I did fix it) because it will only happen when MOAB
is specifically configured not to use Fortran.  The checks are probably
being done because some older versions of the libtool configuration macros
always check for a Fortran compiler (regardless of whether or not the code
ever does anything with Fortran.)

> But what if a user doesn't have
> any Fortran compiler, will autoconf fail if it doesn't find one?
> 

No.

- jason