On Mon, 23 Aug 2010, Aron Ahmadia wrote: > Hi Leo, > > I haven't seen this problem before. What are you specifying to configure? > You may want to send the configure.log (after killing it) to > petsc-maint at mcs.anl.gov. I am not on that mailing list, but it's the right > place to send potential bugs. > > Also, this goes without saying, but if you were doing anything strange, it's > best to start with a clean copy of the repository (I don't know the *right* > way to do this in Mercurial, but you can just do an hg clone of your > petsc-dev into another directory)
Aron, One can do the following: cd petsc-dev hg status hg revert -a hg pull -u cd BuildSystem hg status hg revert -a hg pull -u Satish > > A > > On Mon, Aug 23, 2010 at 2:45 PM, Leo van Kampenhout < > lvankampenhout at gmail.com> wrote: > > > Hi Aron, > > > > I try now to configure the Mercurial version of Petsc-dev. However, the > > script gets stuck in some kind of "infinite" loop, producing this text over > > and over again. What should I do now? > > > > -- The C compiler identification is GNU > > -- Check for working C compiler: /opt/local/bin/mpicc > > -- Check for working C compiler: /opt/local/bin/mpicc -- works > > -- Detecting C compiler ABI info > > -- Detecting C compiler ABI info - done > > -- The Fortran compiler identification is GNU > > -- Check for working Fortran compiler: mpif90 > > -- Check for working Fortran compiler: mpif90 -- works > > -- Checking whether mpif90 supports Fortran 90 > > -- Checking whether mpif90 supports Fortran 90 -- yes > > -- Configuring done > > You have changed variables that require your cache to be deleted. > > Configure will be re-run and you may have to reset some variables. > > The following variables have changed: > > CMAKE_Fortran_COMPILER= mpif90 > > > > > > > > Leo > > > > > > 2010/8/23 Aron Ahmadia <aron at ahmadia.net> > > > >> Hi Leo, > >> > >> Yes. > >> > >> A > >> > >> On Mon, Aug 23, 2010 at 2:19 PM, Leo van Kampenhout < > >> lvankampenhout at gmail.com> wrote: > >> > >>> Hi Aron, > >>> > >>> I'm using the nightly tarball. Do you propose using mercurial? I can try > >>> that. > >>> > >>> Leo > >>> > >>> > >>> > >>> 2010/8/23 Aron Ahmadia <aron at ahmadia.net> > >>> > >>> Hi Leo, > >>>> > >>>> Did you perform an "hg pull; hg update" in petsc-dev/config/BuildSystem? > >>>> > >>>> A > >>>> > >>>> On Mon, Aug 23, 2010 at 2:14 PM, Leo van Kampenhout < > >>>> lvankampenhout at gmail.com> wrote: > >>>> > >>>>> Hi all, > >>>>> > >>>>> I'm trying to install PETSc-dev on my desktop machine. This is what > >>>>> goes wrong. I suspect the line > >>>>> import cmakegen [line 409] > >>>>> in the configure.py is the cause. The version of Cmake installed on my > >>>>> system is 2.6 > >>>>> Best regards, > >>>>> > >>>>> Leo van Kampenhout > >>>>> > >>>>> > >>>>> csg4035 at wingtip70:~/install/petsc-dev$ ./configure > >>>>> > >>>>> =============================================================================== > >>>>> Configuring PETSc to compile on your > >>>>> system > >>>>> > >>>>> =============================================================================== > >>>>> TESTING: configureFortranFlush from > >>>>> PETSc.Configure(/net/users/csg/csg4035/download/petsc-dev/config/PETSc/Configure.py:652******************************************************************************* > >>>>> UNABLE to FIND MODULE for ./configure > >>>>> > >>>>> ------------------------------------------------------------------------------- > >>>>> No module named cmakegen > >>>>> > >>>>> ******************************************************************************* > >>>>> > >>>>> > >>>>> > >>>>> > >>>> > >>> > >> > > >
