Re: produce *mod with fortran

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


Hello Ralph and all,

I think I have updated autoconf succesfully...
Now it says:
configure: error: Fortran compiler cannot create executables

If I check the log it says:
checking for Fortran compiler version
$FC --version >&5
configure:2460: ifort --version >&5
ifort (IFORT) 12.0.0 20101006
Copyright (C) 1985-2010 Intel Corporation.  All rights reserved.

configure:2471: $? = 0
$FC -v >&5
configure:2460: ifort -v >&5
Version 12.0.0
configure:2471: $? = 0
$FC -V >&5
configure:2460: ifort -V >&5
Intel(R) Fortran Intel(R) 64 Compiler XE for applications running on
Intel(R) 64, Version 12.0.0.084 Build 20101006
Copyright (C) 1985-2010 Intel Corporation.  All rights reserved.

configure:2471: $? = 0
$FC -qversion >&5
configure:2460: ifort -qversion >&5
ifort: command line warning #10006: ignoring unknown option '-qversion'
ifort: command line error: no files specified; for help type "ifort -help"
configure:2471: $? = 1
configure:2486: checking whether the Fortran compiler works
configure:2508: ifort -c -O2 -convert big_endian -free -assume
byterecl   conftest.f  >&5
configure:2512: $? = 0
configure:2550: result: no
configure: failed program was:
|       program main
|
|       end
configure:2555: error: in
`/net/orbit272l/home/pub/evemarie/projects/CRTM/autoconf/play/CRTM':
configure:2557: error: Fortran compiler cannot create executables


First I am not sure why it goes through all those tests to find the
version and doesn't stop once one test has been successful but that is
probably not part of the problem....

I still don't see a conftest...

As previously if I use -g only as my FCFLAGS instead of -c -O2 -convert
big_endian -free -assume byterecl , configure runs fine but then of
course make doesn't....

Any insights would be greatly appreciated,
Have a great week-end,
Thanks,
Cheers,
Eve-Marie
Ralf Wildenhues said the following on 1/14/2011 2:13 PM:
> Hello Eve-Marie,
>
> addressing the remaining part of your question:
>
> * Eve-Marie Devaliere wrote on Fri, Jan 14, 2011 at 05:32:58PM CET:
>> I have created my makefiles and configure.ac...
>> I have read in the tutorial that FCFLAG had to be set to -g (unless it
>> is g77).. Well I need to create *.mod and *.o so I need another set of
>> flags.....
> [...]
>
>> In my Makefile.am I have entries such as:(there are many more like that)
>> bin_PROGRAMS = Type_Kinds
>> Type_Kinds_SOURCES = Type_Kinds.f90
>> ... is that wrong for modules?
>>
>> I tried those macro too
>> AC_PROG_FC_C_O
>> AC_FC_MAIN
>> in my configure.ac to try telling it it didn't have a main (I just want
>> modules), but no luck.... (Please bear with me as I am new to Fortran
>> too... )
> 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])
>
>
> And then we use the substituted variables in the Makefile.am files,
> more or less like this:
>
> # Find module files from the ../lib directory.
> AM_FCFLAGS = $(FC_MODINC)../lib
>
> # Clean up modules.
> clean-local: clean-modules
> clean-modules:
> 	test -z "$(FC_MODEXT)" || $(RM) *.$(FC_MODEXT)
>
>
> Now, Automake doesn't (yet) have builtin support for Fortran module
> dependencies, so you will have to write dependencies yourself, or use
> one of the several scripts out there for them.  Sorry.  We would like to
> change this in the near future ...
>
> If you need to support long lines in Fortran sources (and can require
> Autoconf >= 2.68), you can also use the new AC_FC_LINE_LENGTH macro.
>
> Hope that helps.
>
> Cheers,
> Ralf
>
> _______________________________________________
> Autoconf mailing list
> Autoconf@xxxxxxx
> http://lists.gnu.org/mailman/listinfo/autoconf

_______________________________________________
Autoconf mailing list
Autoconf@xxxxxxx
http://lists.gnu.org/mailman/listinfo/autoconf


[GCC Help]     [Kernel Discussion]     [RPM Discussion]     [Red Hat Development]     [Yosemite News]     [USB]     [Samba]

Add to Google Powered by Linux