Re: autoconf 2.52

[Steven G. Johnson]

Pieter> The following testsuite.log was produced on a Mac OS X box.
Pieter> The problem seems to be related to the fact that the f77
Pieter> command is really a script which calls f2c.
Pieter> If more information is required, please let me know.

(Note that that this f77-f2c wrapper does not come standard with MacOS
X, and g77 3.0 supports MacOS X, I believe.)

The problem here seems to be that your f77 script does not support any
known "verbose" flag to get it to say what libraries it is linking with,
so autoconf cannot detect them.   (There is usually a libf2c or something
that is required if you want to link to any code using Fortran intrinsic
functions, etcetera.)  We have two options here:

1) If there is some special verbose flag that your f77 script uses, we can
easily support it.  Currently, we check:  -v -verbose --verbose -V -\#\#\#

2) We can try to manually detect this f77-f2c script and manually set the
right FLIBS (Fortran libraries).  Ugh.

3) We can screw it and say that linking C and Fortran code using this
script is not supported automatically.  The user has to specify the FLIBS
environment variable explicitly to get the right Fortran libs.

Obviously, we would prefer (1), but if it not practical I would not feel
too guilty about (3)...

Steven

PS. Akim, please use my Reply-To address when emailing me directly.