[petsc-dev] no module named cmakegen

[Leo van Kampenhout]

Hi Satish,

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).

cheers, Leo



2010/8/23 Satish Balay <balay at mcs.anl.gov>

> 1. you haven't mentioned the command you've invoked
>
> 2. you haven't sent the logfile as instructed.
>
> All discussions without the above are just guessing games.  If you
> want to make progress - run with the additional configure option
>
> --with-cmake=0
>
>
> Jed,
>
> shouldn't the cmake output [when invoked via configure] - go into
> configure.log - and not to stdout?.
>
> Satish
>
> On Mon, 23 Aug 2010, Leo van Kampenhout wrote:
>
> > Hello, the problem with the "infinite" loop seems to be CMAKE related.
> Sorry
> > to bother. Maybe the minimum required version of CMake should be changed
> > from 2.6 to something higher.
> > Here<http://www.mail-archive.com/cmake@cmake.org/msg25107.html>people
> > discuss the same problem, where somebody suggest the problem of
> > infinite looping is fixed in version
> > 2.6.2<http://www.cmake.org/files/v2.6/CMakeChangeLog-2.6.2>
> >
> > regards
> >
> >
> >
> > 2010/8/23 Matthew Knepley <knepley at gmail.com>
> >
> > > This is not output from our configure. Are you running something else
> in
> > > the PETSc directory?
> > > Send configure.log
> > >
> > >    Matt
> > >
> > >
> > > On Mon, Aug 23, 2010 at 11:45 AM, 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
> > >>>>>>
> > >>>>>>
> *******************************************************************************
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>>
> > >>>>>
> > >>>>
> > >>>
> > >>
> > >
> > >
> > > --
> > > 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
> > >
> >
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20100823/b8ae627a/attachment.html>