Hi John, I have now tried the PETSC versions 3.5.1, 3.5.2, and 3.5.3 and I have got the same error as described below for all versions. Note that I have not tried 3.5.4 since it has been released after the libmesh 0.9.4 release.
I am using MPICH 3.0.4. Could that maybe be an issue? Do you have any further ideas? Best, Kathrin On May 17, 2016, at 3:03 PM, Kathrin Smetana <ksmet...@mit.edu> wrote: > Hi John, > > Thanks very much for your answer! > > On May 17, 2016, at 2:59 PM, John Peterson <jwpeter...@gmail.com> wrote: > >> >> >> On Tue, May 17, 2016 at 12:51 PM, Kathrin Smetana <ksmet...@mit.edu> wrote: >> >> I have just run with the configuration above and I still do not have any >> problems in the optimized mode. >> >> >> OK, maybe I misunderstood. The problem is only when running the dbg >> executable? > > > Yes, that’s true. > >> >> >> I would like to stick to the llibmesh version 0.9.4 for the moment. Which is >> the most recent PETSC version I could use? >> >> 0.9.4 is from February 2015, so it should work with PETSc 3.5.x but probably >> not with 3.6.x. >> >> -- >> John > > Thanks for the info! Then I will try a more recent PETSC version. > > Best, > Kathrin ------------------------------------------------------------------------------ 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
