From c06b0170f7e26b5c7719081871e0a98699b7a7b5 Mon Sep 17 00:00:00 2001
From: Allen Byrne <byrn@hdfgroup.org>
Date: Fri, 20 Sep 2013 15:36:57 -0500
Subject: [svn-r24180] HDFFV-8321:Add note about changing FFLAGS to FCFLAGS in
 configure. Merged INSTALL and h5fc.in from trunk.

---
 fortran/src/h5fc.in      | 24 ++++++++++++------------
 release_docs/INSTALL     |  4 ++--
 release_docs/RELEASE.txt |  1 +
 3 files changed, 15 insertions(+), 14 deletions(-)

diff --git a/fortran/src/h5fc.in b/fortran/src/h5fc.in
index 2e29e72..b220e8b 100644
--- a/fortran/src/h5fc.in
+++ b/fortran/src/h5fc.in
@@ -36,15 +36,15 @@ HL="@HL@"
 ##                                                                        ##
 ## (Advanced usage - know what you're doing - you're on your own here.)   ##
 ## The three variables below can be used to insert paths and flags in     ##
-## FFLAGS, LDFLAGS, or LIBS in the h5fc compile line:                     ##
-##    $FLINKER $FFLAGS $H5BLD_FFLAGS $F9XSUFFIXFLAG $LDFLAGS $LIBS        ##
+## FCFLAGS, LDFLAGS, or LIBS in the h5fc compile line:                    ##
+##    $FLINKER $FCFLAGS $H5BLD_FCFLAGS $F9XSUFFIXFLAG $LDFLAGS $LIBS      ##
 ##    $fmodules $link_objs $link_args $shared_link                        ##
 ##                                                                        ##
-## These settings can be overriden by setting HDF5_FFLAGS,                ##
+## These settings can be overriden by setting HDF5_FCFLAGS,               ##
 ## HDF5_LDFLAGS, or HDF5_LIBS in the environment.                         ##
 ##                                                                        ##
 ############################################################################
-FFLAGSBASE=""
+FCFLAGSBASE=""
 LDFLAGSBASE=""
 LIBSBASE=""
 
@@ -77,15 +77,15 @@ SHOW="eval"
 FCBASE="@FC@"
 FLINKERBASE="@FC@"
 
-# FFLAGS and LDFLAGS are reserved for use by the script user.  
+# FCFLAGS and LDFLAGS are reserved for use by the script user.  
 # FLAGS brought from the hdf5 build are put in H5BLD_*FLAGS.
 
-# User's FFLAGS come after their H5BLD counterparts. User's LDFLAGS come just 
+# User's FCFLAGS come after their H5BLD counterparts. User's LDFLAGS come just 
 # before clibpath, user's LIBS come after $link_objs and before the hdf5 
 # libraries in $link_args, followed by any external library paths and libraries 
 # from AM_LDFLAGS, LDFLAGS, AM_LIBS or LIBS carried in from the hdf5 build.
 # The order of the flags is intended to give precedence to the user's flags.
-H5BLD_FFLAGS="@AM_FCFLAGS@ @FCFLAGS@"
+H5BLD_FCFLAGS="@AM_FCFLAGS@ @FCFLAGS@"
 F9XMODFLAG="@F9XMODFLAG@"
 F9XSUFFIXFLAG="@F9XSUFFIXFLAG@"
 H5BLD_LDFLAGS="@AM_LDFLAGS@ @LDFLAGS@"
@@ -93,7 +93,7 @@ H5BLD_LIBS="@LIBS@"
 
 FC="${HDF5_FC:-$FCBASE}"
 FLINKER="${HDF5_FLINKER:-$FLINKERBASE}"
-FFLAGS="${HDF5_FFLAGS:-$FFLAGSBASE}"
+FCFLAGS="${HDF5_FCFLAGS:-$FCFLAGSBASE}"
 LDFLAGS="${HDF5_LDFLAGS:-$LDFLAGSBASE}"
 LIBS="${HDF5_LIBS:-$LIBSBASE}"
 
@@ -130,7 +130,7 @@ usage() {
   echo " in the 'Things You Can Modify to Override...'" section of $prog_name
   echo " "
   echo "  Variable              Current value to be replaced"
-  echo "  HDF5_FFLAGS           \"$CFLAGSBASE\""
+  echo "  HDF5_FCFLAGS          \"$CFLAGSBASE\""
   echo "  HDF5_LDFLAGS          \"$LDFLAGSBASE\""
   echo "  HDF5_LIBS             \"$LIBSBASE\""
   echo " "
@@ -277,7 +277,7 @@ if test "x$do_compile" = "xyes"; then
   fi
 
 
-  $SHOW $FC $H5BLD_FFLAGS $FFLAGS ${F9XSUFFIXFLAG} ${fmodules} $compile_args
+  $SHOW $FC $H5BLD_FCFLAGS $FCFLAGS ${F9XSUFFIXFLAG} ${fmodules} $compile_args
   status=$?
 
   if test "$status" != "0"; then
@@ -348,12 +348,12 @@ if test "x$do_link" = "xyes"; then
   # module. It's okay if they're included twice in the compile line.
   link_args="$link_args $H5BLD_LDFLAGS $H5BLD_LIBS"
 
-  # User's FFLAGS come after their H5BLD counterparts. User's LDFLAGS come just 
+  # User's FCFLAGS come after their H5BLD counterparts. User's LDFLAGS come just 
   # before clibpath, user's LIBS come after $link_objs and before the hdf5 
   # libraries in $link_args, followed by any external library paths and libraries 
   # from AM_LDFLAGS, LDFLAGS, AM_LIBS or LIBS carried in from the hdf5 build.
   # The order of the flags is intended to give precedence to the user's flags.
-  $SHOW $FLINKER $FFLAGS $H5BLD_FFLAGS $F9XSUFFIXFLAG $LDFLAGS $fmodules $link_objs $LIBS $link_args $shared_link
+  $SHOW $FLINKER $FCFLAGS $H5BLD_FCFLAGS $F9XSUFFIXFLAG $LDFLAGS $fmodules $link_objs $LIBS $link_args $shared_link
   status=$?
 fi
 
diff --git a/release_docs/INSTALL b/release_docs/INSTALL
index df2632d..abf836b 100644
--- a/release_docs/INSTALL
+++ b/release_docs/INSTALL
@@ -263,10 +263,10 @@ CONTENTS
         To configure AIX 64-bit support including the Fortran and C++ APIs,
         (Note: need to set $AR to 'ar -X 64'.)
         Serial:
-            $ CFLAGS=-q64 FFLAGS=-q64 CXXFLAGS=-q64 AR='ar -X 64'\
+            $ CFLAGS=-q64 FCFLAGS=-q64 CXXFLAGS=-q64 AR='ar -X 64'\
               ./configure --enable-fortran
         Parallel: (C++ not supported with parallel)
-            $ CFLAGS=-q64 FFLAGS=-q64 AR='ar -X 64'\
+            $ CFLAGS=-q64 FCFLAGS=-q64 AR='ar -X 64'\
               ./configure --enable-fortran
 
 4.3.4. Additional compilation flags
diff --git a/release_docs/RELEASE.txt b/release_docs/RELEASE.txt
index 949e192..47b8cdd 100644
--- a/release_docs/RELEASE.txt
+++ b/release_docs/RELEASE.txt
@@ -57,6 +57,7 @@ New Features
 
     Configuration
     -------------
+    - Rename FFLAGS to FCFLAGS in configure (ADB 2013/08/13)
     - CMake can now package a compressed examples file, the default for 
       Windows binaries from HDF Group.  (ADB  - 2013/07/22)
     
-- 
cgit v0.12