[petsc-dev] error with build

Mon Nov 15 19:11:53 CST 2010

On Mon, Nov 15, 2010 at 6:07 PM, Matthew Knepley <knepley at gmail.com> wrote:

> On Tue, Nov 16, 2010 at 11:58 AM, Srinath Vadlamani <srinath at txcorp.com>wrote:
>
>> It seems now that petsc4py must be built during a petsc configure/build.
>>  Is this correct?  I was hoping to install petsc4py in the same location as
>> my other python builds, so that I only have to specify one location in my
>> PYTHONPATH.
>
>
> I also prefer independent installs:
>
>   1) Clone the petsc4py-dev repo
>
>   2) make cython (you need Cython 0.13)
>
>   3) python setup.py sdist
>
>   4) pip install dist/petsc4py.*.tar.gz --install-option="--user"
>
> which will install it under ~/.local. You can also omit the option to
> install it in the default place.
>

I better make sure before this gets to far:
petsc4py-dev repo = hg clone https://petsc4py.googlecode.com/hg/ petsc4py

Correct?

Also your #4, suggestion: how do I get it to install in :
~/software?
Does petsc4py install in:
<install_dir>/lib/python2.6/site-packages/   ?

thanks,
<>Srinath

>
>   Thanks,
>
>      Matt
>
>
>> <>Srinath
>>
>> On Mon, Nov 15, 2010 at 2:11 PM, Barry Smith <bsmith at mcs.anl.gov> wrote:
>>
>>>
>>>   There (sadly) is not completely automatic way to do this. Cd to
>>> $PETSC_DIR/externalpackages; remove any petsc4py* directories from there;
>>> clone petsc4py-dev into that directory. cd back to $PETSC_DIR; now run
>>> ./configure --download-petsc4py
>>>
>>>   It will not go and get a copy of petsc4py since the petsc4py-dev
>>> directory exists, rather it will use the one you have put there (by your
>>> clone).
>>>
>>>   Note that petsc4py-dev may not always have been updated to the latest
>>> changes to petsc-dev, if you get errors in the build report them to
>>> petsc-maint at mcs.anl.gov and we'll update the petsc4py-dev; note that
>>> after an update of petsc4py-dev you should cd externalpackages/petsc4py-dev
>>> and hg pull; hg update to get the latest.
>>>
>>>  Yes, someone should add proper support for ./configure to handle hg
>>> repositories from petsc-dev and do the pulls and updates automatically but
>>> that code has not been written, hence the manual process.
>>>
>>>   Barry
>>>
>>>
>>> On Nov 15, 2010, at 3:00 PM, Srinath Vadlamani wrote:
>>>
>>> > How does one configure petsc-dev to build petsc4py-dev?
>>> > I cloned petsc4py-dev but it needs my petsc-dev complex install to have
>>> petsc4py symbols?
>>> >
>>> > <>Srinath
>>> >
>>> > 2010/11/15 Satish Balay <balay at mcs.anl.gov>
>>> > [original e-mail didnt make it to the list due to the attached
>>> > configure.log. Huge attachments are prohibited on the mailing lists]
>>> >
>>> >
>>> > Using configure Options: --with-petsc-arch=real-par-debug
>>> --with-scalar-type=real --with-debugging=yes --with-debugger=totalview
>>> --download-superlu_dist=1 --download-mumps=1 --download-spooles=1
>>> --with-shared=1 --download-blacs=1 --download-parmetis=1 --download-szip=1
>>> --download-scalapack=1 --download-petsc4py --download-mpi4py
>>> --with-shared-libraries -prefix=/Users/srinath/software/petsc-dev-real-par
>>> >
>>> >
>>> > petsc4py listed in petsc4py.py is
>>> > http://petsc4py.googlecode.com/files/petsc4py-1.1.1.tar.gz Perhaps you
>>> > have to use petsc-4py-dev directly to get this working?
>>> >
>>> > Lisandro will know..
>>> >
>>> > Satish
>>> >
>>> > On Mon, 15 Nov 2010, Srinath Vadlamani wrote:
>>> >
>>> > > In file included from src/PETSc.c:3:
>>> > > src/petsc4py.PETSc.c: In function
>>> > > ‘__pyx_pf_8petsc4py_5PETSc_2IS_getBlockSize’:
>>> > > src/petsc4py.PETSc.c:49179: warning: implicit declaration of function
>>> > > ‘ISBlock’
>>> > > src/petsc4py.PETSc.c: In function
>>> ‘__pyx_pf_8petsc4py_5PETSc_2IS_getInfo’:
>>> > > src/petsc4py.PETSc.c:51132: warning: implicit declaration of function
>>> > > ‘ISStride’
>>> > > src/petsc4py.PETSc.c: In function
>>> ‘__pyx_pf_8petsc4py_5PETSc_3Mat_zeroRows’:
>>> > > src/petsc4py.PETSc.c:75725: error: too few arguments to function
>>> > > ‘MatZeroRowsIS’
>>> > > src/petsc4py.PETSc.c:75750: error: too few arguments to function
>>> > > ‘MatZeroRows’
>>> > > src/petsc4py.PETSc.c: In function
>>> > > ‘__pyx_pf_8petsc4py_5PETSc_3Mat_zeroRowsLocal’:
>>> > > src/petsc4py.PETSc.c:75872: error: too few arguments to function
>>> > > ‘MatZeroRowsLocalIS’
>>> > > src/petsc4py.PETSc.c:75897: error: too few arguments to function
>>> > > ‘MatZeroRowsLocal’
>>> > > src/petsc4py.PETSc.c: In function
>>> > > ‘__pyx_pf_8petsc4py_5PETSc_3KSP_setConvergenceTest’:
>>> > > src/petsc4py.PETSc.c:87471: error: ‘KSP_NORM_NO’ undeclared (first
>>> use in
>>> > > this function)
>>> > > src/petsc4py.PETSc.c:87471: error: (Each undeclared identifier is
>>> reported
>>> > > only once
>>> > > src/petsc4py.PETSc.c:87471: error: for each function it appears in.)
>>> > > src/petsc4py.PETSc.c: In function
>>> > > ‘__pyx_pf_8petsc4py_5PETSc_3KSP_getNormType’:
>>> > > src/petsc4py.PETSc.c:88847: error: ‘KSP_NORM_NO’ undeclared (first
>>> use in
>>> > > this function)
>>> > > src/petsc4py.PETSc.c: In function ‘initPETSc’:
>>> > > src/petsc4py.PETSc.c:131697: error: ‘KSP_NORM_NO’ undeclared (first
>>> use in
>>> > > this function)
>>> > > error: command 'mpicc' failed with exit status 1
>>> > > make[1]: *** [petsc4py] Error 1
>>> > >
>>> > >
>>> > >
>>> > >
>>> >
>>> >
>>> >
>>> > --
>>> > =========================
>>> > Srinath Vadlamani, PhD.
>>> > Tech-X Corp. Research Scientist
>>> > 5621 Arapahoe Ave. Suite A
>>> > Boulder, CO 80303
>>> > 303-996-2034
>>> > =========================
>>> >
>>>
>>>
>>>
>>
>>
>> --
>> =========================
>> Srinath Vadlamani, PhD.
>> Tech-X Corp. Research Scientist
>> 5621 Arapahoe Ave. Suite A
>> Boulder, CO 80303
>> 303-996-2034
>> =========================
>>
>>
>
>
> --
> What most experimenters take for granted before they begin their
> experiments is infinitely more interesting than any results to which their
> experiments lead.
> -- Norbert Wiener
>

-- 
=========================
Srinath Vadlamani, PhD.
Tech-X Corp. Research Scientist
5621 Arapahoe Ave. Suite A
Boulder, CO 80303
303-996-2034
=========================
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/petsc-dev/attachments/20101115/6368a615/attachment.html>