<div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div><div dir="ltr"><div>If I do this, will I get all the libraries compiled properly?</div></div>
</div></blockquote><div><br></div><div>Yes. All the libraries will be compiled properly on the mac and put int $PETSC_DIR/$PETSC_ARCH/lib. More importantly, PETSc will be compiled with MUMPS support easiest with this method.</div>
<div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div><div dir="ltr"><div> I was thinking of independently compiling these external packages and then use them during run time.</div>
</div></div></blockquote><div><br></div><div>Do you need to use MUMPS without PETSc? You could look at my extension to MacPorts:</div><div><br></div><div><a href="https://bitbucket.org/seanfarley/scienceports">https://bitbucket.org/seanfarley/scienceports</a></div>
<div><br></div><div>But it will require you to:</div><div><br></div><div>1) Install (and use) MacPorts</div><div><br></div><div>2) Install the MacPorts gfortran</div><div><br></div><div>A big caveat is that it is not as flexible as having different PETSC_ARCH's. This is due to MacPorts insistence on having everything installed into /opt/local but if you only want one PETSC_ARCH then it might be handy.</div>
<div><br></div><div>You would then specify to PETSc's configure:</div><div><br></div><div>./configure --with-blacs-dir=/opt/local --with-scalapack-dir=/opt/local --with-mumps-dir=/opt/local</div><div><br></div><div>Use this method at your own risk.</div>
<div><br></div><div>Sean</div></div>