Sure, will try that next, although I claim the stack trace will be no more illuminating ;-)
On Thu, Nov 8, 2012 at 9:55 AM, Kirk, Benjamin (JSC-EG311) <email@example.com>
Any chance you can manually hack -g in there?
will do it I think...
And in case anyone's curious, here are the different link lines used in the automake and trunk checkouts (with some stuff removed for readability)
/bin/sh ./libtool \
(various .lo objects) \
(various .la objects) \
-L/opt/packages/petsc/3.3-p4/lib -lpetsc \
-L/opt/packages/hypre/2.8.0b/lib -lHYPRE \
-lflapack -lfblas -lmpichf90 -lpthread -lgfortran \
-lquadmath -lm -lmpichcxx -lstdc++ -lpmpich -lmpich \
-lopa -lmpl -lSystem -lgcc_ext.10.5 -ldl
-o /Users/moose/projects/libmesh/lib/x86_64-apple-darwin12.0.0_opt/libmesh.dylib \
(various .o files) \
So I'd say the important differences are the following:
1.) The libtool used (trunk uses my hand-built one, automake uses one that has been generated in libmesh's top-level directory)
2.) automake branch passes more system libraries on the link line ( -lSystem, -lgcc_ext.10.5, -ldl, -lgfortran) than trunk.
I guess next I'll try to have my hand-built libtool (rather than libmesh's) first in my PATH, see if that makes a difference...