On Tue, 27 Sep 2005, Malcolm J. Currie wrote:
>> Peering at the output from configure and the contents of config.log and
>> maybe config.status, is the only way to see what's happening.
>
> No mention of g77 or gfortran in these files. config.cache does know
> about it because of my setting FC.
>
> config.cache:ac_cv_env_FC_value=g77
> config.cache:ac_cv_prog_ac_ct_F77=${ac_cv_prog_ac_ct_F77=g77}
> config.cache:ac_cv_prog_fpp=${ac_cv_prog_fpp='g77 -E'}
> config.cache:star_cv_initialise_fortran=${star_cv_initialise_fortran=g77-setarg}
Slight sublety here. You have to look at the various config files in a
package that uses Fortran. At the top-level you just get the shared cache
file. In say applications/astrom/config.log you can see straight-away what
compilers are being used.
>> order). Pausing at gfortran is a known bug, to me anyway, I think it's
>> mentioned in the Wiki page somewhere.
>
> One possibility is that rlspc3 now has a gfortran, but didn't the last
> time I did a full build on rlspc3.
>
>> What operating system are you actually running? Strange you have gfortran
>> if not Fedora Core 4.
>
> RHEL 4 2.6.9-5.0.5.EL
Should have remembered about RHEL/4, since that's why I have it on my
desktop. I guess rlspc3 has been upgraded from RHEL/3 since the last full
build you tried. Anyway now you have gfortran you do need to set FC.
Cheers,
Peter.
|