[petsc-dev] missing include files
Satish Balay
balay at mcs.anl.gov
Thu Mar 17 18:48:16 CDT 2011
for now - I commented these lines out. Once these files are added -
this change can be reverted.
Satish
On Thu, 17 Mar 2011, Lisandro Dalcin wrote:
> On 17 March 2011 18:46, Blaise Bourdin <bourdin at lsu.edu> wrote:
> > Hi,
> >
> > include/finclude/petsc.h references "finclude/petscdmadda.h", "finclude/petscdmcomposite.h", "finclude/petscdmsliced.h", none of which exists in my system.
> >
> > Is the header file wrong or are the header files really missing in the repository?
> >
>
> I think it is the second. However, I'm not sure if the ADDA, COMPOSITE
> and Sliced API's are fully supported in Fortran.
>
> [dalcinl at nikola dev]$ nm linux-gnu/lib/libpetsc.so | grep dmadda
> 0000000000599900 T dmaddagetcorners_
> 00000000005998f0 T dmaddagetghostcorners_
> 0000000000599930 T dmaddagetmatrixns_
> 0000000000599910 T dmaddasetrefinement_
> [dalcinl at nikola dev]$ nm linux-gnu/lib/libpetsc.so | grep dmcomposite
> 0000000000596ed0 T dmcompositeaddarray_
> 0000000000596f00 T dmcompositeadddm_
> 0000000000596f20 T dmcompositecreate_
> 0000000000596ef0 T dmcompositedestroy_
> 0000000000596eb0 T dmcompositegetaccess4_
> 0000000000626970 T dmcompositegetaccessvpvp_
> 0000000000596df0 T dmcompositegetcontext_
> 0000000000596fb0 T dmcompositegetentries1_
> 0000000000596f90 T dmcompositegetentries2_
> 0000000000596f70 T dmcompositegetentries3_
> 0000000000596f50 T dmcompositegetentries4_
> 0000000000596f30 T dmcompositegetentries5_
> 0000000000596e30 T dmcompositegetlocalvectors4_
> 0000000000596e50 T dmcompositerestoreaccess4_
> 0000000000626900 T dmcompositerestoreaccessvpvp_
> 0000000000596e10 T dmcompositerestorelocalvectors4_
> 0000000000596e80 T dmcompositescatter4_
> 0000000000596e00 T dmcompositesetcontext_
> [dalcinl at nikola dev]$ nm linux-gnu/lib/libpetsc.so | grep dmsliced
>
>
> >
> > The problem comes up when compiling a heavily patched version of TAO compatible with petsc-dev
> >
>
> Is this patched version publicly available somewhere? Are you planning
> to contribute it back to TAO? Do it still requires a C++ build of
> PETSc?
>
>
More information about the petsc-dev
mailing list