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

Alexander Grayver agrayver at gfz-potsdam.de
Fri Sep 16 07:40:07 CDT 2011 

Satish,

A also have 10.1:

alex at group /cygdrive/d/dev/petsc-3.2-p1
# ifort
Intel(R) Visual Fortran Compiler for applications running on Intel(R) 
64, Version 10.1    Build 20080801 Package ID: w_fc_p_10.1.025
Copyright (C) 1985-2008 Intel Corporation.  All rights reserved.

Regards,
Alexander

On 16.09.2011 14:33, Satish Balay wrote:
> Could you tell us - which version of ifort you have? Its strange
> that this test works for me [with ifort 10.1] - but not for you.
>
> Satish
>
> On Fri, 16 Sep 2011, Alexander Grayver wrote:
>
>> Satish,
>>
>> Thanks a lot! The configure and make stages work well now.
>>
>> Regards,
>> Alexander
>>
>> On 15.09.2011 19:19, Satish Balay wrote:
>>> Looks like its related to the the commenting out of the lines [and the
>>> failed test before that].
>>>
>>> After the commented lines - try adding:
>>>       self.setCompilers.fortranModuleIncludeFlag = '-I'
>>>
>>> Satish
>>>
>>> On Thu, 15 Sep 2011, Alexander Grayver wrote:
>>>
>>>> Satish,
>>>>
>>>> It is reproducible.
>>>> So that is the nasty error, I don't know where to look for solution.
>>>> Anyway, I commented these lines in compiler.py as Matt suggested:
>>>>       #if not found:
>>>>       #  raise RuntimeError('Cannot determine Fortran module include flag')
>>>>
>>>> And configure fails further down, but I suspect that this new error is
>>>> also
>>>> somehow linked to the relative paths (seen log attached). Can you
>>>> confirmthis?
>>>>
>>>> Regards,
>>>> Alexander
>>>>
>>>> On 15.09.2011 16:48, Satish Balay wrote:
>>>>> I just ran petsc-32 with ifort - and it ran fine. So I'm not sure
>>>>> whats hapenning in this case..
>>>>>
>>>>> Is this error reproduceable [if configure is rerun with the same
>>>>> options?]
>>>>>
>>>>> Satish
>>>>>
>>>>>
>>>>> Intel(R) Visual Fortran Compiler for applications running on Intel(R)
>>>>> 64,
>>>>> Version 10.1    Build 20080212 Package ID: w_fc_p_10.1.019
>>>>>
>>>>> ================================================================================
>>>>> TEST checkFortranModuleInclude from
>>>>> config.compilers(/home/balay/petsc-3.2/config/BuildSystem/config/compilers.py:1155)
>>>>> TESTING: checkFortranModuleInclude from
>>>>> config.compilers(config/BuildSystem/config/compilers.py:1155)
>>>>>      Figures out what flag is used to specify the include path for
>>>>> Fortran
>>>>> modules
>>>>>              Pushing language FC
>>>>> sh: /home/balay/petsc-3.2/bin/win32fe/win32fe ifort -c -o
>>>>> /tmp/petsc-zRoAJW/config.compilers/conftest.o
>>>>> -I/tmp/petsc-zRoAJW/config.compilers
>>>>> -I/tmp/petsc-zRoAJW/config.setCompilers
>>>>> -MT -Z7 -fpp  /tmp/petsc-zRoAJW/config.compilers/conftest.F
>>>>> Executing: /home/balay/petsc-3.2/bin/win32fe/win32fe ifort -c -o
>>>>> /tmp/petsc-zRoAJW/config.compilers/conftest.o
>>>>> -I/tmp/petsc-zRoAJW/config.compilers
>>>>> -I/tmp/petsc-zRoAJW/config.setCompilers
>>>>> -MT -Z7 -fpp  /tmp/petsc-zRoAJW/config.compilers/conftest.F
>>>>> sh:
>>>>> Successful compile:
>>>>> Source:
>>>>>          module configtest
>>>>>          integer testint
>>>>>          parameter (testint = 42)
>>>>>          end module configtest
>>>>>              Pushing language FC
>>>>> sh: /home/balay/petsc-3.2/bin/win32fe/win32fe ifort -c -o
>>>>> /tmp/petsc-zRoAJW/config.compilers/conftest.o
>>>>> -I/tmp/petsc-zRoAJW/config.compilers
>>>>> -I/tmp/petsc-zRoAJW/config.setCompilers
>>>>> -I/tmp/petsc-zRoAJW/config.compilers/confdir  -MT -Z7 -fpp
>>>>> /tmp/petsc-zRoAJW/config.compilers/conftest.F
>>>>> Executing: /home/balay/petsc-3.2/bin/win32fe/win32fe ifort -c -o
>>>>> /tmp/petsc-zRoAJW/config.compilers/conftest.o
>>>>> -I/tmp/petsc-zRoAJW/config.compilers
>>>>> -I/tmp/petsc-zRoAJW/config.setCompilers
>>>>> -I/tmp/petsc-zRoAJW/config.compilers/confdir  -MT -Z7 -fpp
>>>>> /tmp/petsc-zRoAJW/config.compilers/conftest.F
>>>>> sh:
>>>>> Successful compile:
>>>>> Source:
>>>>>          program main
>>>>>          use configtest
>>>>>
>>>>>          write(*,*) testint
>>>>>
>>>>>          end
>>>>>                      Pushing language FC
>>>>>                      Popping language FC
>>>>> sh: /home/balay/petsc-3.2/bin/win32fe/win32fe ifort  -o
>>>>> /tmp/petsc-zRoAJW/config.compilers/conftest.exe
>>>>> -I/tmp/petsc-zRoAJW/config.compilers/confdir  -MT -Z7 -fpp
>>>>> /tmp/petsc-zRoAJW/config.compilers/conftest.o
>>>>> /tmp/petsc-zRoAJW/config.compilers/configtest.o
>>>>> Executing: /home/balay/petsc-3.2/bin/win32fe/win32fe ifort  -o
>>>>> /tmp/petsc-zRoAJW/config.compilers/conftest.exe
>>>>> -I/tmp/petsc-zRoAJW/config.compilers/confdir  -MT -Z7 -fpp
>>>>> /tmp/petsc-zRoAJW/config.compilers/conftest.o
>>>>> /tmp/petsc-zRoAJW/config.compilers/configtest.o
>>>>> sh: LINK : C:\cygwin\tmp\PETSC-~3\CONFIG~1.COM\conftest.exe not found or
>>>>> not
>>>>> built by the last incremental link; performing full link^M
>>>>>
>>>>>            compilers: Fortran module include flag -I found
>>>>>              Popping language FC
>>>>> <<<<<<<<<<<<<<<<<<<<<<<
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>> On Thu, 15 Sep 2011, Matthew Knepley wrote:
>>>>>
>>>>>> On Thu, Sep 15, 2011 at 8:43 AM, Alexander Grayver
>>>>>> <agrayver at gfz-potsdam.de>wrote:
>>>>>>
>>>>>>> **
>>>>>>> Thanks Matt,
>>>>>>>
>>>>>>> I will that, but I use PETSC from Fortran so I need Fortran
>>>>>>> functionality.
>>>>>>>
>>>>>> Sure. Do you use the F90 modules? If so, send us the build problem. If
>>>>>> there
>>>>>> is not build problem,
>>>>>> then ifort supports only relative paths for module includes, which is
>>>>>> crazy
>>>>>> and will break sometimes.
>>>>>>
>>>>>>      Thanks,
>>>>>>
>>>>>>         Matt
>>>>>>
>>>>>>
>>>>>>> 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>    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>    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
>>>>>>>
>>>>>>>
>>>>>>>
>>

More information about the petsc-users mailing list