Yes, this is what I was working on but my time got blown away by other things. Using the parmetis makefile is ridiculous.
On Thursday, February 16, 2012, Barry Smith wrote: > > PETSc-folks > > Actually why does parmetis.py even use that stupid gnumake file, we > could change parmetis.py to issue the cmake builder command directly and > then the make on the cmake generated makefile also directly and totally > bypass that absurd makefile. Then we can have better control over what gets > passed to the cmake builder and can pass down easily the needed include > directories for MPI > > Barry > > On Feb 16, 2012, at 10:00 PM, Barry Smith wrote: > > > > > John, > > > > So I looked in the parmetis Makefile and it looks like it has no > direct mechanism to pass in MPI include file directories etc. I do not know > much about cmake the only way I could see getting that information in is via > > > > ifneq ($(cflags), not-set) > > CONFIG_FLAGS += -DCMAKE_C_FLAGS:STRING="$(cflags)" > > endif > > > > but I don't know if this is a legitimate way in cmake to pass in include > directories to cmake. JED????? > > > > If the machine has MPI compiler wrappers (like most systems do) and you > used that rather than passing icc and the MPI information to PETSc's > ./configure that would also work. > > > > > > Barry > > > > > > On Feb 16, 2012, at 11:58 AM, John Fettig wrote: > > > >> Hello PETSc gurus, > >> > >> I'm trying to install petsc-dev using --download-parmetis=1, and it > isn't > >> passing any info that I give it about MPI to the parmetis configure. > >> Looking at config/PETSc/packages/parmetis.py, it doesn't look like > there is > >> any attempt made to pass along this info. Am I doing something wrong? > >> (configure.log attached) > >> > >> Thanks, > >> John > >> > >> <configure.log.gz> > > > > -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20120217/dcb27131/attachment.html>