Differences

This shows you the differences between two versions of the page.

--- manual:required_libraries [2016/08/11 19:53] – [Building Boost libraries with MPI from source] zenke
+++ manual:required_libraries [2016/09/01 07:12] (current) – zenke
@@ Line 12: / Line 12: @@
 It might happen that your distribution's Boost version is too old. To install Boost from scratch, first install any versions of the Boost libraries installed on your computer using your stock package manager.
+Then download and build boost from source (with MPI support). To that end, follow the instructions found in the MPI section of the boost website http://www.boost.org/doc/libs/1_61_0/doc/html/mpi/getting_started.html
-Then follow download and build boost from source (with MPI support). To that end, follow the instructions found on the boost website
-http://www.boost.org/doc/libs/1_61_0/doc/html/mpi/getting_started.html
 Before you [[compileauryn|build Auryn]] make sure to delete the ''CMakeCache.txt'' file and all other ''CMakeFiles'' in the build directory to ensure that CMake looks for the new library and creates the needed Makefiles.
-===== Known Issues =====
-  * Spike-loss and random crashes experienced with with process numbers that were not a power of two. (OpenMPI 1.4.3)
+==== Troubleshooting common problems ====
-  * Random communication freezes for large messages (i.e. caused by synchronization in the network -> many spikes in short time intervals).  (OpenMPI 1.5.4)
+If you can compile your Auryn programs, but you see an error along these lines
+<code shell>
+./sim_rc_p10c: error while loading shared libraries: libboost_mpi.so.1.61.0: cannot open shared object file: No such file or directory
+</code>
+it's probably because you have installed Boost under the default path ''/usr/local/lib'', but your environment is only looking in ''/usr/lib'' for dynamically linkable libraries. In this case it is usually enough to update your ''LD_LIBRARY_PATH'' environment variable.
+You could for instance add the following to your ''.bashrc'' if you are using bash:
+<code shell>
+export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/local/lib
+</code>
-When compiled against MPICH2 these problems did not occur.
+See also [[known issues]]