2003-04-03 00:50:58 +08:00
|
|
|
# -*- shell-script -*-
|
|
|
|
#
|
2007-02-15 06:29:52 +08:00
|
|
|
# Copyright by The HDF Group.
|
2005-10-21 22:54:41 +08:00
|
|
|
# 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
|
2005-10-29 04:28:20 +08:00
|
|
|
# root level of an installed copy of the electronic HDF5 document set and
|
2005-10-21 22:54:41 +08:00
|
|
|
# is linked from the top-level documents page. It can also be found at
|
2007-02-15 06:29:52 +08:00
|
|
|
# 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.
|
2005-10-21 22:54:41 +08:00
|
|
|
|
|
|
|
|
2003-04-03 00:50:58 +08:00
|
|
|
# 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.
|
|
|
|
|
2003-12-14 02:46:10 +08:00
|
|
|
# Use Intel C compiler by default (if it's available).
|
2006-08-29 19:19:11 +08:00
|
|
|
# Use mpicc for parallel by default.
|
|
|
|
if test "X$CC" = "X"; then
|
|
|
|
if test "X-$enable_parallel" = "X-yes"; then
|
|
|
|
CC=mpicc
|
|
|
|
CC_BASENAME=mpicc
|
|
|
|
elif which icc > /dev/null; then
|
|
|
|
CC=icc
|
|
|
|
CC_BASENAME=icc
|
|
|
|
fi
|
|
|
|
fi
|
|
|
|
|
|
|
|
# Define RUNPARALLEL if parallel mode is enabled or a parallel compiler used.
|
|
|
|
if test "X-$enable_parallel" = "X-yes" -o X-$CC_BASENAME = X-mpicc; then
|
2010-11-12 02:17:02 +08:00
|
|
|
RUNPARALLEL=${RUNPARALLEL="mpirun -np \$\${NPROCS:=6}"}
|
2003-04-03 00:50:58 +08:00
|
|
|
fi
|
|
|
|
|
|
|
|
#----------------------------------------------------------------------------
|
|
|
|
# Compiler flags. The CPPFLAGS values should not include package debug
|
|
|
|
# flags like `-DH5G_DEBUG' since these are added with the
|
2004-12-29 22:26:20 +08:00
|
|
|
# `--enable-debug' switch of configure.
|
2003-04-03 00:50:58 +08:00
|
|
|
|
|
|
|
case $CC_BASENAME in
|
2004-08-27 03:03:33 +08:00
|
|
|
ecc|icc)
|
2004-12-04 02:08:14 +08:00
|
|
|
. $srcdir/config/intel-flags
|
2004-07-16 06:45:29 +08:00
|
|
|
;;
|
|
|
|
|
|
|
|
gcc)
|
|
|
|
. $srcdir/config/gnu-flags
|
|
|
|
;;
|
|
|
|
|
|
|
|
*)
|
[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.
2009-10-08 23:17:30 +08:00
|
|
|
H5_CFLAGS="$H5_CFLAGS -ansi"
|
2004-07-16 06:45:29 +08:00
|
|
|
DEBUG_CFLAGS="-g"
|
|
|
|
DEBUG_CPPFLAGS=
|
|
|
|
PROD_CFLAGS="-O"
|
|
|
|
PROD_CPPFLAGS=
|
|
|
|
PROFILE_CFLAGS="-pg"
|
|
|
|
PROFILE_CPPFLAGS=
|
|
|
|
;;
|
2003-07-29 05:38:04 +08:00
|
|
|
esac
|
|
|
|
|
|
|
|
# The default Fortran 90 compiler
|
|
|
|
|
2003-08-05 02:27:57 +08:00
|
|
|
# Use Intel Fortran compiler by default.
|
2006-08-29 19:19:11 +08:00
|
|
|
if test X-$enable_fortran = X-yes -a "X-$FC" = "X-"; then
|
|
|
|
if test "X-$enable_parallel" = "X-yes"; then
|
|
|
|
FC=mpif90
|
|
|
|
else
|
|
|
|
FC="ifort"
|
|
|
|
fi
|
2003-08-05 02:27:57 +08:00
|
|
|
fi
|
|
|
|
|
[svn-r10158] Purpose:
Automake version upgrade
Description:
Upgraded automake version from 1.6.2 to 1.9.5.
Changed bin/reconfigure script to use automake 1.9.5.
Changed configure.in and Makefiles to use new FCFLAGS and FC variables
instead of FFLAGS and F9X.
Automake and configure should now do the lion's share of the work
supporting Fortran 9X; macros in acsite.m4 are now mostly unused (will
be cleaned later).
Altered how configure handles pmake; now root-level Makefile.in is
processed by bin/reconfigure to have a .MAKEFLAGS target, since
automake no longer allows us to define unused variables.
Configure now always checks for C++ compiler even if it is not
used, since automake thinks this is the Right Thing To Do and
will break otherwise.
Platforms tested:
Sol, copper, heping, mir, sleipnir, eirene, pommier, kelgia, modi4.
2005-03-08 01:57:27 +08:00
|
|
|
case $FC in
|
2004-11-24 04:48:06 +08:00
|
|
|
*efc|*ifort)
|
2003-07-29 05:38:04 +08:00
|
|
|
# this is for efc v7. Older efc do not work with these.
|
|
|
|
# -Vaxlib is for non-standard fortran calls like exit().
|
[svn-r10158] Purpose:
Automake version upgrade
Description:
Upgraded automake version from 1.6.2 to 1.9.5.
Changed bin/reconfigure script to use automake 1.9.5.
Changed configure.in and Makefiles to use new FCFLAGS and FC variables
instead of FFLAGS and F9X.
Automake and configure should now do the lion's share of the work
supporting Fortran 9X; macros in acsite.m4 are now mostly unused (will
be cleaned later).
Altered how configure handles pmake; now root-level Makefile.in is
processed by bin/reconfigure to have a .MAKEFLAGS target, since
automake no longer allows us to define unused variables.
Configure now always checks for C++ compiler even if it is not
used, since automake thinks this is the Right Thing To Do and
will break otherwise.
Platforms tested:
Sol, copper, heping, mir, sleipnir, eirene, pommier, kelgia, modi4.
2005-03-08 01:57:27 +08:00
|
|
|
MORE_FCFLAGS='-fpp -DDEC$=DEC_ -DMS$=MS_ -Vaxlib'
|
[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.
2009-10-08 23:17:30 +08:00
|
|
|
H5_FCFLAGS="$H5_FCFLAGS $MORE_FCFLAGS"
|
2003-07-29 05:38:04 +08:00
|
|
|
f9x_flags_set=yes
|
|
|
|
;;
|
|
|
|
|
|
|
|
*)
|
|
|
|
f9x_flags_set=yes
|
|
|
|
;;
|
2003-04-03 00:50:58 +08:00
|
|
|
esac
|
2003-07-29 05:38:04 +08:00
|
|
|
|
|
|
|
# The following is not right and need work.
|
|
|
|
if test "X$f9x_flags_set" = "X"; then
|
|
|
|
F9XSUFFIXFLAG=""
|
|
|
|
FSEARCH_DIRS=""
|
[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.
2009-10-08 23:17:30 +08:00
|
|
|
H5_FCFLAGS="$H5_FCFLAGS"
|
[svn-r10158] Purpose:
Automake version upgrade
Description:
Upgraded automake version from 1.6.2 to 1.9.5.
Changed bin/reconfigure script to use automake 1.9.5.
Changed configure.in and Makefiles to use new FCFLAGS and FC variables
instead of FFLAGS and F9X.
Automake and configure should now do the lion's share of the work
supporting Fortran 9X; macros in acsite.m4 are now mostly unused (will
be cleaned later).
Altered how configure handles pmake; now root-level Makefile.in is
processed by bin/reconfigure to have a .MAKEFLAGS target, since
automake no longer allows us to define unused variables.
Configure now always checks for C++ compiler even if it is not
used, since automake thinks this is the Right Thing To Do and
will break otherwise.
Platforms tested:
Sol, copper, heping, mir, sleipnir, eirene, pommier, kelgia, modi4.
2005-03-08 01:57:27 +08:00
|
|
|
DEBUG_FCFLAGS=""
|
|
|
|
PROD_FCFLAGS=""
|
|
|
|
PROFILE_FCFLAGS=""
|
2003-07-29 05:38:04 +08:00
|
|
|
f9x_flags_set=yes
|
|
|
|
fi
|
2004-08-06 07:02:26 +08:00
|
|
|
|
|
|
|
# The Default settings for C++
|
2005-05-26 23:29:45 +08:00
|
|
|
# Intel changed C++ compiler's name from "icc" to "icpc" in version 8.1
|
2004-08-06 07:02:26 +08:00
|
|
|
if test -z "$CXX"; then
|
2005-05-26 23:29:45 +08:00
|
|
|
CXX=icpc
|
|
|
|
CXX_BASENAME=icpc
|
2004-08-06 07:02:26 +08:00
|
|
|
fi
|
|
|
|
|
2004-08-27 03:03:33 +08:00
|
|
|
# A patch to make g++ getting the default settings.
|
|
|
|
# CXX_BASENAME should have been set in configure.
|
2004-12-04 02:08:14 +08:00
|
|
|
if test "X$CXX" = "Xg++"; then
|
2004-08-27 03:03:33 +08:00
|
|
|
CXX_BASENAME=g++
|
2004-12-04 02:08:14 +08:00
|
|
|
fi
|
2004-08-27 03:03:33 +08:00
|
|
|
|
2004-08-06 07:02:26 +08:00
|
|
|
|
|
|
|
case $CXX_BASENAME in
|
2004-08-27 03:03:33 +08:00
|
|
|
ecc|icc) # Intel compilers
|
|
|
|
# Default to C99 standard.
|
[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.
2009-10-08 23:17:30 +08:00
|
|
|
H5_CXXFLAGS="${H5_CXXFLAGS:--std=c99}"
|
2004-08-27 03:03:33 +08:00
|
|
|
DEBUG_CXXFLAGS="-g -w2 -Wall"
|
|
|
|
DEBUG_CPPFLAGS=
|
|
|
|
PROD_CXXFLAGS="" #Default optimization O2 is used
|
|
|
|
PROD_CPPFLAGS=
|
|
|
|
PROFILE_CXXFLAGS="-pg"
|
|
|
|
PROFILE_CPPFLAGS=
|
|
|
|
;;
|
2004-08-06 07:02:26 +08:00
|
|
|
g++)
|
[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.
2009-10-08 23:17:30 +08:00
|
|
|
H5_CXXFLAGS="$H5_CXXFLAGS -Wsign-compare" #Only works for some versions
|
2004-08-06 07:02:26 +08:00
|
|
|
DEBUG_CXXFLAGS="-g -fverbose-asm"
|
|
|
|
DEBUG_CPPFLAGS=
|
|
|
|
PROD_CXXFLAGS="-O3 -fomit-frame-pointer"
|
|
|
|
PROD_CPPFLAGS=
|
|
|
|
PROFILE_CXXFLAGS="-pg"
|
|
|
|
PROFILE_CPPFLAGS=
|
|
|
|
;;
|
|
|
|
|
|
|
|
*)
|
|
|
|
# Default to C99 standard.
|
[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.
2009-10-08 23:17:30 +08:00
|
|
|
H5_CXXFLAGS="${H5_CXXFLAGS:--std=c99}"
|
2004-08-27 03:03:33 +08:00
|
|
|
DEBUG_CXXFLAGS="-g"
|
2004-08-06 07:02:26 +08:00
|
|
|
DEBUG_CPPFLAGS=
|
2004-08-27 03:03:33 +08:00
|
|
|
PROD_CXXFLAGS="-O"
|
2004-08-06 07:02:26 +08:00
|
|
|
PROD_CPPFLAGS=
|
|
|
|
PROFILE_CXXFLAGS="-pg"
|
|
|
|
PROFILE_CPPFLAGS=
|
|
|
|
;;
|
|
|
|
esac
|