mirror of
https://github.com/HDFGroup/hdf5.git
synced 2024-12-27 08:01:04 +08:00
7ec079a515
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.
96 lines
3.0 KiB
Bash
96 lines
3.0 KiB
Bash
# -*- shell-script -*-
|
|
#
|
|
# Copyright by The HDF Group.
|
|
# Copyright by the Board of Trustees of the University of Illinois.
|
|
# All rights reserved.
|
|
#
|
|
# This file is part of HDF5. The full HDF5 copyright notice, including
|
|
# terms governing use, modification, and redistribution, is contained in
|
|
# the files COPYING and Copyright.html. COPYING can be found at the root
|
|
# of the source code distribution tree; Copyright.html can be found at the
|
|
# root level of an installed copy of the electronic HDF5 document set and
|
|
# is linked from the top-level documents page. It can also be found at
|
|
# http://hdfgroup.org/HDF5/doc/Copyright.html. If you do not have
|
|
# access to either file, you may request a copy from help@hdfgroup.org.
|
|
|
|
|
|
# This file should be sourced into configure if the compiler is the
|
|
# Intel ifort compiler or a derivative. It is careful not to do anything
|
|
# if the compiler is not Intel; otherwise `f9x_flags_set' is set to `yes'
|
|
#
|
|
|
|
# Get the compiler version in a way that works for ifort
|
|
# ifort unless a compiler version is already known
|
|
#
|
|
# f9x_vendor: The compiler name: ifort
|
|
# f9x_version: Version number: 8.0
|
|
#
|
|
if test X = "X$f9x_flags_set"; then
|
|
f9x_version="`$FC $FCFLAGS $H5_FCFLAGS -V 2>&1 |grep '^Intel'`"
|
|
if test X != "X$f9x_version"; then
|
|
f9x_vendor=ifort
|
|
f9x_version="`echo $f9x_version |sed 's/.*Version \([-a-z0-9\.\-]*\).*/\1/'`"
|
|
echo "compiler '$FC' is Intel $f9x_vendor-$f9x_version"
|
|
|
|
# Some version numbers
|
|
# Intel version numbers are of the form: "major.minor"
|
|
f9x_vers_major=`echo $f9x_version | cut -f1 -d.`
|
|
f9x_vers_minor=`echo $f9x_version | cut -f2 -d.`
|
|
#f9x_vers_patch=`echo $f9x_version | cut -f2 -d.`
|
|
test -n "$f9x_vers_major" || f9x_vers_major=0
|
|
test -n "$f9x_vers_minor" || f9x_vers_minor=0
|
|
test -n "$f9x_vers_patch" || f9x_vers_patch=0
|
|
f9x_vers_all=`expr $f9x_vers_major '*' 1000000 + $f9x_vers_minor '*' 1000 + $f9x_vers_patch`
|
|
fi
|
|
fi
|
|
|
|
# Common Intel flags for various situations
|
|
if test "X-ifort" = "X-$f9x_vendor"; then
|
|
# Insert section about version specific problems from gnu-flags here, if
|
|
# necessary.
|
|
|
|
arch=
|
|
# Architecture-specific flags
|
|
# Nothing currently. (Uncomment code below and modify to add any)
|
|
#case "$host_os-$host_cpu" in
|
|
# *-i686)
|
|
# arch="-march=i686"
|
|
# ;;
|
|
#esac
|
|
|
|
# Host-specific flags
|
|
# Nothing currently. (Uncomment code below and modify to add any)
|
|
#case "`hostname`" in
|
|
# sleipnir.ncsa.uiuc.edu)
|
|
# arch="$arch -pipe"
|
|
# ;;
|
|
#esac
|
|
|
|
# General
|
|
FC_BASENAME=ifort
|
|
F9XSUFFIXFLAG=""
|
|
FSEARCH_DIRS=""
|
|
H5_FCFLAGS="$H5_FCFLAGS"
|
|
|
|
# Production
|
|
PROD_FCFLAGS="-O3"
|
|
|
|
# Debug
|
|
DEBUG_FCFLAGS="-g -check all"
|
|
|
|
# Profile
|
|
# Use this for profiling with gprof
|
|
PROFILE_FCFLAGS="-g -p"
|
|
|
|
# Flags are set
|
|
f9x_flags_set=yes
|
|
fi
|
|
|
|
# Clear f9x info if no flags set
|
|
if test "X-$f9x_flags_set" = "X-"; then
|
|
f9x_vendor=
|
|
f9x_version=
|
|
fi
|
|
|
|
|