[svn-r8966] Purpose: Maintenance

Description: Added support for Absoft Fortran compiler

Solution: Modified configuration file to check which Fortran compiler is used
          and set appropriate flags.

Platforms tested: verbena with pgf90 and Absoft f95 compilers

Misc. update:
This commit is contained in:
Elena Pourmal 2004-07-29 16:08:16 -05:00
parent d60d367930
commit abf5d5cf60
2 changed files with 57 additions and 16 deletions

View File

@ -18,6 +18,26 @@ NOFP=${NOFP:=-fomit-frame-pointer}
# Figure out compiler flags
. $srcdir/config/gnu-flags
# Figure out which compiler we are using: pgf90 or Absoft f95
RM='rm -f'
tmpfile=/tmp/cmpver.$$
$F9X -V >$tmpfile
if test -s "$tmpfile"; then
if( grep -s 'Absoft' $tmpfile > /dev/null)
then
F9X_BASENAME=f95
CFLAGS="$CFLAGS -DH5_ABSOFT"
fi
if( grep -s 'pgf90' $tmpfile > /dev/null)
then
F9X_BASENAME=pgf90
fi
fi
$RM $tmpfile
# The default Fortran 90 compiler
#
@ -36,20 +56,38 @@ HID_T='SELECTED_INT_KIND(R_INTEGER)'
SIZE_T='SELECTED_INT_KIND(R_INTEGER)'
OBJECT_NAMELEN_DEFAULT_F=-1
if test -z "$F9X"; then
F9X=pgf90
if test "X-" = "X-$F9X"; then
F9X=pgf90
F9X_BASENAME=pgf90
fi
if test -z "$f9x_flags_set"; then
F9XSUFFIXFLAG=""
FSEARCH_DIRS=""
FFLAGS="$FFLAGS"
DEBUG_FFLAGS=""
PROD_FFLAGS=""
PROFILE_FFLAGS=""
f9x_flags_set=yes
fi
case $F9X_BASENAME in
pgf90)
F9XSUFFIXFLAG=""
FFLAGS="$FFLAGS"
FSEARCH_DIRS=""
DEBUG_FFLAGS=""
PROD_FFLAGS=""
PROFILE_FFLAGS=""
f9x_flags_set=yes
;;
#
# Assume Absoft compiler
#
f95)
F9XSUFFIXFLAG=""
# We force compiler to use upper case for external names
# (just in case since this should be a default EIP)
FFLAGS="$FFLAGS -YEXT_NAMES=UCS"
FSEARCH_DIRS=""
DEBUG_FFLAGS="-O"
PROD_FFLAGS="-O"
PROFILE_FFLAGS="-O"
f9x_flags_set=yes
;;
esac
# The default C++ compiler
# The default compiler is `g++'.

View File

@ -150,6 +150,8 @@ New Features
Support for new platforms, languages and compilers.
=======================================
- Absoft compiler f95 v9.0 supported on Linux 2.4
EIP - 2004/07/29
- HDF5 Fortran APIs are supported on Mac OSX with IBM XL Fortran
compiler version 8.1. This is a default compiler.
- HDF5 Fortran APIs are supported on MAC OSX with Absoft F95 compiler
@ -382,8 +384,9 @@ Platforms Tested
g++ 3.2.2, 3.2.3
Intel(R) C++ Version 7.1
Intel(R) Fortran Compiler Version 7.1
PGI compilers (pgcc, pgf90, pgCC) version 4.0-2
PGI compilers (pgcc, pgf90, pgCC) version 5.0-2
MPIch 1.2.4
Absoft Fortran v9.0
OSF1 V5.1 Compaq C V6.4-014
Compaq C V6.3-027
Compaq Fortran V5.5-1877
@ -417,7 +420,8 @@ Platforms Tested
MAC OS X Darwin 6.5
gcc and g++ Apple Computer, Inc. GCC
version 1161, based on gcc version 3.1
IBM XL Fortran compiler version 8.1 Beta
IBM XL Fortran compiler version 8.1
Absoft Fortran v8.2
@ -567,14 +571,13 @@ Known Problems
replace H5Aff.f90, H5Dff.f90 and H5Pff.f90 files in the fortran/src
subdirectory in the top level directory with the Cray-specific files
from the site:
ftp://hdf.ncsa.uiuc.edu/pub/outgoing/hdf5/hdf5-1.6.2/F90_source_for_Crays
* On some platforms that use Intel compilers to build HDF5 fortran library,
* On some platforms that use Intel and Absoft compilers to build HDF5 fortran library,
compilation may fail for fortranlib_test.f90, fflush1.f90 and fflush2.f90
complaining about exit subroutine. Comment out the line
IF (total_error .ne. 0) CALL exit (total_error)
ftp://hdf.ncsa.uiuc.edu/pub/outgoing/hdf5/hdf5-1.6.0/F90_source_for_Crays
* On IA32 and IA64 systems, if you use a compiler other than GCC (such as
Intel's ecc or icc compilers), you will need to modify the generated
"libtool" program after configuration is finished. On or around line 104 of