<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Tahoma
}
--></style>
</head>
<body class='hmmessage'><div dir='ltr'>
I do not plan on using MUMPS without PETSc, but I would like to learn how I can compile these libraries independent of PETSc so that later when I try to configure PETSc in some other computer I know how to take care of MUMPS libraries. Coming to think of it, it sounds like I should not be doing this, because the other computer (which will be a cluster since this is where I plan on doing my number crunching ultimately) will have different OS and I will be out of luck again. <br><br>By the way, I already have Macports installed and I have gcc44, but I do not have gfortran (I checked inside /opt/local/lib), which I can install .<br><br>I am not quite understanding why we need gfortran from Macports, because I already have them in /usr/local/lib . Moreover, when we ./configure PETSc with MPI we need to use wrapper compilers mpicc and mpif77 anyways. I am sorry if this wrong, bu this is what my understanding was, and this is how I compiled PETSc on my computer.<br><br>If I configure PETSc the way you mentioned (that is, with download mumps etc), will I then be able to run the executable of my program (the one that we get out by typing make myprogram) on any computer anywhere regardless of whether it has MAC OSX or not? Do I need to carry all the libraries with the program if I do so? Sorry for digressing with elementary questions.<br><br>My original plan was to install PETSc on my laptop ( MAC OSX) and any external libraries or packages on the laptop, then compile my C program on my laptop, and then send the executable to cluster or more powerful computer around the country/national labs for number crunching. I am not implying that compiling MUMPS separately from PETSc will allow me to do this, but if your method of configuring PETSc with download mumps option will allow me to meet these needs, then I'd definitely do it that way. My ultimate goal is to be able to run my program on powerful computers and cluster. <br><div>
<br>Thanks.<br><br>-Amrit<br><br></div><br><br><div><hr id="stopSpelling">From: sean@mcs.anl.gov<br>Date: Wed, 7 Sep 2011 12:35:51 -0500<br>To: petsc-users@mcs.anl.gov<br>Subject: Re: [petsc-users] petsc-users Digest, Vol 33, Issue 13<br><br><div class="ecxgmail_quote"><blockquote class="ecxgmail_quote" style="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="ecxgmail_quote" style="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" target="_blank">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></div> </div></body>
</html>