autoconf
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: produce *mod with fortran


From: Christopher Hulbert
Subject: Re: produce *mod with fortran
Date: Mon, 31 Jan 2011 12:40:46 -0500

On Mon, Jan 31, 2011 at 12:21 PM, Eve-Marie Devaliere
<address@hidden> wrote:
> Thanks Ralph! I am now trying to make my package more portable so I am
> working on the part below
>
>> Do you need the package to be very portable?  If so, I suggest you go to
>> the Autoconf Macro Archive and grab two Fortran-related macros,
>> AX_F90_MODULE_EXTENSION and AX_F90_MODULE_FLAG.
>>
>> We then use roughly the following in configure.ac besides what you
>> already have:
>>
>> # Find out how to add to the Fortran include path.
>> AX_F90_MODULE_FLAG
>> # The module flag may be "-I " or so, and some make implementations
>> # swallow trailing space in variable settings, so we employ a little
>> # trick.
>> AC_SUBST([empty], [""])
>> AC_SUBST([FC_MODINC], [$ax_f90_modflag'${empty}'])
>> # Find out the file name extensions of Fortran module files.
>> AX_F90_MODULE_EXTENSION
>> if test "x$ax_f90_modext" != xunknown; then
>>   FC_MODEXT=$ax_f90_modext
>> else
>>   FC_MODEXT=$ax_f90_modext
>> fi
>> AC_SUBST([FC_MODEXT])
> isn't the if/else above the same thing?
>
> When I run autoconf I get:
> configure.ac:81: warning: AC_CACHE_VAL(ax_f90_modflag, ...): suspicious
> cache-id, must contain _cv_ to be cached
> autoconf/general.m4:2047: AC_CACHE_VAL is expanded from...
> autoconf/general.m4:2060: AC_CACHE_CHECK is expanded from...
> m4/ax_f90_module_flag.m4:53: AX_F90_MODULE_FLAG is expanded from...
> configure.ac:81: the top level
> configure.ac:88: warning: AC_CACHE_VAL(ax_f90_modext, ...): suspicious
> cache-id, must contain _cv_ to be cached
> autoconf/general.m4:2047: AC_CACHE_VAL is expanded from...
> autoconf/general.m4:2060: AC_CACHE_CHECK is expanded from...
> m4/ax_f90_module_extension.m4:42: AX_F90_MODULE_EXTENSION is expanded
> from...
> configure.ac:88: the top level

>From where/when did you get the m4 files? Cache variables need the
_cv_ in the name for (at least newer) autoconf to like it. Looks like
this was done back in April of 2009? Make sure you update the
configure.ac code above for the variable names.

commit 2673212c84ed131e9014832005277da6513aabeb
Author: Luc Maisonobe <address@hidden>
Date:   Sun Apr 19 13:05:55 2009 +0200

    AX_F90_*: fix cached variable warnings

    Autoconf 2.63 generates warnings when cached variable names have no _cv_
    in them.

 m4/ax_f90_internal_headmod.m4 |    4 ++--
 m4/ax_f90_library.m4          |    6 +++---
 m4/ax_f90_library_setup.m4    |    6 +++---
 m4/ax_f90_module.m4           |    4 ++--
 m4/ax_f90_module_extension.m4 |   16 ++++++++--------
 m4/ax_f90_module_flag.m4      |   12 ++++++------
 6 files changed, 24 insertions(+), 24 deletions(-)


If it still fails, what compiler are you using, and can you post the
config.log file?

Chris

>
> Did I do anything wrong? I have both AX_F90_MODULE_FLAG and
> AX_F90_MODULE_EXTENSION in my m4 directory and ran aclocal -I m4
> I also have AC_CONFIG_MACRO_DIR([m4]) in my configure.ac file somewhere
> up from that section.... (it seems to find them anyways)
> I get the same warnings running automake and if I keep on going (tried
> since there were warnings only) I get the following for ./configure
> checking fortran 90 modules inclusion flag... not found
> checking fortran 90 modules extension... unknown
> ./configure: line 4710: syntax error near unexpected token `('
> ./configure: line 4710: `  $as_echo_n "(cached) " >&6'
>
> Thanks,
> Cheers,
> Eve-Marie
>
>
>
> _______________________________________________
> Autoconf mailing list
> address@hidden
> http://lists.gnu.org/mailman/listinfo/autoconf
>



reply via email to

[Prev in Thread] Current Thread [Next in Thread]