Strange... So, when running it through the debugger I first saw that the type was AUTOMATIC. To double check, I tried running it again and had trouble with the debugger. So, I did a make clean, retried and then subsequently got the error you were reporting, the nonconforming object sizes. AH! I had two versions of libMesh running around. I first had it linked to version 3454 which produced the type error. With it linked to one I downloaded this morning i got the nonconforming object sizes. Hmmm... I still don't know what it would be.
(Note: I do not usually have two versions hanging around, I had just downloaded the second one to see if it would make a difference, but apparently I did not modify my definition of LIBMESH_DIR....) Andrea On Tue, Oct 20, 2009 at 5:54 PM, Roy Stogner <[email protected]>wrote: > > On Tue, 20 Oct 2009, Andrea Hawkins wrote: > > Perhaps the difference is our PETSc versions? I'm using an older one, >> 2.3.3-p13. >> > > 2.3.3-p15 is what I'm configured for at the moment... > > Could you run your setup through the debugger and see what it says the > vector type is? It sounds like there's garbage data being written > somewhere and our different compiler/version/etc. is just causing that > to manifest in different ways. I'll try again with a debug-mode PETSc > and see if that gives a different error. > --- > Roy > ------------------------------------------------------------------------------ Come build with us! The BlackBerry(R) Developer Conference in SF, CA is the only developer event you need to attend this year. Jumpstart your developing skills, take BlackBerry mobile applications to market and stay ahead of the curve. Join us from November 9 - 12, 2009. Register now! http://p.sf.net/sfu/devconference _______________________________________________ Libmesh-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-users
