<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
</head>
<body>
<div dir="auto" style="direction: ltr; margin: 0; padding: 0; font-family: sans-serif; font-size: 11pt; color: black; ">
Hmm. So if petsc always compiles mpiuni if --with-mpi=0, then it makes me think it should be possible to drop requires(MPI) from p4est, while still passing `--enable-mpi` to p4est.<br>
<br>
</div>
<div dir="auto" style="direction: ltr; margin: 0; padding: 0; font-family: sans-serif; font-size: 11pt; color: black; ">
<span id="ms-outlook-android-cursor"></span>Maybe: if mpiuni doesn't provide some esoteric part of MPI that p4est uses, it will break.<br>
<br>
</div>
<div dir="auto" style="direction: ltr; margin: 0; padding: 0; font-family: sans-serif; font-size: 11pt; color: black; ">
<span id="OutlookSignature">
<div dir="auto" style="direction: ltr; margin: 0; padding: 0; font-family: sans-serif; font-size: 11pt; color: black; ">
Toby Isaac, Assistant Professor, GTCSE</div>
</span><br>
</div>
<hr style="display:inline-block;width:98%" tabindex="-1">
<div id="divRplyFwdMsg" dir="ltr"><font face="Calibri, sans-serif" style="font-size:11pt" color="#000000"><b>From:</b> Satish Balay <balay@mcs.anl.gov><br>
<b>Sent:</b> Friday, April 16, 2021 1:03:55 PM<br>
<b>To:</b> Isaac, Tobin G <tisaac@cc.gatech.edu><br>
<b>Cc:</b> petsc-dev <petsc-dev@mcs.anl.gov><br>
<b>Subject:</b> Re: [petsc-dev] p4est w/o MPI</font>
<div> </div>
</div>
<div class="BodyFragment"><font size="2"><span style="font-size:11pt;">
<div class="PlainText">Thanks! Another issue:<br>
<br>
mpiuni provides mpi.h. And I get the following errors when building PETSc.<br>
<br>
/home/balay/petsc/arch-linux-c-debug/include/sc.h:87:2: error: #error "mpi.h is included. Use --enable-mpi."<br>
87 | #error "mpi.h is included. Use --enable-mpi."<br>
| ^~~~~<br>
<br>
etc..<br>
<br>
Satish<br>
<br>
<br>
On Fri, 16 Apr 2021, Isaac, Tobin G wrote:<br>
<br>
> Yes, `--disable-mpi` should be accepted by p4est.<br>
> <br>
> ________________________________________<br>
> From: Satish Balay <balay@mcs.anl.gov><br>
> Sent: Friday, April 16, 2021 11:47<br>
> To: Satish Balay via petsc-dev<br>
> Cc: Isaac, Tobin G<br>
> Subject: Re: [petsc-dev] p4est w/o MPI<br>
> <br>
> BTW: Is there no --disable-mpi option?<br>
> <br>
> Satish<br>
> <br>
> On Fri, 16 Apr 2021, Satish Balay via petsc-dev wrote:<br>
> <br>
> > MPI pacakge is a bit weird compared to others [as it does this funny thing with MPIUNI].<br>
> ><br>
> > For regular packages - I guess I would use 'if package.found'<br>
> ><br>
> > I guess I should create an MR with this diff.<br>
> ><br>
> > Satish<br>
> ><br>
> > ----<br>
> ><br>
> > diff --git a/config/BuildSystem/config/packages/p4est.py b/config/BuildSystem/config/packages/p4est.py<br>
> > index e7108b0ab8..40d6797f02 100644<br>
> > --- a/config/BuildSystem/config/packages/p4est.py<br>
> > +++ b/config/BuildSystem/config/packages/p4est.py<br>
> > @@ -24,14 +24,16 @@ class Configure(config.package.GNUPackage):<br>
> > self.blasLapack = framework.require('config.packages.BlasLapack',self)<br>
> > self.zlib = framework.require('config.packages.zlib',self)<br>
> > self.memalign = framework.argDB['with-memalign']<br>
> > - self.deps = [self.mpi,self.blasLapack,self.zlib]<br>
> > + self.deps = [self.blasLapack,self.zlib]<br>
> > + self.odeps = [self.mpi]<br>
> > return<br>
> ><br>
> > def formGNUConfigureArgs(self):<br>
> > args = config.package.GNUPackage.formGNUConfigureArgs(self)<br>
> > if self.argDB['with-p4est-debugging']:<br>
> > args.append('--enable-debug')<br>
> > - args.append('--enable-mpi')<br>
> > + if not self.mpi.usingMPIUni:<br>
> > + args.append('--enable-mpi')<br>
> > args.append('CPPFLAGS="'+self.headers.toStringNoDupes(self.dinclude)+'"')<br>
> > args.append('LIBS="'+self.libraries.toString(self.dlib)+'"')<br>
> > args.append('--enable-memalign='+self.memalign)<br>
> ><br>
> > On Fri, 16 Apr 2021, Isaac, Tobin G wrote:<br>
> ><br>
> > > Matt, this is the configure logic I would like, but I don't know how to do it:<br>
> > > - configure p4est after MPI, but do not require MPI<br>
> > > - if MPI is present, add the '--enable-mpi' flack in formGNUConfigureArgs(), otherwise omit it.<br>
> > ><br>
> > > ________________________________________<br>
> > > From: Isaac, Tobin G <tisaac@cc.gatech.edu><br>
> > > Sent: Friday, April 16, 2021 11:03<br>
> > > To: Mark Adams; For users of the development version of PETSc<br>
> > > Subject: Re: [petsc-dev] p4est w/o MPI<br>
> > ><br>
> > > p4est has a mode where it can compile without MPI, I don't know if PETSc is using it, will check.<br>
> > ><br>
> > > ________________________________________<br>
> > > From: petsc-dev <petsc-dev-bounces@mcs.anl.gov> on behalf of Mark Adams <mfadams@lbl.gov><br>
> > > Sent: Friday, April 16, 2021 10:23<br>
> > > To: For users of the development version of PETSc<br>
> > > Subject: [petsc-dev] p4est w/o MPI<br>
> > ><br>
> > > I don't have MPI (Fugaku w/ gcc) and p4est seems to need it. Is there a work around?<br>
> > > Thanks,<br>
> > > Mark<br>
> > ><br>
> ><br>
> <br>
<br>
</div>
</span></font></div>
</body>
</html>