On Wed, Nov 7, 2012 at 3:08 PM, Kirk, Benjamin (JSC-EG311) <benjamin.kirk-1@nasa.gov> wrote:
So --enable-tecplot is the old behavior.
     --enable-tecio controls this woe.

I see.  Thanks for the info, it does indeed work with --disable-tecio.

BTW, perhaps you can comment on the following:  I think I have gotten to the bottom of our troubles with building our own compilers from source on Mac.  If I download and build libtool from source, and change the top-level Makefile's link command to:

@libtool --tag=CXX --quiet --mode=link $(libmesh_CXX) $(libmesh_CXXSHAREDFLAG) -o $(mesh_library) $(objects) $(libmesh_LDFLAGS)

i.e. just *prepend* "libtool --tag=CXX --quiet --mode=link" to what we already have there, most of the random segfaults we were seeing are magically gone!  It works 100% if I also build the triangle shared library in contrib with the same method.

This libtool trick has been tested with both GCC 4.6.x and 4.7.x series compilers, so I don't think the issue was ever compiler-related, just shared-library-creation related.

Some questions:

.) Do you know what magic libtool could possibly be doing here?

.) On the automake branch, I still get the (system-level) segfaults with my hand-built compilers.  Do you know how automake builds shared libraries?  Is there any way I could try this libtool trick with the automake branch of libmesh as well?