If you get petsc4py from the git repo, you should be able to checkout the
revision:

2dffbbc88844d69580258d9a372bd8f411609a7a

from Feb 9. That should work wth dolfin 1.4.0.

Johan

On Tue, Dec 9, 2014 at 8:08 PM, Thomas Patrick Kelly <[email protected]> wrote:

> Thanks for the replies,
>
> Unfortunately doflin-1.4.0 is incompatible/unstable with the latest
> petsc4py
>
> https://bitbucket.org/fenics-project/dorsal/issue/24/stable-build-fails-on-dolfin-with-on-petsc
>
> But I have switched to the latest version as it might be easier to find a
> solution withthe latest petsc4py.
>
> I have rerun dolfin with the latest petsc4py (and boost) and everything
> compiles fine except dolfin, which gets stuck on the configuration stage
>
> It gets to --found petsconfg.h and then hangs indefinitely.
>
> Thanks again for the help.
>
> On 9 December 2014 at 11:47, Johan Hake <[email protected]> wrote:
>
>> You need to update petsc4py.
>>
>> Johan
>>
>> On Tue, Dec 9, 2014 at 12:46 PM, Johannes Ring <[email protected]> wrote:
>>
>>> On Tue, Dec 9, 2014 at 6:48 AM, Thomas Patrick Kelly <[email protected]>
>>> wrote:
>>> > Hi,
>>> >
>>> > When installing dolfin, I manage to get to 96%, then the following
>>> errors
>>> > pop up
>>> >
>>> > [ 96%] Building CXX object
>>> > dolfin/swig/modules/mesh/CMakeFiles/_mesh.dir/modulePYTHON_wrap.cxx.o
>>> >
>>> /home/thomaskelly/FEniCS/dolfin/swig/modules/mesh/modulePYTHON_wrap.cxx:2978:21:
>>> > warning: invalid suffix on literal; C++11 requires a space between
>>> literal
>>> > and identifier [-Wliteral-suffix]
>>> >    "in method '" name"', argument "argn" of type '"type"'"
>>> >                      ^
>>> >
>>> /home/thomaskelly/FEniCS/dolfin/swig/modules/mesh/modulePYTHON_wrap.cxx:2978:39:
>>> > warning: invalid suffix on literal; C++11 requires a space between
>>> literal
>>> > and identifier [-Wliteral-suffix]
>>> >    "in method '" name"', argument "argn" of type '"type"'"
>>> >                                        ^
>>> >
>>> /home/thomaskelly/FEniCS/dolfin/swig/modules/mesh/modulePYTHON_wrap.cxx:2980:3:
>>> > warning: invalid suffix on literal; C++11 requires a space between
>>> literal
>>> > and identifier [-Wliteral-suffix]
>>> >    "invalid null reference "SWIG_ArgFail_Fmt(type, name, argn)
>>> >    ^
>>> >
>>> /home/thomaskelly/FEniCS/dolfin/swig/modules/mesh/modulePYTHON_wrap.cxx:2982:3:
>>> > warning: invalid suffix on literal; C++11 requires a space between
>>> literal
>>> > and identifier [-Wliteral-suffix]
>>> >    "in method '"name"', output value of type '"type"'"
>>> >    ^
>>> >
>>> /home/thomaskelly/FEniCS/dolfin/swig/modules/mesh/modulePYTHON_wrap.cxx:2982:20:
>>> > warning: invalid suffix on literal; C++11 requires a space between
>>> literal
>>> > and identifier [-Wliteral-suffix]
>>> >    "in method '"name"', output value of type '"type"'"
>>> >                     ^
>>> >
>>> /home/thomaskelly/FEniCS/dolfin/swig/modules/mesh/modulePYTHON_wrap.cxx: In
>>> > function ‘int SWIG_AsVal_MPI_Comm(PyObject*, MPI_Comm*)’:
>>> >
>>> /home/thomaskelly/FEniCS/dolfin/swig/modules/mesh/modulePYTHON_wrap.cxx:4862:43:
>>> > error: ‘SWIGTYPE_p_MPI_Comm’ was not declared in this scope
>>> >      int res = SWIG_ConvertPtr(input,&argp,SWIGTYPE_p_MPI_Comm, 0);
>>> >                                            ^
>>> >
>>> /home/thomaskelly/FEniCS/dolfin/swig/modules/mesh/modulePYTHON_wrap.cxx:2974:37:
>>> > note: in definition of macro ‘SWIG_ConvertPtr’
>>> >          SWIG_convert_ptr(obj, pptr, type, flags)
>>> >
>>> > The error seems to be "error: ‘SWIGTYPE_p_MPI_Comm’ was not declared
>>> in this
>>> > scope"
>>> >
>>> > dependencies like ufl fiat instant PETSc SLEPc etc have all been built
>>> from
>>> > scratch.  I have tried local installs and system-wide installs.
>>> >
>>> > My platform is Linux CentOS 7.
>>>
>>> I think you need to update SWIG. Which version of SWIG do you have?
>>>
>>> Johannes
>>> _______________________________________________
>>> fenics-support mailing list
>>> [email protected]
>>> http://fenicsproject.org/mailman/listinfo/fenics-support
>>>
>>
>>
>
_______________________________________________
fenics-support mailing list
[email protected]
http://fenicsproject.org/mailman/listinfo/fenics-support

Reply via email to