[svn-r376] ./acconfig.h

./configure.in
./config/BlankForm
./src/H5.c
	Configure tries to figure out how to print `long long' types
	and then defines PRINTF_LL_WIDTH to be `ll' or `q' or
	something.  It does this by running little sprintf() programs
	with various formats until it gets one that works.  If this
	causes problems when cross compiling (like with parallel
	machines) then you may add the following to the appropriate
	config file:

	       hdf5_cv_printf_ll=${hdf5_cv_printf_ll='ll'}	or
	       hdf5_cv_printf_ll=${hdf5_cv_printf_ll='q'}	or
	       hdf5_cv_printf_ll=${hdf5_cv_printf_ll='l'}


./config/intel-osf1
./config/irix5.3
	Updated these config files to match the others.  This allows
	the `--enable-production' configure flag to work properly.

3 files changed, 90 insertions, 51 deletions

diff --git a/config/BlankForm b/config/BlankForm
index a844dea..5ff807b 100644
--- a/config/BlankForm
+++ b/config/BlankForm
@@ -41,3 +41,8 @@ PROFILE_CPPFLAGS=
 # 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'}
+
+# Set this to the width required by printf() to print type `long
+# long'.  For instance, if the format would be `%lld' then set it to
+# `ll' or if the format would be `%qd' set it to `q'.
+#hdf5_cv_printf_ll=${hdf5_cv_printf_ll='ll'}
diff --git a/config/intel-osf1 b/config/intel-osf1
index 66c643c..840afd4 100644
--- a/config/intel-osf1
+++ b/config/intel-osf1
@@ -1,55 +1,52 @@
-# 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.
+
+
+#----------------------------------------------------------------------------
+# 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=cicc
 AR=xar
-RANLIB=true
+RANLIB=:
 LIBS="-L./ -L../ -lnoop_stubs"
 RUNTEST="yod -sz 1"
-export CC AR RANLIB LIBS RUNTEST
-
-# 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.
-#
 
+# What must *always* be present for things to compile correctly?
+CFLAGS="$CFLAGS -DDOS386"
+#CPPFLAGS="$CPPFLAGS -I."
 
-# Unconditionally set the compiler to cicc since the following flags
-# only apply to that compiler.
+# What compiler flags should be used for code development?
+DEBUG_CFLAGS=-g
+DEBUG_CPPFLAGS=
 
-warn=""
+# What compiler flags should be used for building a production
+# library?
+PROD_CFLAGS=-O
+PROD_CPPFLAGS=
 
-profile="-pg"
+# What compiler flags enable code profiling?
+PROFILE_CFLAGS=-pg
+PROFILE_CPPFLAGS=
 
-debug="-g -DH5AC_DEBUG -DH5B_DEBUG -DH5F_DEBUG -DH5G_DEBUG -UH5O_DEBUG -DH5T_DEBUG -DH5F_OPT_SEEK=0"
 
-production="-O -DNDEBUG"
+#----------------------------------------------------------------------------
+# 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.
 
-default_mode='-DDOS386 $debug $warn -DH5F_LOW_DFLT=H5F_LOW_SEC2'
+# 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'}
 
-# 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 the width required by printf() to print type `long
+# long'.  For instance, if the format would be `%lld' then set it to
+# `ll' or if the format would be `%qd' set it to `q'.
+#hdf5_cv_printf_ll=${hdf5_cv_printf_ll='ll'}
diff --git a/config/irix5.3 b/config/irix5.3
index e24bd25..acc375e 100644
--- a/config/irix5.3
+++ b/config/irix5.3
@@ -1,13 +1,50 @@
-#!/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.
 
-CC="cc"
 
-# -woff 799	about long long type non-standard
+#----------------------------------------------------------------------------
+# 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.
 
-RANLIB=:		# SGI does not use ranlib
+# 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=cc
+RANLIB=:
+
+# What must *always* be present for things to compile correctly?
+CFLAGS="$CFLAGS -ansi -fullwarn -woff 799"
+#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'}
+
+# Set this to the width required by printf() to print type `long
+# long'.  For instance, if the format would be `%lld' then set it to
+# `ll' or if the format would be `%qd' set it to `q'.
+#hdf5_cv_printf_ll=${hdf5_cv_printf_ll='ll'}
 
-# Don't set CFLAGS if the user already did.
-if test -z "$CFLAGS"; then
-   CFLAGS="-ansi -fullwarn -woff 799"
-fi