On Fri, Nov 10, 2017 at 4:05 PM, Dafang Wang <dafang.w...@jhu.edu> wrote:

> Hi John,
> Please see my replies below.
>
> On 11/10/2017 11:31 AM, John Peterson wrote:
>
>> On Thu, Nov 9, 2017 at 8:32 PM, Dafang Wang <dafang.w...@jhu.edu <mailto:
>> dafang.w...@jhu.edu>> wrote:
>>
>>     Hi,
>>
>>     I got the following error when installing Libmesh v1.0.0 with
>>     PETSC v3.6.4/3.5.4 (neither Petsc worked).
>>
>> What does this mean? What were the error messages? 1.0.0 was tagged in
>> June 2016, PETSc 3.6 was tagged in summer 2015 and should definitely work
>> with that version of libmesh.
>>
>>     I am installing an older version of Libmesh because only that
>>     version is compatible with my user code.
>>
>>
>> I'm curious how extensive the incompatibilities are. It may be something
>> that can be remedied fairly easily with some mailing list support.
>>
> The last time my code was successfully built, it was with Libmesh 1.0.0
> and Petsc 3.5.4; it was built in Aug 2016.  However, I couldn't even
> reproduce the same installation on another linux desktop yesterday.
>
> My code got different errors when compiling with various recent versions
> of Libmesh (see below). It seems Libmesh removed some data structures such
> as "mesh_data.h", so I am not sure how much work it will take to adapt my
> user code to the latest version of Libmesh.
>

Yes, MeshData was deprecated for several years and finally removed in
1.2.0. Were you actually using it in your application? The standard advice
is to store data fields on an ExplicitSystem object, as this approach works
in parallel and on adaptively-refined grids.




>
> _*When compiling my code with Libmesh 1.2.0 and the latest Petsc (both
> were successfully built), I got the following error:*_
> /home/dwang/research/libmesh_mech/latest/CardiacSystemMaker.hpp:7:10:
> fatal error: petsc.h: No such file or directory
>  #include <petsc.h>
>           ^~~~~~~~~
> compilation terminated.
>


There is most likely something wrong with your application Makefile. You
should be using the "libmesh-config --cxxflags" script to pass the list of
the include paths to the compiler while compiling your app...



> make[2]: *** [CMakeFiles/cardiacMech.dir/build.make:92:
> CMakeFiles/cardiacMech.dir/CardiacSystemMaker.cpp.o] Error 1
> [ 33%] Building CXX object CMakeFiles/cardiacMech.dir/CarpMeshIO.cpp.o
> /home/dwang/research/libmesh_mech/latest/CarpMeshIO.cpp:24:10: fatal
> error: libmesh/mesh_data.h: No such file or directory
>  #include <libmesh/mesh_data.h>
>           ^~~~~~~~~~~~~~~~~~~~~
> compilation terminated.
>

Right, the MeshData object was removed.




> ------------------------------------------------------------------------
> *_When compiling my code with Libmesh 1.1.0 and Petsc 3.7.7, I got the
> folliwng error:_*
>
> /home/dwang/research/libmesh_mech/LibmeshMechanic_2017_0701/parallel.cpp:8:15:
> error: template-id ‘send<unsigned int>’ for ‘void
> libMesh::Parallel::Communicator::send(unsigned int, unsigned int&, const
> libMesh::Parallel::MessageTag&) const’ does not match any template
> declaration
>  template void libMesh::Parallel::Communicator::send<unsigned
> int>(unsigned int, unsigned int&, libMesh::Parallel::MessageTag const&)
> const;
>                ^~~~~~~
> In file included from /home/dwang/program/libmesh-1.
> 1.0/RelWithDebInfo/include/libmesh/parallel.h:1302:0,
>                  from /home/dwang/research/libmesh_m
> ech/LibmeshMechanic_2017_0701/utility.hpp:14,
>                  from /home/dwang/research/libmesh_m
> ech/LibmeshMechanic_2017_0701/parallel.cpp:4:
> /home/dwang/program/libmesh-1.1.0/RelWithDebInfo/include/lib
> mesh/parallel_communicator_specializations:114:10: note: candidates are:
> template<class T> void libMesh::Parallel::Communicator::send(unsigned
> int, const std::vector<T>&, const libMesh::Parallel::DataType&,
> libMesh::Parallel::Request&, const libMesh::Parallel::MessageTag&) const
>      void send (const unsigned int dest_processor_id,
>           ^~~~
> /home/dwang/program/libmesh-1.1.0/RelWithDebInfo/include/lib
> mesh/parallel_communicator_specializations:108:10: note:
> template<class T> void libMesh::Parallel::Communicator::send(unsigned
> int, const std::vector<T>&, const libMesh::Parallel::DataType&, const
> libMesh::Parallel::MessageTag&) const
>      void send (const unsigned int dest_processor_id,
>           ^~~~
> /home/dwang/program/libmesh-1.1.0/RelWithDebInfo/include/lib
> mesh/parallel_communicator_specializations:102:10: note:
> template<class T> void libMesh::Parallel::Communicator::send(unsigned
> int, const std::vector<T>&, libMesh::Parallel::Request&, const
> libMesh::Parallel::MessageTag&) const
>      void send (const unsigned int dest_processor_id,



This has nothing to do with PETSc and I don't think it's a version
incompatibility thing either. You might need to post the actual line of
code that triggers this error message for us to diagnose it further. It's
possible that we are missing a particular specialization for
Communicator::Send, but then I am confused how this line of code would have
ever worked...

-- 
John
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Libmesh-users mailing list
Libmesh-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-users

Reply via email to