Re: [Libmesh-users] compile libmesh with triangle
On Mon, Nov 7, 2016 at 8:59 PM, Michael Povolotskyi wrote: > Dear Libmesh developers, > > how to compile libmesh with triangle support? I'm using version 1.0.0, > the command is > > ./configure PETSC_DIR=/home/mpovolot/NEMO5/NEMO/libs/petsc/build-real > MPIHOME=/usr/local/include PETSC_ARCH=linux \ > F77="mpif77" CC="mpicc" GCC="gcc" CXX="mpic++" --enable-vtk > --with-vtk-include=/usr/include/vtk \ > --with-vtk-lib=/usr/lib64/vtk/ --disable-tetgen --enable-triangle > --disable-nemesis --disable-cxx11 \ > --enable-parmesh --enable-amr --enable-shared=yes; > > Am I missing something? > Yes, due to the encumbered license under which Triangle is distributed, we do not build it unless the user explicitly passes --disable-strict-lgpl to configure. If you look at your config.log, you should see a warning message along the lines of: "Triangle meshing support is disabled, configure with --disable-strict-lgpl to enable it" -- 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 Libmesh-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-users
[Libmesh-users] compile libmesh with triangle
Dear Libmesh developers, how to compile libmesh with triangle support? I'm using version 1.0.0, the command is ./configure PETSC_DIR=/home/mpovolot/NEMO5/NEMO/libs/petsc/build-real MPIHOME=/usr/local/include PETSC_ARCH=linux \ F77="mpif77" CC="mpicc" GCC="gcc" CXX="mpic++" --enable-vtk --with-vtk-include=/usr/include/vtk \ --with-vtk-lib=/usr/lib64/vtk/ --disable-tetgen --enable-triangle --disable-nemesis --disable-cxx11 \ --enable-parmesh --enable-amr --enable-shared=yes; Am I missing something? Thank you, Michael. -- 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 Libmesh-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-users
Re: [Libmesh-users] compilation error
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 mailto:jwpeter...@gmail.com>> wrote: On Mon, Nov 7, 2016 at 9:28 AM, Rossi, Simone mailto:sro...@email.unc.edu>> 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&)’: /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’ 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 Libmesh-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-users
Re: [Libmesh-users] compilation error
On Mon, 7 Nov 2016, John Peterson wrote: 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? Aha! That's why I didn't get the same error; C++11 defines an override of operator==(unique_ptr, nullptr_t). I'm kind of surprised that this only cropped up in one place. --- Roy-- 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 Libmesh-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-users
Re: [Libmesh-users] compilation error
On Mon, Nov 7, 2016 at 9:28 AM, Rossi, Simone 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&)’: > /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’ 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 Libmesh-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-users
Re: [Libmesh-users] compilation error
On Mon, 7 Nov 2016, Rossi, Simone wrote: 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. This looks correct; I'll put in a patch just as soon as I figure out why my own builds didn't trigger the same compiler failure. I could swear I built a --enable-everything libMesh, using SLEPc, more recently than John's unique_ptr upgrades. --- Roy-- 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 Libmesh-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-users
[Libmesh-users] compilation error
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&)’: /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’ 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, Simone -- 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 Libmesh-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-users
