summaryrefslogtreecommitdiffstats
path: root/config
diff options
context:
space:
mode:
authorRobb Matzke <matzke@llnl.gov>1998-04-03 03:29:38 (GMT)
committerRobb Matzke <matzke@llnl.gov>1998-04-03 03:29:38 (GMT)
commita780cdd178f849afbc8cbb24e416eef733cbc9f2 (patch)
treec9e0162ab42567a4872a5c37444be0e08d4c1914 /config
parent2a77c19b2216f04a6f8c50995ca0bf09f69e63d0 (diff)
downloadhdf5-a780cdd178f849afbc8cbb24e416eef733cbc9f2.zip
hdf5-a780cdd178f849afbc8cbb24e416eef733cbc9f2.tar.gz
hdf5-a780cdd178f849afbc8cbb24e416eef733cbc9f2.tar.bz2
[svn-r335] Changes since 19980330
---------------------- ./MANIFEST ./src/Makefile.in ./test/Makefile.in Added new files. ./config/linux ./src/H5HL.c ./src/H5HLprivate.h ./src/H5MF.c ./src/H5MFprivate.h Added `-DH5HL_DEBUG -DH5MF_DEBUG' to the debug list. ./html/H5.format.html Updated shared object message information. ./src/H5D.c Datasets can now share data types. ./src/H5F.c Updated a comment that referred to H5ACC_WRITE. ./src/H5HG.c ./src/H5HGprivate.h Moved a few things around. Made debugging better so you can now give a collection address to ./src/debug and it shows some useful stuff. ./src/H5O.c ./src/H5Ocont.c ./src/H5Odtype.c ./src/H5Oefl.c ./src/H5Olayout.c ./src/H5Oname.c ./src/H5Onull.c ./src/H5Oprivate.h ./src/H5Osdspace.c ./src/H5Oshared.c [NEW] ./src/H5Ostab.c Supports shared messages. ./src/H5T.c ./src/H5Tpkg.h ./src/H5Tprivate.h ./src/H5Tpublic.h The H5Tshare() function allows the user to give the library hints about how a data type will be used. ./test/shtype.c Tests the H5Tshare() function. ./test/gheap.c Tests the global heap. ./configure.in ./config/BlankForm [NEW] ./config/alpha-dec ./config/freebsd2.2.1 ./config/hpux10.20 ./config/irix6.2 ./config/irix64 ./config/linux ./config/powerpc-ibm-aix4.2.1.0 ./config/rs6000-ibm-aix4.1.4.0 ./config/solaris2.5 Cleaned up lots of configuration stuff and made the site configuration files lots easier and more uniform. To make a new file grab the BlankForm and modify it. By default, debugging is turned on for most packages. Within a package one can use `#ifdef H5AC_DEBUG' to wrap debugging code. Other options are: --enable-debug --enable-debug=yes The default, most but not all packages. --disable-debug --enable-debug=no --enable-debug=none The symbol NDEBUG is defined and none of the package debug symbols. --enable-debug=all Debugging is turned on for all packages. This might produce lots of output. --enable-debug=g,d Debugging is turned on for H5G and H5D. A compile mode is also now supported --enable-production --enable-production=yes The library is compiled with optimizations turned on. The compiler flags are augmented by adding PROD_CFLAGS and PROD_CPPFLAGS which are defined in the site config file. --disable-production --enable-production=no The default. The library is compiled for development by including DEBUG_CFLAGS and DEBUG_CPPFLAGS defined in the site config file. This is usually just `-g'. --enable-production=profile --enable-production=pg Builds a library for profiling by including the flags from PROFILE_CFLAGS and PROFILE_CPPFLAGS defined in the site config file. This is usullay just `-pg' but it could include optimization flags as well depending on the type of profile one wants. In summary, configure by saying `./configure' and you'll get a development version of the library. Configure by saying `./configure --enable-production --disable-debug' and you'll get a production version with no debugging code.
Diffstat (limited to 'config')
-rw-r--r--config/BlankForm43
-rw-r--r--config/alpha-dec74
-rw-r--r--config/freebsd2.2.158
-rw-r--r--config/hpux10.2040
-rw-r--r--config/irix6.240
-rw-r--r--config/irix6469
-rw-r--r--config/linux95
-rw-r--r--config/powerpc-ibm-aix4.2.1.040
-rw-r--r--config/rs6000-ibm-aix4.1.4.040
-rw-r--r--config/solaris2.543
10 files changed, 345 insertions, 197 deletions
diff --git a/config/BlankForm b/config/BlankForm
new file mode 100644
index 0000000..a844dea
--- /dev/null
+++ b/config/BlankForm
@@ -0,0 +1,43 @@
+# -*- 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.
+
+# Sometimes a particular compiler must be used. If that's the case
+# then uncomment the following line. Otherwise the main configure
+# script will try to detect the compiler automatically.
+#CC=gcc
+
+# What must *always* be present for things to compile correctly?
+#CFLAGS="$CFLAGS -ansi"
+#CPPFLAGS="$CPPFLAGS -I."
+
+# What compiler flags should be used for code development?
+DEBUG_CFLAGS=-g
+DEBUG_CPPFLAGS=
+
+# What compiler flags should be used for building a production
+# library?
+PROD_CFLAGS=-O
+PROD_CPPFLAGS=
+
+# 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'}
diff --git a/config/alpha-dec b/config/alpha-dec
index 3e54c78..2c10695 100644
--- a/config/alpha-dec
+++ b/config/alpha-dec
@@ -1,54 +1,38 @@
-#!/bin/sh
-# Site configuration -- do not distribute this file.
+# -*- 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.
-# Based on the setting of environment variable `HDF5_MODE' we set the
-# compiler flags unless they're already set. Its value can be one or
-# more of the following words (be sure to use single quotes when
-# setting its value or the dollar signs will be expanded as variables
-# too soon):
-#
-# $warn -- Generates compiler warnings. You should always
-# include this since it has no effect on the speed of
-# the code produced.
-#
-# $debug -- Compiles in code to check for invariant conditions
-# and turns on the `-g' flag for interactive
-# debugging. It also turns off seek optimizations in
-# the low-level file driver. This version of the
-# library can be significantly slower than a production
-# version.
-#
-# $production -- Compiles an optimized version of the library
-# and disables code that checks for invariant
-# conditions.
-#
-# $profile -- Compiles code with the `-pg' flag which
-# produces a `gmon.out' file when the library
-# runs. The gprof(1) command can read that file
-# and produce detailed run-time statistics.
-#
-# If HDF5_MODE is undefined then we use the value
-#
-# $debug $warn -DH5F_LOW_DFLT=H5F_LOW_SEC2
-#
+#----------------------------------------------------------------------------
+# 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.
-# Unconditionally set the compiler to gcc since the following flags
-# only apply to that compiler.
-CC=cc
+# What must *always* be present for things to compile correctly?
+#CFLAGS="$CFLAGS -ansi"
+#CPPFLAGS="$CPPFLAGS -I."
-warn=""
+# What compiler flags should be used for code development?
+DEBUG_CFLAGS=-g
+DEBUG_CPPFLAGS="-DH5F_OPT_SEEK=0 -DH5F_LOW_DFLT=H5F_LOW_SEC2"
-profile="-pg"
+# What compiler flags should be used for building a production
+# library?
+PROD_CFLAGS=-O
+PROD_CPPFLAGS=
-debug="-g -DH5AC_DEBUG -DH5B_DEBUG -DH5F_DEBUG -DH5G_DEBUG -UH5O_DEBUG -DH5T_DEBUG -DH5F_OPT_SEEK=0"
+# What compiler flags enable code profiling?
+PROFILE_CFLAGS=-pg
+PROFILE_CPPFLAGS=
-production="-O -DNDEBUG"
-default_mode='$debug $warn -DH5F_LOW_DFLT=H5F_LOW_SEC2'
+#----------------------------------------------------------------------------
+# 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.
-# Don't set CFLAGS if the user already did.
-if test -z "$CFLAGS"; then
- CFLAGS="`eval echo ${HDF5_MODE:-$default_mode}`"
- export CFLAGS
-fi
+# 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'}
diff --git a/config/freebsd2.2.1 b/config/freebsd2.2.1
index ef1c706..2cf310c 100644
--- a/config/freebsd2.2.1
+++ b/config/freebsd2.2.1
@@ -1,54 +1,6 @@
-#!/bin/sh
-# Site configuration -- do not distribute this file.
+# -*- 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.
-
-# Based on the setting of environment variable `HDF5_MODE' we set the
-# compiler flags unless they're already set. Its value can be one or
-# more of the following words (be sure to use single quotes when
-# setting its value or the dollar signs will be expanded as variables
-# too soon):
-#
-# $warn -- Generates compiler warnings. You should always
-# include this since it has no effect on the speed of
-# the code produced.
-#
-# $debug -- Compiles in code to check for invariant conditions
-# and turns on the `-g' flag for interactive
-# debugging. It also turns off seek optimizations in
-# the low-level file driver. This version of the
-# library can be significantly slower than a production
-# version.
-#
-# $production -- Compiles an optimized version of the library
-# and disables code that checks for invariant
-# conditions.
-#
-# $profile -- Compiles code with the `-pg' flag which
-# produces a `gmon.out' file when the library
-# runs. The gprof(1) command can read that file
-# and produce detailed run-time statistics.
-#
-# If HDF5_MODE is undefined then we use the value
-#
-# $debug $warn -DH5F_LOW_DFLT=H5F_LOW_SEC2
-#
-
-# Unconditionally set the compiler to gcc since the following flags
-# only apply to that compiler.
-CC=gcc
-
-warn="-Wall -Wshadow -Wpointer-arith -Wcast-qual -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wnested-externs"
-
-profile="-pg"
-
-debug="-g -DH5AC_DEBUG -DH5B_DEBUG -DH5D_DEBUG -DH5F_DEBUG -DH5G_DEBUG -UH5O_DEBUG -DH5T_DEBUG -DH5F_OPT_SEEK=0 -fverbose-asm"
-
-production="-O3 -DNDEBUG -finline-functions -funroll-loops -malign-double -fomit-frame-pointer"
-
-default_mode='-ansi $debug $warn -DH5F_LOW_DFLT=H5F_LOW_SEC2'
-
-# Don't set CFLAGS if the user already did.
-if test -z "$CFLAGS"; then
- CFLAGS="`eval echo ${HDF5_MODE:-$default_mode}`"
- export CFLAGS
-fi
+. config/linux
diff --git a/config/hpux10.20 b/config/hpux10.20
index 46bf4ee..99d333b 100644
--- a/config/hpux10.20
+++ b/config/hpux10.20
@@ -1,6 +1,38 @@
-# Site configuration -- do not distribute this file.
+# -*- 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.
-if test "x$CFLAGS" = "x"; then
- CFLAGS="-Ae"
-fi
+#----------------------------------------------------------------------------
+# 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.
+
+# What must *always* be present for things to compile correctly?
+CFLAGS="$CFLAGS -Ae"
+#CPPFLAGS="$CPPFLAGS -I."
+
+# What compiler flags should be used for code development?
+DEBUG_CFLAGS=
+DEBUG_CPPFLAGS=
+
+# What compiler flags should be used for building a production
+# library?
+PROD_CFLAGS=
+PROD_CPPFLAGS=
+
+# What compiler flags enable code profiling?
+PROFILE_CFLAGS=
+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'}
diff --git a/config/irix6.2 b/config/irix6.2
index a1c55c4..1ec4f4b 100644
--- a/config/irix6.2
+++ b/config/irix6.2
@@ -1,6 +1,38 @@
-# Site configuration -- do not distribute this file.
+# -*- 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.
-if test "x$CFLAGS" = "x"; then
- CFLAGS="-ansi -n32"
-fi
+#----------------------------------------------------------------------------
+# 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.
+
+# What must *always* be present for things to compile correctly?
+CFLAGS="$CFLAGS -ansi -n32"
+#CPPFLAGS="$CPPFLAGS -I."
+
+# What compiler flags should be used for code development?
+DEBUG_CFLAGS=-g
+DEBUG_CPPFLAGS=
+
+# What compiler flags should be used for building a production
+# library?
+PROD_CFLAGS=-O
+PROD_CPPFLAGS=
+
+# 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'}
diff --git a/config/irix64 b/config/irix64
index 95207fb..6c07765 100644
--- a/config/irix64
+++ b/config/irix64
@@ -1,27 +1,46 @@
+# -*- 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.
+
+# What must *always* be present for things to compile correctly?
+# Always turn off these warnings:
+# 1174: function declared but not used
+# 1429: the `long long' type is not standard
+# 1209: constant expressions
+# 1196: __vfork() (this is an SGI config problem)
+#
+CFLAGS="$CFLAGS -fullwarn -ansi -64 -woff 1174,1429,1209,1196"
+#CPPFLAGS="$CPPFLAGS -I."
+
+# What compiler flags should be used for code development?
+DEBUG_CFLAGS=-g
+DEBUG_CPPFLAGS=
+
+# What compiler flags should be used for building a production
+# library?
+PROD_CFLAGS=-O
+PROD_CPPFLAGS=
+
+# 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'}
#!/bin/sh
-# Site configuration -- do not distribute this file.
-CC="cc -ansi -64"
-
-# -woff 1174 about function declared but not used
-# -woff 1429 about long long type non-standard
-# -woff 1209 about constant expressions
-# -woff 1196 about __vfork() being implicitly declared, config prob.
-warn="-fullwarn -woff 1174,1429,1209,1196"
-#warn="-woff 1174,1429,1209,1196"
-
-profile="-pg"
-
-debug="-g"
-
-#production="-O -DNDEBUG"
-
-default_mode='$debug $warn'
-
-RANLIB=: # SGI needs not ranlib
-
-# Don't set CFLAGS if the user already did.
-if test -z "$CFLAGS"; then
- CFLAGS="`eval echo ${HDF5_MODE:-$default_mode}`"
- export CFLAGS
-fi
diff --git a/config/linux b/config/linux
index 78a9913..d17b5de 100644
--- a/config/linux
+++ b/config/linux
@@ -1,63 +1,38 @@
-#!/bin/sh
-# Site configuration -- do not distribute this file.
+# -*- 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.
-# Based on the setting of environment variable `HDF5_MODE' we set the
-# compiler flags unless they're already set. Its value can be one or
-# more of the following words (be sure to use single quotes when
-# setting its value or the dollar signs will be expanded as variables
-# too soon):
-#
-# $warn -- Generates compiler warnings. You should always
-# include this since it has no effect on the speed of
-# the code produced.
-#
-# $debug -- Compiles in code to check for invariant conditions
-# and turns on the `-g' flag for interactive
-# debugging. It also turns off seek optimizations in
-# the low-level file driver. This version of the
-# library can be significantly slower than a production
-# version.
-#
-# $production -- Compiles an optimized version of the library
-# and disables code that checks for invariant
-# conditions.
-#
-# $profile -- Compiles code with the `-pg' flag which
-# produces a `gmon.out' file when the library
-# runs. The gprof(1) command can read that file
-# and produce detailed run-time statistics.
-#
-# If HDF5_MODE is undefined then we use the value
-#
-# $debug $warn -DH5F_LOW_DFLT=H5F_LOW_SEC2
-#
+#----------------------------------------------------------------------------
+# 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.
+
+# What must *always* be present for things to compile correctly?
+CFLAGS="$CFLAGS -ansi"
+#CPPFLAGS="$CPPFLAGS -I."
+
+# 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?
+PROD_CFLAGS="-O3 -finline-functions -malign-double -fomit-frame-pointer"
+PROD_CPPFLAGS=
+
+# 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.
-if [ arborea = `hostname` -a -z "$enable_parallel" ]; then
- enable_parallel=mpio
-fi
-
-# The following flags only apply to the gcc compiler.
-CC=${CC:-gcc}
-
-# First set up the CFLAGS arguments.
-if test "X" = "X$CFLAGS"; then
- warn="-Wall -Wshadow -Wpointer-arith -Wcast-qual -Wwrite-strings -Wstrict-prototypes -Wmissing-prototypes -Wmissing-declarations -Wnested-externs"
- profile="-pg"
- debug="-g -fverbose-asm"
- production="-O3 -finline-functions -funroll-loops -malign-double -fomit-frame-pointer"
- parallel=""
- default_mode='-ansi $debug $warn $parallel'
- CFLAGS="`eval echo ${HDF5_MODE:-$default_mode}`"
-fi
-
-# Then set up the CPPFLAGS arguments.
-if test "X" = "X$CPPFLAGS"; then
- warn=
- profile=
- debug="-DH5AC_DEBUG -DH5B_DEBUG -DH5D_DEBUG -DH5F_DEBUG -DH5G_DEBUG -UH5O_DEBUG -DH5T_DEBUG -DH5F_OPT_SEEK=0 -DH5F_LOW_DFLT=H5F_LOW_SEC2"
- production="-DNDEBUG"
- parallel=""
- default_mode='$debug $warn $parallel'
- CPPFLAGS="`eval echo ${HDF5_MODE:-$default_mode}`"
-fi
+# 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'}
diff --git a/config/powerpc-ibm-aix4.2.1.0 b/config/powerpc-ibm-aix4.2.1.0
index e5e8738..522f50b 100644
--- a/config/powerpc-ibm-aix4.2.1.0
+++ b/config/powerpc-ibm-aix4.2.1.0
@@ -1 +1,39 @@
-ac_cv_c_bigendian=${ac_cv_c_bigendian='yes'} # or 'no'
+# -*- 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.
+
+# What must *always* be present for things to compile correctly?
+#CFLAGS="$CFLAGS -ansi"
+#CPPFLAGS="$CPPFLAGS -I."
+
+# What compiler flags should be used for code development?
+DEBUG_CFLAGS=
+DEBUG_CPPFLAGS=
+
+# What compiler flags should be used for building a production
+# library?
+PROD_CFLAGS=
+PROD_CPPFLAGS=
+
+# What compiler flags enable code profiling?
+PROFILE_CFLAGS=
+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'}
+
diff --git a/config/rs6000-ibm-aix4.1.4.0 b/config/rs6000-ibm-aix4.1.4.0
index e5e8738..522f50b 100644
--- a/config/rs6000-ibm-aix4.1.4.0
+++ b/config/rs6000-ibm-aix4.1.4.0
@@ -1 +1,39 @@
-ac_cv_c_bigendian=${ac_cv_c_bigendian='yes'} # or 'no'
+# -*- 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.
+
+# What must *always* be present for things to compile correctly?
+#CFLAGS="$CFLAGS -ansi"
+#CPPFLAGS="$CPPFLAGS -I."
+
+# What compiler flags should be used for code development?
+DEBUG_CFLAGS=
+DEBUG_CPPFLAGS=
+
+# What compiler flags should be used for building a production
+# library?
+PROD_CFLAGS=
+PROD_CPPFLAGS=
+
+# What compiler flags enable code profiling?
+PROFILE_CFLAGS=
+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'}
+
diff --git a/config/solaris2.5 b/config/solaris2.5
index 87dd710..581415e 100644
--- a/config/solaris2.5
+++ b/config/solaris2.5
@@ -1,6 +1,41 @@
-# Site configuration -- do not distribute this file.
+# -*- 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.
-if test "x$CFLAGS" = "x"; then
- CFLAGS="-Wall -g -O2"
-fi
+#----------------------------------------------------------------------------
+# 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.
+
+# We can only use gcc
+CC=gcc
+
+# What must *always* be present for things to compile correctly?
+CFLAGS="$CFLAGS -ansi"
+#CPPFLAGS="$CPPFLAGS -I."
+
+# What compiler flags should be used for code development?
+DEBUG_CFLAGS=-g
+DEBUG_CPPFLAGS=
+
+# What compiler flags should be used for building a production
+# library?
+PROD_CFLAGS=-O2
+PROD_CPPFLAGS=
+
+# 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'}