[petsc-users] Problems with last PETSC-3.2 release on Windows

[Alexander Grayver]

Thanks Matt,

I will that, but I use PETSC from Fortran so I need Fortran functionality.

Regards,
Alexander

On 15.09.2011 15:43, Matthew Knepley wrote:
> On Thu, Sep 15, 2011 at 8:01 AM, Alexander Grayver 
> <agrayver at gfz-potsdam.de <mailto:agrayver at gfz-potsdam.de>> wrote:
>
>     Matthew,
>
>     I found this check in configure.log I obtained for petsc-3.1-p7:
>
>     ================================================================================
>     TEST checkFortranModuleInclude from
>     config.compilers(/cygdrive/d/Dev/petsc-3.1-p7/config/BuildSystem/config/compilers.py:1084)
>     TESTING: checkFortranModuleInclude from
>     config.compilers(config/BuildSystem/config/compilers.py:1084)
>       Figures out what flag is used to specify the include path for
>     Fortran modules
>             Pushing language FC
>     sh: /cygdrive/d/Dev/petsc-3.1-p7/bin/win32fe/win32fe ifort -c -o
>     conftest.o  -MT -Z7 -fpp  conftest.F
>     Executing: /cygdrive/d/Dev/petsc-3.1-p7/bin/win32fe/win32fe ifort
>     -c -o conftest.o  -MT -Z7 -fpp  conftest.F
>     sh:
>             Pushing language FC
>     sh: /cygdrive/d/Dev/petsc-3.1-p7/bin/win32fe/win32fe ifort -c -o
>     conftest.o -Iconfdir  -MT -Z7 -fpp  conftest.F
>     Executing: /cygdrive/d/Dev/petsc-3.1-p7/bin/win32fe/win32fe ifort
>     -c -o conftest.o -Iconfdir  -MT -Z7 -fpp  conftest.F
>     sh:
>                     Pushing language FC
>                     Popping language FC
>     sh: /cygdrive/d/Dev/petsc-3.1-p7/bin/win32fe/win32fe ifort  -o
>     conftest.exe   -Iconfdir  -MT -Z7 -fpp  conftest.o configtest.o
>     Executing: /cygdrive/d/Dev/petsc-3.1-p7/bin/win32fe/win32fe ifort 
>     -o conftest.exe   -Iconfdir  -MT -Z7 -fpp  conftest.o configtest.o
>     sh: LINK : D:\Dev\PETSC-~2.1-P\conftest.exe not found or not built
>     by the last incremental link; performing full link
>
>           compilers: Fortran module include flag -I found
>             Popping language FC
>     ================================================================================
>
>     The compiler I used is the same I use for petsc-3.2-p1.
>     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.
>     Could it be the reason?
>
>
> That would be broken behavior from ifort, but I guess it is possible. 
> I will talk with Satish about how
> this should really be fixed. For right now, go to
>
>   config/BuildSystem/config/compilers.py
>
> to the checkFortranModuleInclude() function and comment out the last 
> two lines, which are killing the configure.
> Your build will break on the Fortran modules (I assume), but 
> everything else should work.
>
>   Thanks,
>
>       Matt
>
>     Regards,
>     Alexander
>
>
>     On 15.09.2011 14:54, Matthew Knepley wrote:
>>     On Thu, Sep 15, 2011 at 2:49 AM, Alexander Grayver
>>     <agrayver at gfz-potsdam.de <mailto:agrayver at gfz-potsdam.de>> wrote:
>>
>>         Hello,
>>
>>         I hope you are having nice day!
>>
>>         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:
>>
>>         ./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'  --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
>>
>>         But unfortunately it doesn't work properly anymore, even
>>         though my development environment has not been changed. The
>>         error is:
>>
>>         *******************************************************************************
>>                 UNABLE to CONFIGURE with GIVEN OPTIONS    (see
>>         configure.log for details):
>>         -------------------------------------------------------------------------------
>>         Cannot determine Fortran module include flag
>>
>>         Please find configure.log attached.
>>
>>
>>     The problem here is that your Fortran compiler reports that is
>>     supports F90, but cannot
>>     locate modules using an include path. This will make parts of the
>>     PETSc build fail. Do you
>>     know what flag it uses? I try -I, -p, and -M.
>>
>>       Thanks,
>>
>>          Matt
>>
>>         Regards,
>>         Alexander
>>
>>     -- 
>>     What most experimenters take for granted before they begin their
>>     experiments is infinitely more interesting than any results to
>>     which their experiments lead.
>>     -- Norbert Wiener
>
>
>
>
> -- 
> What most experimenters take for granted before they begin their 
> experiments is infinitely more interesting than any results to which 
> their experiments lead.
> -- Norbert Wiener

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-users/attachments/20110915/22d9755a/attachment-0001.htm>