OpenFOAM and FDS incompatible on Ubuntu
 

Hello everyone,

I have been using Openfoam v6 fine on my Ubuntu 16.04. Until recently, I had to install Fire Dynamics Simulator (FDS) on the same machine, and Openfoam gives the following issue:

gharek@davinci:~$ blockMesh
blockMesh: symbol lookup error: /opt/openfoam6/platforms/linux64GccDPInt32Opt/lib/openmpi-system/libPstream.so: undefined symbol: ompi_mpi_op_sum

Checking the openMPI library directory gives the following:

gharek@davinci:~$ ldd $FOAM_LIBBIN/openmpi-system/libPstream.so
linux-vdso.so.1 => (0x00007ffd911e6000)
libmpi.so.12 => /opt/FDS/FDS6/bin/INTEL/mpi/intel64/lib/release/libmpi.so.12 (0x00007f3a0f0fd000)
libstdc++.so.6 => /usr/lib/x86_64-linux-gnu/libstdc++.so.6 (0x00007f3a0ed7b000)
libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f3a0ea72000)
libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1 (0x00007f3a0e85c000)
libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007f3a0e63f000)
libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f3a0e275000)
librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007f3a0e06d000)
libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f3a0de69000)
libfabric.so.1 => /opt/FDS/FDS6/bin/INTEL/mpi/intel64/libfabric/lib/libfabric.so.1 (0x00007f3a0dc30000)
/lib64/ld-linux-x86-64.so.2 (0x00007f3a1259a000)


The output above show that libmpi.so.12 is pointed towards the FDS intel library, which I do not want to use.

Does anyone have any idea how to resolve this issue?

I have tried to add the following line in my .bashrc, but this does not work:

export LD_LIBRARY_PATH=$LD_LIBRARY_PATH:/usr/lib/openmpi/lib/

Any suggestions or ideas? Please thanks.

Gary

Quick answer: I saw that you also asked this on the FSD mailing list: https://groups.google.com/forum/#!ms...s/eqDurDACBQAJ

You can easily separate shell environments (namely in one terminal only use OpenfOAM and in another use FDS) by following the instructions given here: https://openfoamwiki.net/index.php/I...nFOAM_versions

Hi wyldckat,

Thanks for your reply. This issue has been resolved as per your kind suggestion.

Gary