--
Eve-Marie Devaliere, MS
Senior Science System/Software Engineer
Joint Center for Satellite Data Assimilation (JCSDA)
Phone: (301) 763-8172
Fax: (301) 763-8149
Address: World Weather Building
Room #808
5200 Auth Rd
Camp Springs, MD 20746
The contents
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... )
Can anyone shed some light on the situation?
Thanks a lot,
Cheers,
Eve-Marie
--
Eve-Marie Devaliere, MS
: cannot
run Fortran compiled programs.
This is very strange... I tried to reset FC to ifort to make sure but no
luck
If I export FCFLAGS again with -g ; (it configures again but make
doesn't work)
Eve-Marie Devaliere said the following on 1/14/2011 11:32 AM:
Good morning autoconf
-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
:29 PM:
* 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
,
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
understand that correctly? Is there a way to go around that?
Thanks again so much for your support! You are the men! :)
Cheers,
Eve-Marie
Christopher Hulbert said the following on 1/15/2011 8:28 AM:
On Fri, Jan 14, 2011 at 4:43 PM, Eve-Marie Devaliere
eve-marie.devali...@noaa.gov wrote:
Hello
,
Eve-Marie
--
Eve-Marie Devaliere, MS
Senior Science System/Software Engineer
Joint Center for Satellite Data Assimilation (JCSDA)
Phone: (301) 763-8172 x215
Fax: (301) 763-8149
Address: World Weather Building
Room #808
5200 Auth Rd
Camp Springs, MD 20746
The contents
Thanks Frank and Eric for the prompt replies!
Autoconf includes the 'autotest' language, which parses a new file
tests.at to build up a (shell script) testsuite; as well as
documentation for a couple of hooks to add in configure.ac and your
Makefile to run such a testsuite. Such tests need
,
Cheers,
Eve-Marie
Ralf Wildenhues said the following on 1/26/2011 2:45 PM:
Hello Eve-Marie,
* Eve-Marie Devaliere wrote on Wed, Jan 26, 2011 at 05:39:35PM CET:
http://www.gnu.org/software/automake/manual/automake.html#Tests
Yes, Frank pointed me to that and I was just having a look... Thanks, I
Wildenhues said the following on 1/27/2011 12:31 PM:
Hello,
* Eve-Marie Devaliere wrote on Thu, Jan 27, 2011 at 06:02:33PM CET:
TESTS = test/forward/Example1_Simple/Example1_Simple.f90 \
test/k_matrix/Example1_Simple/Example1_Simple.f90
check_PROGRAMS = $(TESTS)
It goes like
if there wouldn't be a more elegant way... I am
new to fortran too so that may sound crazy but couldn't there be a
library of flag for known fortran compiler that autoconf could select on
the fly like for the free form one?
Thanks,
Cheers,
Eve-Marie
--
Eve-Marie Devaliere, MS
Senior Science System
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
Thanks Chris, you were right on it. I had downloaded it from sourceforge
but yes it was apparently an older file
Thanks,
Cheers,
Eve-Marie
Christopher Hulbert said the following on 1/31/2011 12:40 PM:
On Mon, Jan 31, 2011 at 12:21 PM, Eve-Marie Devaliere
eve-marie.devali...@noaa.gov wrote
Thanks Ralph.
Which kinds of flags do you need support for?
lots... :(
For example, in their original make.macros they had
# Compiler settings for DEBUG builds
LINUX_COMMON_FLAGS_GFORTRAN_DEBUG = -pg
LINUX_FLAGS_GFORTRAN_DEBUG =
FC_FLAGS= -c \
oops I think I spoke a little too fast. autoconf was not giving me
errors anymore but configure is still not happy
first of all even with my
AC_CONFIG_MACRO_DIR([m4]) in configure.ac (before macro calls)
and ACLOCAL_AMFLAGS= -I m4 in Makefile.am (top one) , I still need to run
aclocal
Thanks Ralph (again :) )
Well, we've already clarified that you should drop -c.
yes , my bad, I just copied what they had in the rules.macros file
For any gfortran-specific flag that there is no good macro for, you can
start off by wrapping it in this if clause:
if test
Thanks again and again Ralph...
well I am at a lost with what happened... I wasn't running autoreconf
but diligently (or badly ? :) )typing the whole set of : libtoolize,
aclocal -I m4, autoconf, automake
I changed the else to what you suggested, ran autoreconf and it worked
when running
In their original setup, they had support for the following compilers:
xlf95, f95, f90 (SGI IRIX64 MIPSpro, Absoft and HP-UX), gfortran,
ifort, pgf95, lf95, g95.
Well, maybe you can then fill the table below of possible flags, and
we can try writing macros for them.
Oh that would be
19 matches
Mail list logo