Hi there,
I am currently trying to use autoconf for a software package including
fortran 90 sources.
I came across some postings from Thomas Ziehmer on this list (about a year
ago) who had already written some f90-related patches, and Thomas was
friendly enough to send them to me.
Since autoconf seems to have changed heavily since that time, I am
currently trying to implement Thomas' macros in the new code, and perhaps
add some new stuff similar to the new f77 library and name mangling
macros.
The new aclang.m4 structure actually makes implementing the f90 support
much easier than it was before.
I'd like to inquire how much interest there is to include f90-related
patches into autoconf (and automake - I also have Thomas' patches for
that, by have little experience with automake).
There is at least one technical problem for f90 in the AC_LANG structure:
The ac_ext variable. This is because f90 compilers make different
assumptions on file extensions. Although the suffix ".f90" is standard,
there is at least one compiler (xlf90 on AIX) that doesn't accept this
suffix (only ".f") unless given the "-qsuffix=f=f90" option.
Question: should macros test for the allowed extension, or should users
be required to provide a compiler option that makes the compiler recognize
".f90" ?
I also have some old macros for extended fortran 77 support, most
prominently to check for features related to C preprocessor/fortran code.
Although these certainly need to be cleaned up and adapted to the new
code structure, they might be useful
to include in autoconf sooner or later. Again, I'd like to know whether
there is interest for this in the autoconf community.
Best regards
Martin
--
Martin Wilck <[EMAIL PROTECTED]>
Institute for Tropospheric Research, Permoserstr. 15, D-04318 Leipzig, Germany
Tel. +49-341-2352151 / Fax +49-341-2352361
