Subject: | RFE: provide overrides for incorrect assumptions |
ExtUtils::F77 can't handle all of the corner cases, although it tries. For example, I've discovered OSX systems where gfortran is only available as gfortran-mp-4.X (choose your X), with no link made to gfortran, so it isn't found.
Some ideas on how to deal with this:
* Have a system for overriding some of the assumptions via environment variables (in addition to possible arguments passed to import()).
* Create a cache of the "proper" values upon installation of ExtUtils::F77, to eliminate the need to set the environment variables. That would lead to things being out of sync if one upgraded compilers.
* If the code were refactored into system specific modules with ExtUtils::F77 just being a dispatcher, it would be possible to create a plugin system which would allow local rules for selecting the compiler which would be more sophisticated than replacing a single value (e.g., using the latest version of gfortran-mp-4.X, or noticing when cached versions were no longer the latest one).
I like the last the best, but things would have to be carefully done to prevent breakage. Or, this might be the time to freeze ExtUtils::F77 and transition to a newer ExtUtils::Fortran distribution.
Any thoughts?
Diab