[petsc-dev] use of outdated code in petsc-dev?

[Dmitry Karpeev]

Matt prefers to keep only headers in the PETSc boost tarball.
This means that only a subset of boost should be packaged up.
I'm not sure how to do the right selection, though.
Even then the warnings might stick around, I'm afraid.

Dmitry.

On Wed, Aug 17, 2011 at 10:32 PM, Barry Smith <bsmith at mcs.anl.gov> wrote:
>
>  Satish,
>
>   Can you please do this on this machine please?
>
>   Thanks
>
>  Barry
>
> On Aug 17, 2011, at 1:29 PM, Dmitry Karpeev wrote:
>
>> Updating the boost tarball might do the trick.
>> Dmitry.
>>
>> On Wed, Aug 17, 2011 at 9:57 PM, Barry Smith <bsmith at mcs.anl.gov> wrote:
>>>
>>> [ 93%] Building CXX object CMakeFiles/petsc.dir/src/snes/impls/python/ftn-custom/zpythonsf.c.o
>>> In file included from /usr/include/c++/4.4/backward/hash_set:60,
>>>                 from /sandbox/petsc/petsc-dev-2/arch-linux-cxx-sieve/include/boost/pending/container_traits.hpp:23,
>>>                 from /sandbox/petsc/petsc-dev-2/arch-linux-cxx-sieve/include/boost/graph/detail/adjacency_list.hpp:31,
>>>                 from /sandbox/petsc/petsc-dev-2/arch-linux-cxx-sieve/include/boost/graph/adjacency_list.hpp:324,
>>>                 from /sandbox/petsc/petsc-dev-2/src/ksp/pc/impls/supportgraph/lowstretch.cpp:6:
>>> /usr/include/c++/4.4/backward/backward_warning.h:28:2: warning: #warning This file includes at least one deprecated or antiquated header which may be removed without further notice at a future date. Please use a non-deprecated interface with equivalent functionality instead. For a listing of replacement headers and interfaces, consult the file
>>>
>>>  Anyone know what this is and can fix?
>>>
>>>  Thanks
>>>    Barry
>>>
>>>
>
>