<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><br><div><div>On Aug 5, 2010, at 9:59 AM, Matthew Knepley wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">On Thu, Aug 5, 2010 at 9:56 AM, Lisandro Dalcin <span dir="ltr"><<a href="mailto:dalcinl@gmail.com">dalcinl@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;">
<div class="im">On 5 August 2010 00:39, Lisandro Dalcin <<a href="mailto:dalcinl@gmail.com">dalcinl@gmail.com</a>> wrote:<br>
> On 4 August 2010 12:44, Barry Smith <<a href="mailto:bsmith@mcs.anl.gov">bsmith@mcs.anl.gov</a>> wrote:<br>
>><br>
>> Lisandro,<br>
>><br>
>> We would like to help you make it possible for petsc4py to be installed by easyinstall and automatically install PETSc with it, thus making it trivial for Python users to start using petsc4py. How can we help make this happen?<br>
>><br>
><br>
> $ export PETSC_DIR=/path/to/petsc<br>
> $ export PETSC_ARCH=arch-name<br>
> $ easy_install petsc4py<br>
><br>
> This should work and be enough (at least on Linux)...<br>
><br>
<br>
</div>I confirm this works out of the box (on Linux) for prefix installs and<br>
non-prefix builds of petsc-3.1<br>
<br>
All this assuming a previous installation/build of PETSc is available.<br>
Barry, Do you actually mean that "easy_install petsc4py" should handle<br>
the download and build of core PETSc?</blockquote><div><br></div></div></blockquote> As Matt says in too many words "absolutely"</div><div><br></div><div> We'd like to remove all the pain of using petsc4py so it will be trivially used with packages like SAGE and Scipy etc. It is too painful now for Python users since it requires installing PETSc manually.</div><div><br></div><div> The reason I want to look for mpi4py is to determine what MPI it was built with so PETSc would be built with the same MPI (and hence can be used with mpi4py).</div><div><br></div><div> Barry</div><div><br><blockquote type="cite"><div class="gmail_quote"><div>What I was hoping for is something along the lines of Atlas in numpy. If</div><div>we find PETSc, use it. If not, do we find mpi4py? If so, use that and</div>
<div>build plain vanilla PETSc. If not, build PETSc with mpiuni. That way, it</div><div>will always work out of the box for everyone, and for savvy users, it does</div><div>the right thing too.</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;"><div><div class="h5">
--<br>
Lisandro Dalcin<br>
---------------<br>
CIMEC (INTEC/CONICET-UNL)<br>
Predio CONICET-Santa Fe<br>
Colectora RN 168 Km 472, Paraje El Pozo<br>
Tel: +54-342-4511594 (ext 1011)<br>
Tel/Fax: +54-342-4511169<br>
</div></div></blockquote></div><br><br clear="all"><br>-- <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>
</blockquote></div><br></body></html>