On Fri, Jan 20, 2012 at 9:43 AM, Dominik Szczerba <span dir="ltr"><<a href="mailto:dominik@itis.ethz.ch">dominik@itis.ethz.ch</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">
<div class="HOEnZb"><div class="h5">I am building on a Cray system with crayftn fortran compiler. I<br>
specify --with-fc=crayftn and --FFLAGS=-em. Despite the latter, I am<br>
still getting the below cited error. Interestingly, the mod file IS<br>
THERE:<br>
<br>
> find /tmp/petsc-0Bnd1w -iname \*.mod<br>
/tmp/petsc-0Bnd1w/config.compilers/CONFIGTEST.mod<br>
<br>
How do I go on from here?<br></div></div></blockquote><div><br></div><div>The problem is not that is doesn't create a module file, but that it will not put it</div><div>where we ask it to. Please send entire configure.log (don't Cc users).</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 class="HOEnZb"><div class="h5">
Thanks<br>
Dominik<br>
<br>
<br>
<br>
================================================================================<br>
TEST checkFortranModuleInclude from<br>
config.compilers(/users/dsz/pack/petsc-3.2-p5/config/BuildSystem/config/compilers.py:1155)<br>
TESTING: checkFortranModuleInclude from<br>
config.compilers(config/BuildSystem/config/compilers.py:1155)<br>
Figures out what flag is used to specify the include path for Fortran modules<br>
Pushing language FC<br>
sh: crayftn -c -o /tmp/petsc-0Bnd1w/config.compilers/conftest.o<br>
-I/tmp/petsc-0Bnd1w/config.compilers<br>
-I/tmp/petsc-0Bnd1w/config.setCompilers -em -O3<br>
/tmp/petsc-0Bnd1w/config.compilers/conftest.F<br>
Executing: crayftn -c -o /tmp/petsc-0Bnd1w/config.compilers/conftest.o<br>
-I/tmp/petsc-0Bnd1w/config.compilers<br>
-I/tmp/petsc-0Bnd1w/config.setCompilers -em -O3<br>
/tmp/petsc-0Bnd1w/config.compilers/conftest.F<br>
sh:<br>
Successful compile:<br>
Source:<br>
module configtest<br>
integer testint<br>
parameter (testint = 42)<br>
end module configtest<br>
*******************************************************************************<br>
UNABLE to CONFIGURE with GIVEN OPTIONS (see configure.log<br>
for details):<br>
-------------------------------------------------------------------------------<br>
Fortran module was not created during the compile.<br>
configtest.mod/CONFIGTEST.mod not found<br>
*******************************************************************************<br>
File "/users/dsz/pack/petsc-3.2-p5/config/configure.py", line 283,<br>
in petsc_configure<br>
framework.configure(out = sys.stdout)<br>
File "/users/dsz/pack/petsc-3.2-p5/config/BuildSystem/config/framework.py",<br>
line 925, in configure<br>
child.configure()<br>
File "/users/dsz/pack/petsc-3.2-p5/config/BuildSystem/config/compilers.py",<br>
line 1338, in configure<br>
self.executeTest(self.checkFortranModuleInclude)<br>
File "/users/dsz/pack/petsc-3.2-p5/config/BuildSystem/config/base.py",<br>
line 115, in executeTest<br>
ret = apply(test, args,kargs)<br>
File "/users/dsz/pack/petsc-3.2-p5/config/BuildSystem/config/compilers.py",<br>
line 1187, in checkFortranModuleInclude<br>
raise RuntimeError('Fortran module was not created during the<br>
compile. configtest.mod/CONFIGTEST.mod not found')<br>
<br>
</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>