From 9becc82dfcfd7b61a1bf17a92c3a9f101b01ea3b Mon Sep 17 00:00:00 2001 From: iarspider Date: Sat, 5 Nov 2022 03:00:16 +0100 Subject: Fix formatting in packaging guide (#33714) --- lib/spack/docs/packaging_guide.rst | 13 +++---------- 1 file changed, 3 insertions(+), 10 deletions(-) (limited to 'lib') diff --git a/lib/spack/docs/packaging_guide.rst b/lib/spack/docs/packaging_guide.rst index b618497497..2ceb4ce051 100644 --- a/lib/spack/docs/packaging_guide.rst +++ b/lib/spack/docs/packaging_guide.rst @@ -4406,16 +4406,9 @@ In addition to invoking the right compiler, the compiler wrappers add flags to the compile line so that dependencies can be easily found. These flags are added for each dependency, if they exist: -Compile-time library search paths -* ``-L$dep_prefix/lib`` -* ``-L$dep_prefix/lib64`` - -Runtime library search paths (RPATHs) -* ``$rpath_flag$dep_prefix/lib`` -* ``$rpath_flag$dep_prefix/lib64`` - -Include search paths -* ``-I$dep_prefix/include`` +* Compile-time library search paths: ``-L$dep_prefix/lib``, ``-L$dep_prefix/lib64`` +* Runtime library search paths (RPATHs): ``$rpath_flag$dep_prefix/lib``, ``$rpath_flag$dep_prefix/lib64`` +* Include search paths: ``-I$dep_prefix/include`` An example of this would be the ``libdwarf`` build, which has one dependency: ``libelf``. Every call to ``cc`` in the ``libdwarf`` -- cgit v1.2.3-60-g2f50