Re: produce *mod with fortran

[Eve-Marie Devaliere]

Thanks Paul!
well it is looking for b.out....
---
configure:1840: $? = 0
configure:1854: checking for Fortran compiler default output file name
configure:1857: ifort -c -O2 -convert big_endian -free -assume
byterecl   conftest.f  >&5
configure:1860: $? = 0
configure:1908: result: b.out
configure:1913: checking whether the Fortran compiler works
configure:1919: ./b.out
./configure: line 1920: ./b.out: No such file or directory
------
nbut I don't see any file names conftest.f (locate either)
when I run with FCFLAGS=-g ; it is looking for a.out and finds it
(didn't find any file with that name either) and keeps on going...
this happens in configure there:
-----
# b.out is created by i960 compilers.
for ac_file in a_out.exe a.exe conftest.exe a.out conftest a.*
conftest.* b.out
do
  test -f "$ac_file" || continue
  case $ac_file in
    *.$ac_ext | *.xcoff | *.tds | *.d | *.pdb | *.xSYM | *.bb | *.bbg |
*.o | *.obj )
        ;;
    conftest.$ac_ext )
        # This is the source file.
        ;;
    [ab].out )
        # We found the default executable, but exeext='' is most
        # certainly right.
        break;;
    *.* )
        ac_cv_exeext=`expr "$ac_file" : '[^.]*\(\..*\)'`
        # FIXME: I believe we export ac_cv_exeext for Libtool,
        # but it would be cool to find out if it's true.  Does anybody
        # maintain Libtool? --akim.
        export ac_cv_exeext
        break;;
    * )
        break;;
  esac
done
---
it does say b.out is created by i960 compilers but my compiler hasn't
changed ; just the flags....?
I did print out the path and it is in my current directory... I don't
have any a.out or b.out....

I'll keep on digging but I am at a lost here....
Thanks,
Cheers,
Eve-Marie

Paul Eggert said the following on 1/14/2011 1:18 PM:
> On 01/14/11 09:23, Eve-Marie Devaliere wrote:
>> checking whether the Fortran compiler works... configure: error: cannot
>> run Fortran compiled programs.
> Please check the output log: it should have a copy of the program
> that couldn't run, along with how it was compiled and built.
> This should let you reproduce the problem and determine how to
> work around it.