From f36c1eb519b719c1ff7a1ba786f7c5442bd807ed Mon Sep 17 00:00:00 2001
From: "Peter W. Draper" <p.w.draper@durham.ac.uk>
Date: Tue, 5 Apr 2022 17:06:12 +0100
Subject: [PATCH] Add note that we may need to link against the C++ mpi library
 for an MPI enabled VR

---
 .../source/VELOCIraptorInterface/stfwithswift.rst    | 12 ++++++++++++
 1 file changed, 12 insertions(+)

diff --git a/doc/RTD/source/VELOCIraptorInterface/stfwithswift.rst b/doc/RTD/source/VELOCIraptorInterface/stfwithswift.rst
index f09c2759dd..ad6c0afa81 100644
--- a/doc/RTD/source/VELOCIraptorInterface/stfwithswift.rst
+++ b/doc/RTD/source/VELOCIraptorInterface/stfwithswift.rst
@@ -73,6 +73,18 @@ VELOCIraptor twice and create two builds, then use the
 ``--with-velociraptor-mpi`` configure option to point to the MPI build and the
 ``--with-velociraptor`` option to point at the non-MPI build.
 In general ``./configure`` can be run with other options as desired.
+
+If you see reports about missing references to ``MPI::Comm`` and
+similar functions, then you will also need to include the C++ version
+of the MPI library in ``LIBS`` variable as part of the configuration
+(or by setting the ``LIBS`` environment variable), as in:
+
+.. code:: bash
+
+  ./configure --with-velociraptor=/path/to/VELOCIraptor-STF/build/src LIBS=-lmpi++
+
+other names and libraries may be necessary as these are MPI flavour determined.
+
 After this we can run SWIFT with VELOCIraptor, but for this we first need to
 add several lines to the yaml file of our simulation
 
-- 
GitLab