[mvapich-discuss] Intel Compilers and Fortran 2008 Support

Subramoni, Hari subramoni.1 at osu.edu
Mon Oct 1 09:26:38 EDT 2018


Dear, Christof.

This is good to know. Unfortunately, I have been backed up by a few other work items. I will get back to you on this issue by the end of this week.

Regards,
Hari.

-----Original Message-----
From: Christof Koehler <christof.koehler at bccms.uni-bremen.de> 
Sent: Monday, October 1, 2018 8:18 AM
To: Subramoni, Hari <subramoni.1 at osu.edu>
Cc: mvapich-discuss at cse.ohio-state.edu <mvapich-discuss at mailman.cse.ohio-state.edu>
Subject: Re: [mvapich-discuss] Intel Compilers and Fortran 2008 Support

Hello everybody,

after some (unrelated) delay I compiled that toolchain, ran "autogen.sh" after patching and can report that with all three compiler versions mentioned I now get "checking for Fortran 2008 support... yes".

Thank you very much for your support !

Did you dinf out if detection for ifort 2016 and 2017 should work with the mvapich2-2.3 release tarball as is ?

Best Regards

Christof

On Fri, Sep 21, 2018 at 01:28:08PM +0000, Subramoni, Hari wrote:
> Hi, Christof.
> 
> In case it makes things easier for you, you can use the script below to build them.
> 
> If you invoke it as <script_file_name.sh> $PWD, it will install 
> everything under $PWD/Tools/install-dir. You can then add 
> $PWD/Tools/install-dir/bin to $PATH and $PWD/Tools/install-dir/lib to 
> LD_LIBRARY_PATH and run autogen.sh
> 
> #!/bin/bash
> 
> #set -x
> 
> #Error checking
> if [ ! -n "$1" ]
> then
>     echo "Please pass the base dir and re-run script"
>     exit 1
> fi
> 
> base_dir="$1/Tools"
> 
> gnum4_path="$base_dir/GNUM4"
> autoconf_path="$base_dir/Autoconf"
> automake_path="$base_dir/Automake"
> libtool_path="$base_dir/Libtool"
> 
> install_dir="$base_dir/install-dir"
> 
> gnum4_version="m4-1.4.17"
> autoconf_version="autoconf-2.69"
> automake_version="automake-1.15"
> libtool_version="libtool-2.4.6"
> 
> gnum4_repo="http://ftp.gnu.org/gnu/m4/$gnum4_version.tar.gz"
> autoconf_repo="http://ftp.gnu.org/gnu/autoconf/$autoconf_version.tar.gz"
> automake_repo="http://ftp.gnu.org/gnu/automake/$automake_version.tar.gz"
> libtool_repo="https://ftp.gnu.org/gnu/libtool/$libtool_version.tar.gz"
> 
> error_print()
> {
>     step=$1
>     repo_name=$2
>     err_code=$3
>     if [ "$err_code" -ne "0" ]
>     then
>             echo "$step for $repo_name failed"
>             cd -
>             exit 1
>     else
>         if [ "$VERBOSE" == "1" ]
>         then
>                 echo "$step for $repo_name succeeded"
>         fi
>     fi
> }
> 
> install_library()
> {
>     repo=$1
>     repo_name=$2
>     local_path=$3
> 
>     cd $local_path
>     wget $repo >& /dev/null
>     error_print "wget" $repo_name $?
> 
>     tar -zxvf "$repo_name.tar.gz"  >& /dev/null
>     error_print "un-tar" $repo_name $?
> 
>     cd $repo_name
> 
>     ./configure --prefix=$install_dir >& /dev/null
>     error_print "configure" $repo_name $?
> 
>     make clean &> /dev/null
>     error_print "make clean" $repo_name $?
> 
>     make &> /dev/null
>     error_print "make" $repo_name $?
> 
>     make install &> /dev/null
>     error_print "make install" $repo_name $?
> 
>     cd - >& /dev/null
> }
> 
> mkdir -p $gnum4_path $autoconf_path $automake_path $libtool_path 
> $install_dir
> 
> #Install GNU M4
> install_library $gnum4_repo $gnum4_version $gnum4_path echo 
> "$gnum4_version installed successfully"
> 
> #Install Autoconf
> install_library $autoconf_repo $autoconf_version $autoconf_path echo 
> "$autoconf_version installed successfully"
> 
> #Install Libtool
> install_library $libtool_repo $libtool_version $libtool_path echo 
> "$libtool_version installed successfully"
> 
> #Install Automake
> install_library $automake_repo $automake_version $automake_path echo 
> "$automake_version installed successfully"
> 
> Thx,
> Hari.
> 
> -----Original Message-----
> From: Christof Koehler <christof.koehler at bccms.uni-bremen.de>
> Sent: Friday, September 21, 2018 8:55 AM
> To: Subramoni, Hari <subramoni.1 at osu.edu>
> Cc: mvapich-discuss at cse.ohio-state.edu 
> <mvapich-discuss at mailman.cse.ohio-state.edu>
> Subject: Re: [mvapich-discuss] Intel Compilers and Fortran 2008 
> Support
> 
> Hello,
> 
> On Fri, Sep 21, 2018 at 11:57:14AM +0000, Subramoni, Hari wrote:
> > Hello, Christof.
> > 
> > I think Fortran 2008 support was working with older Intel compilers. However, let me double check about that and get back to you. 
> Yes, that is confusing. 
> 
> > 
> > Did you do autogen.sh after applying the patch? If not, can you 
> > please try that? Note that you need the following versions of 
> > Autotools installed and available on your system to execute 
> > autogen.sh
> OK, this is the step I was missing. Thank you.
> 
> > 
> > gnum4_version="m4-1.4.17"
> > autoconf_version="autoconf-2.69"
> > automake_version="automake-1.15"
> > libtool_version="libtool-2.4.6"
> Centos7.4 does not have those versions apparently, it is on automake
> 1.13 for example. I will have to build the toolchain by hand then and make sure it is used over the system provided versions. That will take some time.
> I will report back with the result.
> 
> Thank you so far !
> 
> Best Regards
> 
> Christof
> 
> > 
> > You can download them from the following locations
> > 
> > gnum4_repo="http://ftp.gnu.org/gnu/m4/$gnum4_version.tar.gz"
> > autoconf_repo="http://ftp.gnu.org/gnu/autoconf/$autoconf_version.tar.gz"
> > automake_repo="http://ftp.gnu.org/gnu/automake/$automake_version.tar.gz"
> > libtool_repo="https://ftp.gnu.org/gnu/libtool/$libtool_version.tar.gz"
> > 
> > Regards,
> > Hari.
> > 
> > -----Original Message-----
> > From: mvapich-discuss-bounces at cse.ohio-state.edu On Behalf Of 
> > Christof Koehler
> > Sent: Friday, September 21, 2018 7:27 AM
> > To: mvapich-discuss at cse.ohio-state.edu
> > <mvapich-discuss at mailman.cse.ohio-state.edu>
> > Subject: [mvapich-discuss] Intel Compilers and Fortran 2008 Support
> > 
> > Hello everybody,
> > 
> > there was a previous thread on the list concerning detection of 
> > Fortran
> > 2008 support when building mvapich2 2.3 with Intel compilers:
> > http://mailman.cse.ohio-state.edu/pipermail/mvapich-discuss/2018-Aug
> > us
> > t/006704.html
> > 
> > I am a bit confused now, may be someone could clarify the following:
> > 
> > Using the stock mvapich2-2.3.tar.gz I observe that Fortran 2008 capability of the compiler is neither detected with ifort 16.0.4 nor ifort 17.0.5:
> > 
> > # ifort -v
> > ifort version 16.0.4
> > # CC=icc FC=ifort F77=ifort CXX=icpc ./configure --enable-fast=O1 
> > --enable-fortran=all --with-device=ch3:psm  --enable-option-checking
> > 2>&1  |grep 2008 checking for Fortran 2008 support... no # ifort -v
> > ifort version 17.0.5 # CC=icc FC=ifort F77=ifort CXX=icpc  
> > ./configure
> > --enable-fast=O1 --enable-fortran=all --with-device=ch3:psm 
> > --enable-option-checking 2>&1  |grep 2008 checking for Fortran 2008 
> > support... no
> > 
> > From the previous thread I assumed that even without the patch 
> > Fortran
> > 2008 should be detected correctly using these compilers, but may be I misunderstood what the expected behaviour was ?
> > 
> > Remark: Using mvapich2 2.2 together with the 16.0.4 compiler the 
> > Fortran
> > 2008 support is correctly detected as "yes".
> > 
> > Further, I tried to apply the patch to aclocal_fc.m4 but without success. Using both the ifort 17.0.5 compiler and the ifort 18.0.3 I still get a "checking for Fortran 2008 support... no"
> > although configure apparently succeeds, last output is "Configuration completed."
> > 
> > But a subsequent make gives
> > # make
> > CDPATH="${ZSH_VERSION+.}:" && cd . && /bin/sh 
> > /usr/src/mvapich2-2.3/confdb/missing aclocal-1.15 -I confdb
> > /usr/src/mvapich2-2.3/confdb/missing: line 81: aclocal-1.15: command 
> > not found
> > WARNING: 'aclocal-1.15' is missing on your system.
> >          You should only need it if you modified 'acinclude.m4' or
> >          'configure.ac' or m4 files included by 'configure.ac'.
> >          The 'aclocal' program is part of the GNU Automake package:
> >          <http://www.gnu.org/software/automake>
> >          It also requires GNU Autoconf, GNU m4 and Perl in order to run:
> >          <http://www.gnu.org/software/autoconf>
> >          <http://www.gnu.org/software/m4/>
> >          <http://www.perl.org/>
> > make: *** [aclocal.m4] Error 127
> > Running "aclocal" in the top directory which contains configure.ac does not seem to have any effect at all.
> > 
> > From that I would assume (my experience is nonexistent) that I have to regenerate parts of the configure machinery after patching the file in another way. A hint how to do that would be appreciated.
> > The OS is Centos7.4 with automake 1.13.4-3.el7.
> > 
> > 
> > Best Regards
> > 
> > Christof
> > 
> > _______________________________________________
> > mvapich-discuss mailing list
> > mvapich-discuss at cse.ohio-state.edu
> > http://mailman.cse.ohio-state.edu/mailman/listinfo/mvapich-discuss
> 
> -- 
> Dr. rer. nat. Christof Köhler       email: c.koehler at bccms.uni-bremen.de
> Universitaet Bremen/FB1/BCCMS       phone:  +49-(0)421-218-62334
> Am Fallturm 1/ TAB/ Raum 3.12       fax: +49-(0)421-218-62770
> 28359 Bremen
> 
> PGP: http://www.bccms.uni-bremen.de/cms/people/c_koehler/



More information about the mvapich-discuss mailing list