Norman,
I'll address this to you as the maintainer of the fortran autoconf
system rather than a Starlink person.... Feel free to ignore me.
1. Did the patches ever get off? (sorry)
2. I'm playing with a g95 and I'm getting trouble with the autoconf
tests. Specifically:
eg in astrom:
configure:4187: WARNING: Use AC_PROG_FC with AC_PROG_FPP, instead of AC_PROG_F77
This one is odd given that astrom configure.ac uses AC_PROG_FC and
AC_PROG_FPP. So I don't know why it thinks AC_PROG_F77 is being used.
Secondly (and more fatal) to test the preprocessor there is a fatal lack
of $(FFLAGS):
configure:4187: WARNING: Use AC_PROG_FC with AC_PROG_FPP, instead of
AC_PROG_F77
configure:4229: checking for Fortran flag to compile preprocessable .F
files
configure:4257: g95-64 -c -Wall -g -O2 -m64 -mcpu=powerpc64 conftest.F
>&5
configure:4263: $? = 0
configure:4267: test -z
|| test ! -s conftest.err
configure:4270: $? = 0
configure:4273: test -s conftest.o
configure:4276: $? = 0
configure:4348: result: none
configure:4541: checking for fixed form Fortran preprocessor features
configure:4555: g95-64 -o conftest conftest.F >&5
ld:
/usr/local/g95-20050808src-64/bin/../lib/gcc-lib/powerpc-apple-darwin8.2.0/4.0.1//libf95.dylib
bad magic number (not a Mach-O file)
configure:4561: $? = 1
configure: failed program was:
| #define OK
| program main
| #ifndef OK
| syntax error
| #endif
|
This fails and everything dies because I have a case insenitive file
system. The problem is that the fortran runtime library is 64bit and so I
really really need $(FLAGS) to be included for the compiler tests to
actually work. You will note that the first test did include $(FFLAGS)
(and passed) but the second test failed. I'm hoping this is an easy fix...
--
Tim Jenness
JAC software
http://www.jach.hawaii.edu/~timj
|