On 3/14/11 2:51 PM, Boyce Griffith wrote: > > > On 3/14/11 2:11 PM, John Peterson wrote: >> On Mon, Mar 14, 2011 at 12:04 PM, Boyce >> Griffith<[email protected]> wrote: >>> Crap, that is totally what is happening. I use my own build system, >>> and I >>> did not realize that I needed to set -DDEBUG manually. Adding that flag >>> fixes everything. >> >> >> And I *thought* I was using the libmesh build system, but >> -DDEBUG/-DNDEBUG was recently separated out from libmesh_CXXFLAGS into >> libmesh_CPPFLAGS and so I wasn't getting it either... >> > > Quick question --- I just noticed that compiling with -DDEBUG seems to > yield executables that print out a lot of warnings from OpenMPI (both in > my application codes and in the libMesh examples): > > [boyce-griffiths-mac-pro.local:30268] mca: base: component_find: > "mca_paffinity_darwin.so" does not appear to be a valid paffinity MCA > dynamic component (ignored) > [boyce-griffiths-mac-pro.local:30268] mca: base: component_find: > "mca_paffinity_test.so" does not appear to be a valid paffinity MCA > dynamic component (ignored) > > ... > > Have you all seen this kind of stuff before, and if so, do you have any > ideas on how to fix it/get rid of it?
I'm a moron. I think I screwed up my dynamic libraries while trying to debug this example. -- Boyce ------------------------------------------------------------------------------ Colocation vs. Managed Hosting A question and answer guide to determining the best fit for your organization - today and in the future. http://p.sf.net/sfu/internap-sfd2d _______________________________________________ Libmesh-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/libmesh-devel
