[petsc-dev] cmakeboot.py is a total disaster needs fixing or removal
Satish Balay
balay at mcs.anl.gov
Mon May 23 16:47:23 CDT 2011
Barry,
Does --with-cmake=0 workarround this?
Satish
On Mon, 23 May 2011, Barry Smith wrote:
>
> Jed,
>
> I can no longer configure!
>
>
> You move a bunch of stuff that has nothing to do with cmake into cmakeboot.py for example self.make = self.framework.require('config.programs', None)
> now if your silly cmakeboot stuff doesn't work then variables like OMAKE are never defined in the generated petscvariables file and so nothing can get built. Pisses me off, it is fine to support cmake but don't make it the goddamn center of PETSc.
>
> I am stuck without PETSc because I don't have a clue why this is happening.
>
> Barry
>
> [see attached file: configure.log]
>
>
More information about the petsc-dev
mailing list