On Wed, Nov 7, 2012 at 3:50 PM, Paul T. Bauman <ptbau...@gmail.com> wrote:
> .) On the automake branch, I still get the (system-level) segfaults with
>> my hand-built compilers.
>>
>
> What are the errors?
>
The error is an unhelpful stack trace ending in an obscure system function
called misaligned_stack_error_entering_dyld_stub_binder().
It typically only shows up in opt mode, so the stack traces aren't
super-helpful anyway.
Speaking of stack traces, can anyone recommend a way to run the examples in
the automake branch through a debugger? I should probably try
export LIBMESH_OPTIONS=-on_error_attach_debugger
and see if that works.
>
>
>> Do you know how automake builds shared libraries?
>>
>
> libtool is what takes care of this. Again, you'll see the command it uses
> at link time with the --disable-silent-rules configure option.
>
Thanks, I will try this configure option soon...
Is there any way I could try this libtool trick with the automake branch
>> of libmesh as well?
>>
>
> libtool should be doing the "trick" you showed. So are you in the
> situation that trunk and branch are failing in different ways with
> hand-built GCC?
>
No, trunk and branch fail in the same way with my hand-built GCC compiler.
So I'm thinking if I can get the automake branch to do its linking the
same way as trunk, I can make it work as well.
> Latest automake branch is running cleanly for me (in dbg, need to try the
others).
> Anythign special you guys are feeding to $LIBMESH_RUN or $LIBMESH_OPTIONS?
Definitely try opt mode, that's where I see the segfaults, for example in
adjoints_ex1. No special LIBMESH_RUN or LIBMESH_OPTIONS, just hand-built
compilers and no macports. Not sure if it was mentioned, but macports is
not really an option for us since for some reason our site blocks rsync :-P
> Also, did you rename the libtool executable (e.g. when macports builds
autotools, it
> installs libtool as glibtool), because there is a native libtool
installed that's Apple's
> thing and I'm not sure if glibtool is using it or not.
I built libtool by hand from source (no macports on this box). I'm
*definitely* not using Apple's libtool from /usr/bin! AFAICT, it doesn't
even accept the same arguments as GNU libtool!
Also of note: if you don't have autotools installed on your machine (which
is my case for a stock Mountain Lion laptop) libmesh helpfully builds it
for you, along with a libtool. So on the automake branch, I place
libmesh's libtool first in my path and presumably that is the one used for
linking. This may be another important difference from y'alls macports
machines...
--
John
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_nov
_______________________________________________
Libmesh-devel mailing list
Libmesh-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/libmesh-devel
