summaryrefslogtreecommitdiffstats
path: root/config/intel-fflags
diff options
context:
space:
mode:
authorMike McGreevy <mamcgree@hdfgroup.org>2009-10-08 15:17:30 (GMT)
committerMike McGreevy <mamcgree@hdfgroup.org>2009-10-08 15:17:30 (GMT)
commit7ec079a5152761d3e972b2f52c3542f5ec38f89e (patch)
tree4f9693427882de9fda9a36512637a7a569b57a89 /config/intel-fflags
parent047ac8f136c58c373dbb0bf04963382ed8930334 (diff)
downloadhdf5-7ec079a5152761d3e972b2f52c3542f5ec38f89e.zip
hdf5-7ec079a5152761d3e972b2f52c3542f5ec38f89e.tar.gz
hdf5-7ec079a5152761d3e972b2f52c3542f5ec38f89e.tar.bz2
[svn-r17616] Purpose:
CFLAGS overhaul Description: Modified the way configure handles CFLAGS. (note: all changes also apply to FCFLAGS, CXXFLAGS, CPPFLAGS, and LDFLAGS). 1. The configure process will now always preserve a user's CFLAGS environment variable setup. Any additional flags necessary for compilation added at configure time will be passed into the Makefiles as AM_CFLAGS, which is an automake construct to be used in addition to CFLAGS. This will allow a user to have the final say, as CFLAGS will always appear later in the compile line than AM_CFLAGS. Additionally, setting CFLAGS during make will no longer completely erase all flags set by configure, since they're maintained in AM_CFLAGS. 2. Additionally, where possible, flags previously being assigned directly into CFLAGS (and thus propagating into h5cc) have now been redirected into H5_CFLAGS, so they're used ONLY for compiling hdf5, and not embedded into the h5cc wrapper script as well. *Note that H5_CFLAGS ultimately is assigned into AM_CFLAGS for use in the Makefiles. Complete description of changes and build process will be included in a Configure Document that Elena and I are working on. 3. Removed unsupported config files. This includes: config/dec-osf* config/hpux11.00 config/irix5.x config/powerpc-ibm-aix4.x config/rs6000-ibm-aix5.x config/unicos* 4. Modified configure summary to display additional values. Specifically, appropriate AM_* variables are being shown, as well as H5_FCFLAGS and H5_CXXFLAGS, which were for some reason not already present. Tested: - H5committest - Tested on all THG / NCSA machines, using several combinations of the more prominent configure options (c++, fortran, szip, threadsafe, parallel, et cetera). (Thanks to Quincey for rysnc testing setup!) - With regards to new automated testing, anything *necessary* for compilation will be caught by the daily tests as it stands now. (i.e., if LDFLAGS is not properly set when szip is used, linking will fail). Additionally, with regards to which flags get into h5cc, if any *necessary* flags have been improperly removed, then daily tests should fail during make installcheck. Additional machine-specific desired behaviors and/or checks may have to be set up separately within the daily tests, so this is something to work on.
Diffstat (limited to 'config/intel-fflags')
-rw-r--r--config/intel-fflags2
1 files changed, 1 insertions, 1 deletions
diff --git a/config/intel-fflags b/config/intel-fflags
index 998e569..3e33fc9 100644
--- a/config/intel-fflags
+++ b/config/intel-fflags
@@ -70,7 +70,7 @@ if test "X-ifort" = "X-$f9x_vendor"; then
FC_BASENAME=ifort
F9XSUFFIXFLAG=""
FSEARCH_DIRS=""
- FCFLAGS="$FCFLAGS"
+ H5_FCFLAGS="$H5_FCFLAGS"
# Production
PROD_FCFLAGS="-O3"