blob: 9e3bc5cf31bebbd470f79305c00ed7704fbdaec0 (
plain)
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
|
# -*- shell-script -*-
#
# This file is part of the HDF5 build script. It is processed shortly
# after configure starts and defines, among other things, flags for
# the various compile modes.
#----------------------------------------------------------------------------
# Compiler flags. The CPPFLAGS values should not include package debug
# flags like `-DH5G_DEBUG' since these are added with the
# `--enable-debug' switch of configure.
CC=${CC:-gcc}
case `$CC -v 2>&1 |tail -1 |sed 's/gcc version //'` in
2.7.*)
echo " +------------------------------------------------+"
echo " | You have an old version of gcc. Please upgrade |"
echo " | to 2.8.1 or better. Continuing anyway, but |"
echo " | code generation may be wrong on some platforms.|"
echo " +------------------------------------------------+"
sleep 5
CCVENDOR=gcc
;;
2.8.*)
CFLAGS="$CFLAGS -Wsign-compare"
CCVENDOR=gcc
;;
egcs-*)
CFLAGS="$CFLAGS -Wsign-compare"
CCVENDOR=egcs
;;
pgcc-*)
CFLAGS="$CFLAGS -Wsign-compare"
CCVENDOR=pgcc
;;
esac
# What must *always* be present for things to compile correctly?
CFLAGS="$CFLAGS -ansi"
# What compiler flags should be used for code development?
DEBUG_CFLAGS="-g -fverbose-asm"
DEBUG_CPPFLAGS="-DH5F_OPT_SEEK=0 -DH5F_LOW_DFLT=H5F_LOW_SEC2"
# What compiler flags should be used for building a production
# library?
if [ "gcc" = "$CCVENDOR" ]; then
PROD_CFLAGS="-mcpu=pentiumpro -march=pentiumpro -O3 -finline-functions -malign-double -fomit-frame-pointer -fschedule-insns2"
PROD_CPPFLAGS=
elif [ "egcs" = "$CCVENDOR" ]; then
PROD_CFLAGS="-mcpu=pentiumpro -march=pentiumpro -O6 -malign-double"
PROD_CPPFLAGS=
elif [ "pgcc" = "$CCVENDOR" ]; then
PROD_CFLAGS="-mcpu=pentiumpro -march=pentiumpro -O6 -malign-double"
PROD_CPPFLAGS=
else
PROD_CFLAGS=
PROD_CPPFLAGS=
fi
# What compiler flags enable code profiling?
PROFILE_CFLAGS=-pg
PROFILE_CPPFLAGS=
#----------------------------------------------------------------------------
# Values for overriding configuration tests when cross compiling.
# This includes compiling on some machines where the serial front end
# compiles for a parallel back end.
# Set this to `yes' or `no' depending on whether the target is big
# endian or little endian.
#ac_cv_c_bigendian=${ac_cv_c_bigendian='yes'}
|