[mlpack-git] [mlpack] Segmentation fault with armadillo v5 and up (#431)

[Ryan Curtin]

The only way I can reproduce this is by failing to set `LD_LIBRARY_PATH`, so the runtime linker tries to use a version of libmlpack.so which was compiled with 32-bit `uword`; then it fails.  But compiling out of the box as you suggested, I can't make a libarmadillo.so with 64-bit `uword` and a libmlpack.so with 32-bit `uword`.

So is it possible that there is a libmlpack.so hanging around somewhere still that the runtime linker is picking up on?  (Your output of ldd suggests that this is not the case, since ld seems to be finding the correct libmlpack.so.)

The only other possibility I have not dug further into is that you've used Intel's compiler for Armadillo but gcc for mlpack.  If you use Intel's compiler for mlpack, does this change anything?

---
Reply to this email directly or view it on GitHub:
https://github.com/mlpack/mlpack/issues/431#issuecomment-93534479
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.cc.gatech.edu/pipermail/mlpack-git/attachments/20150415/7d0a9fc9/attachment.html>