summaryrefslogtreecommitdiffstats
path: root/fortran
diff options
context:
space:
mode:
authorElena Pourmal <epourmal@hdfgroup.org>2001-06-21 17:40:37 (GMT)
committerElena Pourmal <epourmal@hdfgroup.org>2001-06-21 17:40:37 (GMT)
commit4abe81ec2080f0ab46c0e319b8cb0a2cf240dc8f (patch)
treeb718fc105f70b7f0609777a2ca962f19b634f6c9 /fortran
parentf42aab2397c9c02e8f5b3817f153111063ff4208 (diff)
downloadhdf5-4abe81ec2080f0ab46c0e319b8cb0a2cf240dc8f.zip
hdf5-4abe81ec2080f0ab46c0e319b8cb0a2cf240dc8f.tar.gz
hdf5-4abe81ec2080f0ab46c0e319b8cb0a2cf240dc8f.tar.bz2
[svn-r4040]
Purpose: Bug bypass Description: Fortran configure checks flags where to find F90 modules in the order "M", "I" and "p". On IBM SP "M" is a reserved flag, configure does not understand compiler's warning and uses it to specify module directories. Then tests and examples compilation fails since module directory is not specified correctly on the compilation line. Solution: Changed the order of flags to be "I", "M", "p", so configure on IBM SP finds the correct flag first. Platforms tested: IBM SP, Solaris 2.7, Linux, DEC UNIX, HP 11.00, IRIX64 (yes, all of them :-)
Diffstat (limited to 'fortran')
-rwxr-xr-xfortran/configure2
1 files changed, 1 insertions, 1 deletions
diff --git a/fortran/configure b/fortran/configure
index c0c2d2f..ac8ef21 100755
--- a/fortran/configure
+++ b/fortran/configure
@@ -1935,7 +1935,7 @@ cd ..
echo $ac_n "checking how $F9X finds modules""... $ac_c" 1>&6
echo "configure:1937: checking how $F9X finds modules" >&5
-for flag in "-M" "-I" "-p"; do
+for flag in "-I" "-M" "-p"; do
cat >conftest.$ac_ext <<EOF
program conftest
use module