summaryrefslogtreecommitdiffstats
path: root/c++/Makefile.in
diff options
context:
space:
mode:
authorJames Laird <jlaird@hdfgroup.org>2005-04-04 21:17:51 (GMT)
committerJames Laird <jlaird@hdfgroup.org>2005-04-04 21:17:51 (GMT)
commitb296a419c4ed2cc43cab53b78a40cbf1346f2362 (patch)
tree7a652352898be1a2e963c9e700228c00a878657d /c++/Makefile.in
parent7f5e1dfe31696bddb3967865af52801a2b38bb7e (diff)
downloadhdf5-b296a419c4ed2cc43cab53b78a40cbf1346f2362.zip
hdf5-b296a419c4ed2cc43cab53b78a40cbf1346f2362.tar.gz
hdf5-b296a419c4ed2cc43cab53b78a40cbf1346f2362.tar.bz2
[svn-r10534] Purpose:
Configuration feature Description: Different Fortran compilers mangle function names in different ways (upper case, lower case, adding underscores). To link between Fortran and C functions, we need to know what a given function's name is under a given compiler. Solution: Use autoconf's FC_WRAPPERS check to determine the Fortran naming scheme and define the FC_FUNC_ macro to name our functions (in H5f90proto.h). Removed references to our old FNAME macro, as well as flags that indicated whether function names were upper or lower case. Platforms tested: mir, pommier, modi4, copper, more
Diffstat (limited to 'c++/Makefile.in')
-rw-r--r--c++/Makefile.in1
1 files changed, 1 insertions, 0 deletions
diff --git a/c++/Makefile.in b/c++/Makefile.in
index 76a81f0..403bfba 100644
--- a/c++/Makefile.in
+++ b/c++/Makefile.in
@@ -135,6 +135,7 @@ F9XMODFLAG = @F9XMODFLAG@
F9XSUFFIXFLAG = @F9XSUFFIXFLAG@
FC = @FC@
FCFLAGS = @FCFLAGS@
+FCLIBS = @FCLIBS@
FFLAGS = @FFLAGS@
FILTERS = @FILTERS@
FSEARCH_DIRS = @FSEARCH_DIRS@