I have the --disable-unique-ptr option in my configuration script since it is required by another library I’m using on top of libMesh. Thanks, Simone
On Nov 7, 2016, at 11:49, John Peterson <[email protected]<mailto:[email protected]>> wrote: On Mon, Nov 7, 2016 at 9:28 AM, Rossi, Simone <[email protected]<mailto:[email protected]>> wrote: Dear all, I’m upgrading to PETSc 3.7.4 and I am now compiling the git version of libMesh. On my workstation (using gcc 5.4 and openmpi 2.0.0) I get a compilation error /not_backed_up/srossi/TPL/libmesh/libmesh-git/src/reduced_basis/rb_eim_assembly.C: In member function ‘virtual void libMesh::RBEIMAssembly::evaluate_basis_function(unsigned int, const libMesh::Elem&, const libMesh::QBase&, std::vector<double>&)’: /not_backed_up/srossi/TPL/libmesh/libmesh-git/src/reduced_basis/rb_eim_assembly.C:72:14: error: no match for ‘operator!=’ (operand types are ‘libMesh::AutoPtr<libMesh::QBase>’ and ‘const libmesh_nullptr_t’) if (_qrule != libmesh_nullptr) I solved the error just by changing if (_qrule != libmesh_nullptr) => if (_qrule.get() != libmesh_nullptr) With this change it compiles fine, but I since ’m not using the rb classes and I cannot say if this is the best way to solve this problem. Thanks, the fix looks OK to me, but I'm wondering how you ended up with a libMesh::AutoPtr here. Did you explicitly configure with --disable-unique-ptr perhaps? -- John ------------------------------------------------------------------------------ Developer Access Program for Intel Xeon Phi Processors Access to Intel Xeon Phi processor-based developer platforms. With one year of Intel Parallel Studio XE. Training and support from Colfax. Order your platform today. http://sdm.link/xeonphi _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
