1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
|
# -*- shell-script -*-
#
# This file is part of the HDF4 build script. It is processed shortly
# after configure starts and defines, among other things, flags for
# the various compilation modes.
# C and Fortran Compiler and Preprocessor Flags
# ---------------------------------------------------
#
# - Flags that end with `_CFLAGS' are always passed to the C compiler.
# - Flags that end with `_FFLAGS' are always passed to the Fortran
# compiler.
# - Flags that end with `_CPPFLAGS' are passed to the C compiler
# when compiling but not when linking.
#
# DEBUG_CFLAGS
# DEBUG_FFLAGS
# DEBUG_CPPFLAGS - Flags to pass to the compiler to create a
# library suitable for use with debugging
# tools. Usually this list will exclude
# optimization switches (like `-O') and include
# switches that turn on symbolic debugging support
# (like `-g').
#
# PROD_CFLAGS
# PROD_FFLAGS
# PROD_CPPFLAGS - Flags to pass to the compiler to create a
# production version of the library. These
# usually exclude symbolic debugging switches (like
# `-g') and include optimization switches (like
# `-O').
#
# PROFILE_CFLAGS
# PROFILE_FFLAGS
# PROFILE_CPPFLAGS- Flags to pass to the compiler to create a
# library suitable for performance testing (like
# `-pg'). This may or may not include debugging or
# production flags.
#
# FFLAGS
# CFLAGS - Flags can be added to these variable which
# might already be partially initialized. These
# flags will always be passed to the compiler and
# should include switches to turn on full warnings.
#
# WARNING: flags do not have to be added to the CFLAGS
# or FFLAGS variable if the compiler is the GNU gcc
# and gfortran compiler.
#
# FFLAGS and CFLAGS should contain *something* or else
# configure will probably add `-g'. For most systems
# this isn't a problem but some systems will disable
# optimizations in favor of the `-g'. The configure
# script will remove the `-g' flag in production mode
# only.
#
# These flags should be set according to the compiler being used.
# There are two ways to check the compiler. You can try using `-v' or
# `--version' to see if the compiler will print a version string. You
# can use the value of $FOO_BASENAME which is the base name of the
# first word in $FOO, where FOO is either CC or F77 (note that the
# value of CC may have changed above).
case $F77_BASENAME in
gfortran)
if test $cc_vers_major -ge 10; then
FFLAGS="$FFLAGS -fallow-argument-mismatch"
else
FFLAGS="$FFLAGS"
fi
DEBUG_FFLAGS="-g"
PROD_FFLAGS="-O"
PROFILE_FFLAGS="-pg"
;;
g77)
FFLAGS="$FFLAGS "
DEBUG_FFLAGS="-g"
PROD_FFLAGS="-O3 -fomit-frame-pointer"
PROFILE_FFLAGS="-pg"
;;
f95)
CFLAGS="$CFLAGS"
FFLAGS="$FFLAGS"
DEBUG_FFLAGS="-g"
PROD_FFLAGS="-O"
PROFILE_FFLAGS="-pg"
;;
g95)
CFLAGS="$CFLAGS"
FFLAGS="$FFLAGS -i4"
DEBUG_FFLAGS="-g"
PROD_FFLAGS="-O"
PROFILE_FFLAGS="-pg"
;;
esac
|
