On Mon, Nov 7, 2011 at 9:43 PM, Shao-Ching Huang <span dir="ltr"><<a href="mailto:huangsc@gmail.com">huangsc@gmail.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi<br>
<br>
I downloaded petsc using the "hg clone<br>
<a href="http://petsc.cs.iit.edu/petsc/releases/petsc-3.2" target="_blank">http://petsc.cs.iit.edu/petsc/releases/petsc-3.2</a>" method. Now, after<br>
hg pull/update (some files are changed), do I always have to build<br>
from scratch (i.e. compiling everything, including the --download-xxx<br>
stuff)? Is there a short cut to rebuild libpetsc.{so,a} when I have no<br>
configuration change?<br></blockquote><div><br></div><div>The point of having a configuration stage is that it allows us to be ignorant</div><div>of the precise configuration of your platform. If you want a package, there</div>
<div>are several package managers with PETSc (like Debian), but it is hard</div><div>to keep them up to date. Personally, I prefer the "built it for the machine"</div><div>philosophy (like Gentoo).</div><div><br>
</div><div> Matt</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Thanks,<br>
<font color="#888888"><br>
Shao-Ching</font></blockquote></div>-- <br>What most experimenters take for granted before they begin their experiments is infinitely more interesting than any results to which their experiments lead.<br>-- Norbert Wiener<br>