[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: produce *mod with fortran
From: |
Ralf Wildenhues |
Subject: |
Re: produce *mod with fortran |
Date: |
Fri, 14 Jan 2011 20:29:40 +0100 |
User-agent: |
Mutt/1.5.20 (2010-08-04) |
* Eve-Marie Devaliere wrote on Fri, Jan 14, 2011 at 08:07:47PM CET:
> 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
Ahh. You have a very old Autoconf version installed. Please install a
newer version (and if you need to do it in a local directory, go ahead
and install a newer Automake right along in the same prefix).
Then rerun autoreconf -v inside your project (after adjusting PATH so it
points to the new autotools).
I bet this is
http://lists.gnu.org/archive/html/autoconf-patches/2006-08/msg00008.html
fixed by commit 75f337207698f515f252005ff67d7d8fd1728f4d.
Cheers,
Ralf
Re: produce *mod with fortran, Ralf Wildenhues, 2011/01/14
- Re: produce *mod with fortran, Eve-Marie Devaliere, 2011/01/14
- Re: produce *mod with fortran, Paul Eggert, 2011/01/14
- Re: produce *mod with fortran, Anthony Chan, 2011/01/14
- Re: produce *mod with fortran, Christopher Hulbert, 2011/01/15
- Re: produce *mod with fortran, Eve-Marie Devaliere, 2011/01/18
- Re: produce *mod with fortran, Christopher Hulbert, 2011/01/18
Re: produce *mod with fortran, Eve-Marie Devaliere, 2011/01/31