diff options
| author | Bill Wendling <wendling@ncsa.uiuc.edu> | 2001-01-18 20:33:56 (GMT) |
|---|---|---|
| committer | Bill Wendling <wendling@ncsa.uiuc.edu> | 2001-01-18 20:33:56 (GMT) |
| commit | 5104f10fed42b211b764d51be6ca45b182834e71 (patch) | |
| tree | 70d2c61373eaacc29c40b6d583761c6ac38689a9 /fortran/configure | |
| parent | 07319d804bd393eb670bd09cd3a906aba8c444fe (diff) | |
| download | hdf5-5104f10fed42b211b764d51be6ca45b182834e71.zip hdf5-5104f10fed42b211b764d51be6ca45b182834e71.tar.gz hdf5-5104f10fed42b211b764d51be6ca45b182834e71.tar.bz2 | |
[svn-r3298] Purpose:
Bug Fix
Description:
Small bug fix to the acsite.m4 stuff. We should check if the Fortran
9X compiler was found instead of the CC compiler.
Solution:
Changed CC to F9X macro.
Platforms tested:
Linux
Diffstat (limited to 'fortran/configure')
| -rwxr-xr-x | fortran/configure | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/fortran/configure b/fortran/configure index 005c144..530f67f 100755 --- a/fortran/configure +++ b/fortran/configure @@ -1770,7 +1770,7 @@ fi test -n "$F9X" && break done -test -z "$CC" && { echo "configure: error: no acceptable f9X compiler found in \$PATH" 1>&2; exit 1; } +test -z "$F9X" && { echo "configure: error: no acceptable f9X compiler found in \$PATH" 1>&2; exit 1; } echo $ac_n "checking whether the Fortran 9X compiler ($F9X $FFLAGS $LDFLAGS) works""... $ac_c" 1>&6 |