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 auto
> "Martin" == Martin Wilck <[EMAIL PROTECTED]> writes:
Martin> Hi there,
Hi!
Martin> The new aclang.m4 structure actually makes implementing the
Martin> f90 support much easier than it was before.
That's the whole point, and I'm happy to see it meets its requirements
:)
Martin> I'd like t
| NTP, on the other hand, appeared to be using *some* 2.14a version of
| autoconf. But it's hard to determine really as there are no periodic
| checkpoints or at least tie in something to indicate which code set things
| were built with.
Right, this is another perverse effect of the long delays
> "Harlan" == Harlan Stenn <[EMAIL PROTECTED]> writes:
Harlan> Since I have not found a way to tell the various people who
Harlan> work on autoconf that a particular date or tag of the autoconf
Harlan> tree is what they have to use, I simply keep a tarball around
Harlan> of the version I am u
> By no way should it be the user. That's probably something easy to
> test and set. Just set ac_ext to ac_cv_prog_f90_ac_ext in
> AC_LANG(Fortran 90) and compute the latter in AC_PROG_F90. That
> should be enough?
The user must specify his source files with one or the other suffix
(.f90 would
Looking at the following code in AC_F77_NAME_MANGLING:
AC_TRY_LINK_FUNC(foobar,
f77_case=lower
f77_underscore=no
ac_foo_bar=foo_bar_,
[ other alternatives ... ]
)
AC_TRY_LINK_FUNC(${ac_foo_bar}, f77_underscore=double)
I have the following question: To my understan
