Hi Satish,<br><br>my problem is solved by now. I upgraded CMake from 2.6 to the latest version (2.8.2) and it works fine. Thanks for the help anyway. In case you really want to see it, i can reproduce the configure.log file but otherwise I consider this "bug-report" as solved. (since i've overwritten the log by now). <br>
<br>cheers, Leo<br><br><br><br><div class="gmail_quote">2010/8/23 Satish Balay <span dir="ltr"><<a href="mailto:balay@mcs.anl.gov">balay@mcs.anl.gov</a>></span><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
1. you haven't mentioned the command you've invoked<br>
<br>
2. you haven't sent the logfile as instructed.<br>
<br>
All discussions without the above are just guessing games. If you<br>
want to make progress - run with the additional configure option<br>
<br>
--with-cmake=0<br>
<br>
<br>
Jed,<br>
<br>
shouldn't the cmake output [when invoked via configure] - go into<br>
configure.log - and not to stdout?.<br>
<br>
Satish<br>
<div class="im"><br>
On Mon, 23 Aug 2010, Leo van Kampenhout wrote:<br>
<br>
> Hello, the problem with the "infinite" loop seems to be CMAKE related. Sorry<br>
> to bother. Maybe the minimum required version of CMake should be changed<br>
> from 2.6 to something higher.<br>
</div>> Here<<a href="http://www.mail-archive.com/cmake@cmake.org/msg25107.html" target="_blank">http://www.mail-archive.com/cmake@cmake.org/msg25107.html</a>>people<br>
<div class="im">> discuss the same problem, where somebody suggest the problem of<br>
> infinite looping is fixed in version<br>
</div>> 2.6.2<<a href="http://www.cmake.org/files/v2.6/CMakeChangeLog-2.6.2" target="_blank">http://www.cmake.org/files/v2.6/CMakeChangeLog-2.6.2</a>><br>
<div><div></div><div class="h5">><br>
> regards<br>
><br>
><br>
><br>
> 2010/8/23 Matthew Knepley <<a href="mailto:knepley@gmail.com">knepley@gmail.com</a>><br>
><br>
> > This is not output from our configure. Are you running something else in<br>
> > the PETSc directory?<br>
> > Send configure.log<br>
> ><br>
> > Matt<br>
> ><br>
> ><br>
> > On Mon, Aug 23, 2010 at 11:45 AM, Leo van Kampenhout <<br>
> > <a href="mailto:lvankampenhout@gmail.com">lvankampenhout@gmail.com</a>> wrote:<br>
> ><br>
> >> Hi Aron,<br>
> >><br>
> >> I try now to configure the Mercurial version of Petsc-dev. However, the<br>
> >> script gets stuck in some kind of "infinite" loop, producing this text over<br>
> >> and over again. What should I do now?<br>
> >><br>
> >> -- The C compiler identification is GNU<br>
> >> -- Check for working C compiler: /opt/local/bin/mpicc<br>
> >> -- Check for working C compiler: /opt/local/bin/mpicc -- works<br>
> >> -- Detecting C compiler ABI info<br>
> >> -- Detecting C compiler ABI info - done<br>
> >> -- The Fortran compiler identification is GNU<br>
> >> -- Check for working Fortran compiler: mpif90<br>
> >> -- Check for working Fortran compiler: mpif90 -- works<br>
> >> -- Checking whether mpif90 supports Fortran 90<br>
> >> -- Checking whether mpif90 supports Fortran 90 -- yes<br>
> >> -- Configuring done<br>
> >> You have changed variables that require your cache to be deleted.<br>
> >> Configure will be re-run and you may have to reset some variables.<br>
> >> The following variables have changed:<br>
> >> CMAKE_Fortran_COMPILER= mpif90<br>
> >><br>
> >><br>
> >><br>
> >> Leo<br>
> >><br>
> >><br>
> >> 2010/8/23 Aron Ahmadia <<a href="mailto:aron@ahmadia.net">aron@ahmadia.net</a>><br>
> >><br>
> >>> Hi Leo,<br>
> >>><br>
> >>> Yes.<br>
> >>><br>
> >>> A<br>
> >>><br>
> >>> On Mon, Aug 23, 2010 at 2:19 PM, Leo van Kampenhout <<br>
> >>> <a href="mailto:lvankampenhout@gmail.com">lvankampenhout@gmail.com</a>> wrote:<br>
> >>><br>
> >>>> Hi Aron,<br>
> >>>><br>
> >>>> I'm using the nightly tarball. Do you propose using mercurial? I can try<br>
> >>>> that.<br>
> >>>><br>
> >>>> Leo<br>
> >>>><br>
> >>>><br>
> >>>><br>
> >>>> 2010/8/23 Aron Ahmadia <<a href="mailto:aron@ahmadia.net">aron@ahmadia.net</a>><br>
> >>>><br>
> >>>> Hi Leo,<br>
> >>>>><br>
> >>>>> Did you perform an "hg pull; hg update" in<br>
> >>>>> petsc-dev/config/BuildSystem?<br>
> >>>>><br>
> >>>>> A<br>
> >>>>><br>
> >>>>> On Mon, Aug 23, 2010 at 2:14 PM, Leo van Kampenhout <<br>
> >>>>> <a href="mailto:lvankampenhout@gmail.com">lvankampenhout@gmail.com</a>> wrote:<br>
> >>>>><br>
> >>>>>> Hi all,<br>
> >>>>>><br>
> >>>>>> I'm trying to install PETSc-dev on my desktop machine. This is what<br>
> >>>>>> goes wrong. I suspect the line<br>
> >>>>>> import cmakegen [line 409]<br>
> >>>>>> in the configure.py is the cause. The version of Cmake installed on my<br>
> >>>>>> system is 2.6<br>
> >>>>>> Best regards,<br>
> >>>>>><br>
> >>>>>> Leo van Kampenhout<br>
> >>>>>><br>
> >>>>>><br>
> >>>>>> csg4035@wingtip70:~/install/petsc-dev$ ./configure<br>
> >>>>>><br>
> >>>>>> ===============================================================================<br>
> >>>>>> Configuring PETSc to compile on your<br>
> >>>>>> system<br>
> >>>>>><br>
> >>>>>> ===============================================================================<br>
> >>>>>> TESTING: configureFortranFlush from<br>
> >>>>>> PETSc.Configure(/net/users/csg/csg4035/download/petsc-dev/config/PETSc/Configure.py:652*******************************************************************************<br>
> >>>>>> UNABLE to FIND MODULE for ./configure<br>
> >>>>>><br>
> >>>>>> -------------------------------------------------------------------------------<br>
> >>>>>> No module named cmakegen<br>
> >>>>>><br>
> >>>>>> *******************************************************************************<br>
> >>>>>><br>
> >>>>>><br>
> >>>>>><br>
> >>>>>><br>
> >>>>><br>
> >>>><br>
> >>><br>
> >><br>
> ><br>
> ><br>
> > --<br>
> > What most experimenters take for granted before they begin their<br>
> > experiments is infinitely more interesting than any results to which their<br>
> > experiments lead.<br>
> > -- Norbert Wiener<br>
> ><br>
><br>
<br>
</div></div></blockquote></div><br>