Hi Jed, hi John, Thanks very much for your help!
I have used —with-clanguage=cxx because of the complex build. At least for my earlier version I got an error when not using that. I am now building PETSC without support for complex numbers and ensuring that it uses the same compiler as libmesh. I really hope that that works… Best, Kathrin On May 19, 2016, at 12:54 PM, Jed Brown <j...@jedbrown.org> wrote: > John Peterson <jwpeter...@gmail.com> writes: >> One unlikely possibility: did you definitely use the same C++ compiler to >> build both PETSc (since you pass --with-clanguage=cxx) and libmesh? > > We recommend never using --with-clanguage=cxx unless you're on a weird > machine that does not have a functional C compiler. The exported API is > the same in either case. > >> libmesh will pick up mpicxx automatically from your environment, whereas I >> think PETSc may use $CXX by default (?). > > PETSc does not use these environment variables because people always > forget what's in them. (Inconsistent environment variables are probably > the leading cause of broken builds.) If you set them, PETSc's configure > warns. You'd need to ./configure CC=$CC CXX=$CXX CFLAGS=$CFLAGS ... to > get them used. ------------------------------------------------------------------------------ Mobile security can be enabling, not merely restricting. Employees who bring their own devices (BYOD) to work are irked by the imposition of MDM restrictions. Mobile Device Manager Plus allows you to control only the apps on BYO-devices by containerizing them, leaving personal data untouched! https://ad.doubleclick.net/ddm/clk/304595813;131938128;j _______________________________________________ Libmesh-users mailing list Libmesh-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/libmesh-users
