If I remember correctly ./configure only generates fortran stubs if they don’t exist but won’t regenerate them later?
The —with-clean option should force configure to do a new generation of the fortran stubs also, when not using a release tar ball. Right? Barry
