<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#ffffff" text="#000000">
    Matthew,<br>
    <br>
    I found this check in configure.log I obtained for petsc-3.1-p7:<br>
    <br>
================================================================================<br>
    TEST checkFortranModuleInclude from
config.compilers(/cygdrive/d/Dev/petsc-3.1-p7/config/BuildSystem/config/compilers.py:1084)<br>
    TESTING: checkFortranModuleInclude from
    config.compilers(config/BuildSystem/config/compilers.py:1084)<br>
    &nbsp; Figures out what flag is used to specify the include path for
    Fortran modules<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Pushing language FC<br>
    sh: /cygdrive/d/Dev/petsc-3.1-p7/bin/win32fe/win32fe ifort -c -o
    conftest.o&nbsp; -MT -Z7 -fpp&nbsp; conftest.F <br>
    Executing: /cygdrive/d/Dev/petsc-3.1-p7/bin/win32fe/win32fe ifort -c
    -o conftest.o&nbsp; -MT -Z7 -fpp&nbsp; conftest.F <br>
    sh: <br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Pushing language FC<br>
    sh: /cygdrive/d/Dev/petsc-3.1-p7/bin/win32fe/win32fe ifort -c -o
    conftest.o -Iconfdir&nbsp; -MT -Z7 -fpp&nbsp; conftest.F <br>
    Executing: /cygdrive/d/Dev/petsc-3.1-p7/bin/win32fe/win32fe ifort -c
    -o conftest.o -Iconfdir&nbsp; -MT -Z7 -fpp&nbsp; conftest.F <br>
    sh: <br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Pushing language FC<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Popping language FC<br>
    sh: /cygdrive/d/Dev/petsc-3.1-p7/bin/win32fe/win32fe ifort&nbsp; -o
    conftest.exe&nbsp;&nbsp; -Iconfdir&nbsp; -MT -Z7 -fpp&nbsp; conftest.o configtest.o&nbsp; <br>
    Executing: /cygdrive/d/Dev/petsc-3.1-p7/bin/win32fe/win32fe ifort&nbsp;
    -o conftest.exe&nbsp;&nbsp; -Iconfdir&nbsp; -MT -Z7 -fpp&nbsp; conftest.o configtest.o&nbsp;
    <br>
    sh: LINK : D:\Dev\PETSC-~2.1-P\conftest.exe not found or not built
    by the last incremental link; performing full link<br>
    <br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp; compilers: Fortran module include flag -I found<br>
    &nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp;&nbsp; Popping language FC<br>
================================================================================<br>
    <br>
    The compiler I used is the same I use for petsc-3.2-p1. <br>
    The difference is in the paths where you try to build this tests. As
    far as I understand for petsc-3.1-p7 you used local directory and
    for petsc-3.2-p1 temp directory is used. <br>
    Could it be the reason?<br>
    <br>
    Regards,<br>
    Alexander<br>
    <br>
    On 15.09.2011 14:54, Matthew Knepley wrote:
    <blockquote
cite="mid:CAMYG4GkOVZUnRJCDHV9MZFdrgToKB7dgMwh=Q4uutQ+1TdY+Eg@mail.gmail.com"
      type="cite">
      <div class="gmail_quote">On Thu, Sep 15, 2011 at 2:49 AM,
        Alexander Grayver <span dir="ltr">&lt;<a moz-do-not-send="true"
            href="mailto:agrayver@gfz-potsdam.de">agrayver@gfz-potsdam.de</a>&gt;</span>
        wrote:<br>
        <blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
          0.8ex; border-left: 1px solid rgb(204, 204, 204);
          padding-left: 1ex;">
          Hello,<br>
          <br>
          I hope you are having nice day!<br>
          <br>
          I have been using petsc-3.1-p7 under windows for 6 months and
          now decided to get new version. I used my old configure line
          which was successful for petsc-3.1:<br>
          <br>
          ./config/configure.py --PETSC_DIR=/cygdrive/d/dev/petsc-3.2-p1
          --with-petsc-arch=cygwin-cxx-debug-fortran
          --with-fortran-interfaces=1 --with-cc='win32fe cl'
          --with-fc='win32fe ifort' &nbsp;--with-cxx='win32fe cl'
          --with-windows-graphics=0 --download-f-blas-lapack=1
          --with-precision=double --with-scalar-type=complex
          --with-clanguage=cxx --with-mpi-include="/cygdrive/d/Dev/HPC_2008_SDK/Include"
          --with-mpi-lib=["/cygdrive/d/Dev/HPC_2008_SDK/Lib/amd64/msmpi.lib","/cygdrive/d/Dev/HPC_2008_SDK/Lib/amd64/msmpifec.lib"]
          --useThreads=0<br>
          <br>
          But unfortunately it doesn't work properly anymore, even
          though my development environment has not been changed. The
          error is:<br>
          <br>
          *******************************************************************************<br>
          &nbsp; &nbsp; &nbsp; &nbsp; UNABLE to CONFIGURE with GIVEN OPTIONS &nbsp; &nbsp;(see
          configure.log for details):<br>
          -------------------------------------------------------------------------------<br>
          Cannot determine Fortran module include flag<br>
          <br>
          Please find configure.log attached.<br>
        </blockquote>
        <div><br>
        </div>
        <div>The problem here is that your Fortran compiler reports that
          is supports F90, but cannot</div>
        <div>locate modules using an include path. This will make parts
          of the PETSc build fail. Do you</div>
        <div>know what flag it uses? I try -I, -p, and -M.</div>
        <div><br>
        </div>
        <div>&nbsp; Thanks,</div>
        <div><br>
        </div>
        <div>&nbsp; &nbsp; &nbsp;Matt</div>
        <div>&nbsp;</div>
        <blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt
          0.8ex; border-left: 1px solid rgb(204, 204, 204);
          padding-left: 1ex;">
          Regards,<br>
          <font color="#888888">
            Alexander</font></blockquote>
      </div>
      -- <br>
      What most experimenters take for granted before they begin their
      experiments is infinitely more interesting than any results to
      which their experiments lead.<br>
      -- Norbert Wiener<br>
    </blockquote>
    <br>
  </body>
</html>