@@ -159,14 +159,15 @@ The ``--showme:*`` flags work with all Open MPI wrapper compilers
159159 my_app: my_app.c
160160 $(CC) $(MPI_COMPILE_FLAGS) my_app.c $(MPI_LINK_FLAGS) -o my_app
161161
162- And here 's an example showing how to use ``pkg-config `` |mdash | you
163- may need to add ``$prefix/lib/pkgconfig `` to the ``PKG_CONFIG_PATH ``
162+ Here 's an example showing how to use ``pkg-config `` |mdash | you may
163+ need to add ``$prefix/lib/pkgconfig `` to the ``PKG_CONFIG_PATH ``
164164environment variable for Open MPI's config files to be found:
165165
166166.. code-block :: sh
167167 :linenos:
168168
169- # Show the flags necessary to compile MPI C applications
169+ # Show the flags necessary to compile MPI C applications.
170+ # Set PKG_CONFIG_PATH as relevant for your Open MPI installation.
170171 shell$ export PKG_CONFIG_PATH=/opt/openmpi/lib/pkgconfig
171172 shell$ pkg-config ompi-c --cflags
172173
@@ -484,7 +485,7 @@ This behavior can be disabled by configuring Open MPI with the
484485Can I build 100% static MPI applications?
485486-----------------------------------------
486487
487- .. caution :: Fully static linking is not for the weak , and it is not
488+ .. caution :: Fully static linking is not for the meek , and it is not
488489 recommended. But it is possible, with some caveats.
489490
490491#. You must have static libraries available for *everything * that your
@@ -546,7 +547,7 @@ following:
546547
547548* ``-static ``: Tell the linker to generate a static executable.
548549* ``-Wl,--whole-archive -lfoo /path/to/plugin.a
549- -Wl,--no-whol -archive ``: Tell the linker to include the entire
550+ -Wl,--no-whole -archive ``: Tell the linker to include the entire
550551 ``foo `` library and the entire ``plugin.a `` archive in the
551552 executable.
552553
0 commit comments