hdf5/config/freebsd
Quincey Koziol 7a9cd4ac49 [svn-r10787] Purpose:
Bug fix

Description:
    Accommodate the GNU C++ compiler.

Platforms tested:
    FreeBSD 4.11 (sleipnir) w/CC=g++
    Not tested by h5committest
2005-05-23 15:39:54 -05:00

77 lines
2.0 KiB
Bash

# -*- 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.
#
# See BlankForm in this directory for details.
# The default compiler is `gcc'
if test "X-" = "X-$CC"; then
CC=gcc
CC_BASENAME=gcc
fi
# Add "_XOPEN_SOURCE" define to cpp flags, to quiet warnings
# from /usr/include/sys/cdefs.h
# (Unless we are using g++ as a C compiler)
if test "X-g++" != "X-$CC"; then
CPPFLAGS="$CPPFLAGS -D_XOPEN_SOURCE=600"
fi
# Figure out C compiler flags
. $srcdir/config/gnu-flags
# Figure out Intel C compiler flags
. $srcdir/config/intel-flags
# The default Fortran 90 compiler
if test "X-" = "X-$FC"; then
case $CC_BASENAME in
gcc*|pgcc*)
FC=gfortran40
FC_BASENAME=gfortran40
;;
icc*)
FC=ifort
FC_BASENAME=ifort
;;
mpicc*)
FC=mpif90
FC_BASENAME=mpif90
;;
esac
fi
#
# HDF5 FORTRAN integers
#
# R_LARGE is the number of digits for the bigest integer supported.
# R_INTEGER is the number of digits in INTEGER
#
R_LARGE=18
R_INTEGER=9
HADDR_T='SELECTED_INT_KIND(R_LARGE)'
HSIZE_T='SELECTED_INT_KIND(R_LARGE)'
HSSIZE_T='SELECTED_INT_KIND(R_LARGE)'
HID_T='SELECTED_INT_KIND(R_INTEGER)'
SIZE_T='SELECTED_INT_KIND(R_INTEGER)'
OBJECT_NAMELEN_DEFAULT_F=-1
# Figure out FORTRAN compiler flags
. $srcdir/config/gnu-fflags
# Figure out Intel F90 compiler flags
. $srcdir/config/intel-fflags
# Special setup to use pthread support if enable-threadsafe is on.
# Works with static executable only.
if test "X-" != "X-$enable_threadsafe"; then
CFLAGS="$CFLAGS -D_THREAD_SAFE"
CXXFLAGS="$CXXFLAGS -D_THREAD_SAFE"
LDFLAGS="$LDFLAGS -pthread"
fi
# Temporarily hard set this variable. The problem of loss of the last 2 bytes of mantissa
# turns out to be elusive. Hard set it until a better solution is found.
hdf5_cv_ullong_to_ldouble_precision_works=${hdf5_cv_ullong_to_ldouble_precision_works='no'}