<html dir="ltr">
<head>
<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1">
<style type="text/css" id="owaParaStyle"></style>
</head>
<body fpstyle="1" ocsi="0">
<div style="direction: ltr;font-family: Tahoma;color: #000000;font-size: 10pt;">I agree, that's annoying.
<div><br>
</div>
<div>However, is it conceivable that someone may want to install PETSc, download MUMPS, but use their own ParMetis and/or ScaLAPACK (especially the latter, since a vendor-optimized version may already be installed in a system scientific software library, and
that will likely perform better than something that is downloaded and compiled from high-level source)?</div>
<div><br>
</div>
<div>I suppose it could be left to the "power users" to specify something like</div>
<div><br>
</div>
<div>./configure --download-mumps --with-scalapack=blahblah</div>
<div><br>
</div>
<div>and then let the PETSc installer decide on its own that it needs to download ParMetis, but that ScaLAPACK is covered.</div>
<div><br>
</div>
<div>At the very least, I would hope that some sort of prominent message is displayed if indeed the PETSc configure automatically decides to download extra things that I didn't specify...</div>
<div><br>
</div>
<div>Just my two cents (I'm not a PETSc developer, but I have had lots of experience building PETSc on a wide variety of systems)...</div>
<div><br>
</div>
<div> -Tom C.<br>
<div style="font-family: Times New Roman; color: #000000; font-size: 16px">
<hr tabindex="-1">
<div id="divRpF971791" style="direction: ltr; "><font face="Tahoma" size="2" color="#000000"><b>From:</b> petsc-dev-bounces@mcs.anl.gov [petsc-dev-bounces@mcs.anl.gov] on behalf of Aron Ahmadia [aron.ahmadia@kaust.edu.sa]<br>
<b>Sent:</b> Wednesday, March 21, 2012 5:46 AM<br>
<b>To:</b> For users of the development version of PETSc<br>
<b>Subject:</b> [petsc-dev] --download-dependencies flag?<br>
</font><br>
</div>
<div></div>
<div>
<div dir="ltr">In order to get a user up-and-running with a MUMPs-enabled PETSc, I followed this frustrating chain:
<div><br>
</div>
<div>configure --download-mumps=1</div>
<div><br>
</div>
<div>...</div>
<div><br>
</div>
<div>Error, no parmetis!</div>
<div><br>
</div>
<div>configure --download-mumps=1 --download-parmetis=1</div>
<div><br>
</div>
<div>Error, no scalapack!</div>
<div><br>
</div>
<div>
<div>configure --download-mumps=1 --download-parmetis=1 --download-scalapack=1</div>
</div>
<div><br>
</div>
<div>It would be convenient if the PETSc BuildSystem did what other package installers like pip, yum, etc..., do, and grab dependencies that I need based on what I have requested.</div>
<div><br>
</div>
<div>Additionally, it would make it a lot easier to build PETSc on complicated systems if BuildSystem did a quick dependency/flag check instead off the way it works now (sequential intermixing of really slow and fast configure options).</div>
<div><br>
</div>
<div>A</div>
</div>
</div>
</div>
</div>
</div>
</body>
</html>