<div dir="ltr">It seems from the Trac notification I just received that you've determined that vpath is the issue.  I was not planning on committing any in-place build atrocities so I'm glad you tested that :-)<div><br></div><div>Jeff</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Sep 9, 2015 at 3:49 PM, Kenneth Raffenetti <span dir="ltr"><<a href="mailto:raffenet@mcs.anl.gov" target="_blank">raffenet@mcs.anl.gov</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">That's what I suspected. I have access to Intel 2016, but need our sysadmins to update the license server to activate it. In the meantime, I can try to fake an env that can build F08 and find the underlying problem. It looks like you were doing a vpath build...does an in-tree build succeed?<br>
<br>
Ken<span class=""><br>
<br>
On 09/09/2015 05:43 PM, Jeff Hammond wrote:<br>
</span><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">
You are right.  GCC 5.2 contains no references to F08, presumably<br>
because configure determined that F08 was not supported.  I assume ifort<br>
16 tested positive for F08.<br>
<br>
I think you can download Intel 16 but if you have any trouble, let me<br>
know offline and I'll help figure it out.<br>
<br>
Jeff<br>
<br>
On Wed, Sep 9, 2015 at 3:40 PM, Kenneth Raffenetti <<a href="mailto:raffenet@mcs.anl.gov" target="_blank">raffenet@mcs.anl.gov</a><br></span><div><div class="h5">
<mailto:<a href="mailto:raffenet@mcs.anl.gov" target="_blank">raffenet@mcs.anl.gov</a>>> wrote:<br>
<br>
    Did the GCC 5.2 build actually build the F08 module? I suspect it<br>
    might have been disabled at configure time. That is, is there an<br>
    mpi_f08.mod file in the installed include dir?<br>
<br>
<br>
    On 09/09/2015 12:58 PM, Jeff Hammond wrote:<br>
<br>
        I cannot configure MPICH due to any F08-related issue.  I ran<br>
        autogen.sh<br>
        twice just to be darn sure I wasn't making that mistake again.<br>
<br>
        This is with the latest MPICH git master.  I am using Intel<br>
        Fortran 16<br>
        on Mac Yosemite.  The GCC 5.2 build was fine so this might be<br>
        related to<br>
        ifort, but it's not obvious why.<br>
<br>
        Thanks,<br>
<br>
        Jeff<br>
<br>
<br>
        This is how I attempted to configure:<br>
<br>
        jrhammon-mac01:build jrhammon$ head config.log<br>
        This file contains any messages produced by compilers while<br>
        running configure, to aid debugging if configure makes a mistake.<br>
<br>
        It was created by MPICH configure 3.2rc1, which was<br>
        generated by GNU Autoconf 2.69.  Invocation command line was<br>
<br>
            $ ../configure CC=icc CXX=icpc FC=ifort F77=ifort --enable-cxx<br>
        --enable-fortran --enable-threads=runtime --enable-g=dbg<br>
        --with-pm=hydra<br>
        --prefix=/opt/mpich/dev/intel/default --enable-wrapper-rpath<br>
        --enable-static --enable-shared<br>
<br>
        Here is the error:<br>
<br>
        Configuration completed.<br>
            MOD<br>
        src/binding/fortran/use_mpi_f08/mpi_c_interface_types.stamp<br>
            MOD      src/binding/fortran/use_mpi_f08/mpi_f08_types.stamp<br>
        ifort: error #10236: File not found:<br>
           'src/binding/fortran/use_mpi_f08/mpi_f08_types.f90'<br>
        ifort: command line error: no files specified; for help type<br>
        "ifort -help"<br>
        make: *** [src/binding/fortran/use_mpi_f08/mpi_f08_types.stamp]<br>
        Error 1<br>
<br>
<br>
        --<br>
        Jeff Hammond<br>
        <a href="mailto:jeff.science@gmail.com" target="_blank">jeff.science@gmail.com</a> <mailto:<a href="mailto:jeff.science@gmail.com" target="_blank">jeff.science@gmail.com</a>><br></div></div>
        <mailto:<a href="mailto:jeff.science@gmail.com" target="_blank">jeff.science@gmail.com</a> <mailto:<a href="mailto:jeff.science@gmail.com" target="_blank">jeff.science@gmail.com</a>>><span class=""><br>
        <a href="http://jeffhammond.github.io/" rel="noreferrer" target="_blank">http://jeffhammond.github.io/</a><br>
<br>
<br>
        _______________________________________________<br>
        To manage subscription options or unsubscribe:<br>
        <a href="https://lists.mpich.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">https://lists.mpich.org/mailman/listinfo/devel</a><br>
<br>
    _______________________________________________<br>
    To manage subscription options or unsubscribe:<br>
    <a href="https://lists.mpich.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">https://lists.mpich.org/mailman/listinfo/devel</a><br>
<br>
<br>
<br>
<br>
--<br>
Jeff Hammond<br>
<a href="mailto:jeff.science@gmail.com" target="_blank">jeff.science@gmail.com</a> <mailto:<a href="mailto:jeff.science@gmail.com" target="_blank">jeff.science@gmail.com</a>><br>
<a href="http://jeffhammond.github.io/" rel="noreferrer" target="_blank">http://jeffhammond.github.io/</a><br>
<br>
<br>
_______________________________________________<br>
To manage subscription options or unsubscribe:<br>
<a href="https://lists.mpich.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">https://lists.mpich.org/mailman/listinfo/devel</a><br>
<br>
</span></blockquote><div class="HOEnZb"><div class="h5">
_______________________________________________<br>
To manage subscription options or unsubscribe:<br>
<a href="https://lists.mpich.org/mailman/listinfo/devel" rel="noreferrer" target="_blank">https://lists.mpich.org/mailman/listinfo/devel</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature">Jeff Hammond<br><a href="mailto:jeff.science@gmail.com" target="_blank">jeff.science@gmail.com</a><br><a href="http://jeffhammond.github.io/" target="_blank">http://jeffhammond.github.io/</a></div>
</div>