On Thu, Sep 15, 2011 at 8:43 AM, Alexander Grayver <span dir="ltr"><<a href="mailto:agrayver@gfz-potsdam.de">agrayver@gfz-potsdam.de</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<u></u>
<div bgcolor="#ffffff" text="#000000">
Thanks Matt,<br>
<br>
I will that, but I use PETSC from Fortran so I need Fortran
functionality.<br></div></blockquote><div><br></div><div>Sure. Do you use the F90 modules? If so, send us the build problem. If there is not build problem,</div><div>then ifort supports only relative paths for module includes, which is crazy and will break sometimes.</div>
<div><br></div><div> Thanks,</div><div><br></div><div> Matt</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div bgcolor="#ffffff" text="#000000">
Regards,<br><font color="#888888">
Alexander</font><div><div></div><div class="h5"><br>
<br>
On 15.09.2011 15:43, Matthew Knepley wrote:
<blockquote type="cite">On Thu, Sep 15, 2011 at 8:01 AM, Alexander Grayver <span dir="ltr"><<a href="mailto:agrayver@gfz-potsdam.de" target="_blank">agrayver@gfz-potsdam.de</a>></span>
wrote:<br>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex">
<div 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>
Figures out what flag is used to specify the include path
for Fortran modules<br>
Pushing language FC<br>
sh: /cygdrive/d/Dev/petsc-3.1-p7/bin/win32fe/win32fe ifort
-c -o conftest.o -MT -Z7 -fpp conftest.F <br>
Executing: /cygdrive/d/Dev/petsc-3.1-p7/bin/win32fe/win32fe
ifort -c -o conftest.o -MT -Z7 -fpp conftest.F <br>
sh: <br>
Pushing language FC<br>
sh: /cygdrive/d/Dev/petsc-3.1-p7/bin/win32fe/win32fe ifort
-c -o conftest.o -Iconfdir -MT -Z7 -fpp conftest.F <br>
Executing: /cygdrive/d/Dev/petsc-3.1-p7/bin/win32fe/win32fe
ifort -c -o conftest.o -Iconfdir -MT -Z7 -fpp conftest.F <br>
sh: <br>
Pushing language FC<br>
Popping language FC<br>
sh: /cygdrive/d/Dev/petsc-3.1-p7/bin/win32fe/win32fe ifort
-o conftest.exe -Iconfdir -MT -Z7 -fpp conftest.o
configtest.o <br>
Executing: /cygdrive/d/Dev/petsc-3.1-p7/bin/win32fe/win32fe
ifort -o conftest.exe -Iconfdir -MT -Z7 -fpp conftest.o
configtest.o <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>
compilers: Fortran module include flag -I found<br>
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>
</div>
</blockquote>
<div><br>
</div>
<div>That would be broken behavior from ifort, but I guess it is
possible. I will talk with Satish about how</div>
<div>this should really be fixed. For right now, go to</div>
<div><br>
</div>
<div> config/BuildSystem/config/compilers.py</div>
<div><br>
</div>
<div>to the checkFortranModuleInclude() function and comment out
the last two lines, which are killing the configure.</div>
<div>Your build will break on the Fortran modules (I assume),
but everything else should work.</div>
<div><br>
</div>
<div> Thanks,</div>
<div><br>
</div>
<div> Matt</div>
<div> </div>
<blockquote class="gmail_quote" style="margin:0pt 0pt 0pt 0.8ex;border-left:1px solid rgb(204, 204, 204);padding-left:1ex">
<div bgcolor="#ffffff" text="#000000"> Regards,<br>
<font color="#888888"> Alexander</font>
<div>
<div><br>
<br>
On 15.09.2011 14:54, Matthew Knepley wrote:
<blockquote type="cite">
<div class="gmail_quote">On Thu, Sep 15, 2011 at 2:49
AM, Alexander Grayver <span dir="ltr"><<a href="mailto:agrayver@gfz-potsdam.de" target="_blank">agrayver@gfz-potsdam.de</a>></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' --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>
UNABLE to CONFIGURE with GIVEN OPTIONS
(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> Thanks,</div>
<div><br>
</div>
<div> Matt</div>
<div> </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>
</div>
</div>
</div>
</blockquote>
</div>
<br>
<br clear="all">
<div><br>
</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>
</div></div></div>
</blockquote></div><br><br clear="all"><div><br></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>