Re: [Libmesh-users] Exodus not working

[Lorenzo Z. <za...@ai...>]

I'm not completely sure this is the information you are asking for, but 
the OSX is 10.8.5, and we are using macports. The configuration line we 
are currently using is:


../configure \

--prefix=/home/zanon/Desktop/libmesh_root/installed \

--with-glpk-include=/usr/local/macports108/include \

--with-glpk-lib=/usr/local/macports108/lib \

--with-eigen-include=/usr/local/macports108/include/eigen3 \

--with-hdf5=/usr/local/macports108 \

--with-mpi-dir=/usr/local/macports108/lib/openmpi-gcc48/openmpi \

--enable-petsc \

--enable-slepc \

--enable-mpi \

--enable-examples \

CXX=mpicxx-openmpi-gcc48 CC=mpicc-openmpi-gcc48 FC=mpif90-openmpi-gcc48 
F77=mpif90-openmpi-gcc48 \

CXXFLAGS=-I/usr/X11/include LDFLAGS=-L/usr/X11/lib \


Thanks!

On 5/13/14 5:29 PM, John Peterson wrote:
>
>
>
> On Tue, May 13, 2014 at 9:16 AM, Lorenzo Zanon 
> <za...@ai... <mailto:za...@ai...>> wrote:
>
>     No, this is the only message:
>
>     Program received signal EXC_BAD_ACCESS, Could not access memory.
>     Reason: 13 at address: 0x0000000000000000
>     0x00007fff8ca628a5 in
>     misaligned_stack_error_entering_dyld_stub_binder ()
>
>     (gdb) bt
>
>     #0  0x00007fff8ca628a5 in
>     misaligned_stack_error_entering_dyld_stub_binder ()
>     #1  0x0000000000000061 in ?? ()
>     #2  0x0000000102c19218 in __func__.14673 ()
>
>
>
> The last time I saw this "misaligned_stack_error" stuff was when using 
> the system GCC 4.1.2 compilers on OSX Lion (and possibly Snow Leopard).
>
> This compiler/OS combination is known not to work... it's the last 
> version GPLv2-licensed version of GCC and is really old.
>
> Based on the config files you sent earlier, it looks like you are 
> using macports... is it possible you accidentally compiled something 
> with the OSX system compiler?
>
> -- 
> John