This is to support different backends. If configure found CMake, then normal "make" will use multiple jobs, or you can do it explicitly with make -j3 $PETSC_ARCH.
CMake would be terrible as a hard dependency (it's terrible enough as it is) but it's less bad than some alternatives. On Mon, Feb 25, 2013 at 3:30 PM, Tim Tautges <tautges at mcs.anl.gov> wrote: > tautges at chronos:~/code/petsc-**dev-moab$ make -j 8 > ********************* ERROR ************************* > Parallel build with 'make -j' is not supported > ******************************************************** > make: *** [chk_makej] Error 1 > tautges at chronos:~/code/petsc-**dev-moab$ > > > Why??? I can almost understand petsc's justification for its own > autotools-looking python-based build system, but why its need to not > support otherwise-standard make options? Similarly, > PETSC_MAKE_STOP_ON_ERROR instead of make -k? > > - tim > > -- > ==============================**==============================**==== > "You will keep in perfect peace him whose mind is > steadfast, because he trusts in you." Isaiah 26:3 > > Tim Tautges Argonne National Laboratory > (tautges at mcs.anl.gov) (telecommuting from UW-Madison) > phone (gvoice): (608) 354-1459 1500 Engineering Dr. > fax: (608) 263-4499 Madison, WI 53706 > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20130225/31c6fc0c/attachment.html>
