From: Thomas Monjalon <thomas@monjalon.net>
To: dev@dpdk.org
Cc: "Ruifeng Wang" <ruifeng.wang@arm.com>,
"Juraj Linkeš" <juraj.linkes@pantheon.tech>
Subject: [dpdk-dev] [PATCH 1/1] doc: fix build
Date: Tue, 26 Jan 2021 16:07:22 +0100 [thread overview]
Message-ID: <20210126150722.4018058-1-thomas@monjalon.net> (raw)
When removing the label "arm_cross_build_getting_the_prerequisite_library"
in the rework of cross_build_dpdk_for_arm64.rst,
the reference to this section got broken.
It went unnoticed because "ninja -C doc" does not regenerate the file
which is referencing the changed file.
Fixes: eb0e12c0c299 ("doc: add clang to aarch64 cross build guide")
Signed-off-by: Thomas Monjalon <thomas@monjalon.net>
---
doc/guides/platform/bluefield.rst | 11 +++++------
1 file changed, 5 insertions(+), 6 deletions(-)
diff --git a/doc/guides/platform/bluefield.rst b/doc/guides/platform/bluefield.rst
index 824f2bde64..635e414600 100644
--- a/doc/guides/platform/bluefield.rst
+++ b/doc/guides/platform/bluefield.rst
@@ -77,12 +77,11 @@ required:
- libnl-3
- libnl-route-3
-Such header files and libraries can be cross-compiled and installed on to the
-cross toolchain directory like depicted in
-:ref:`arm_cross_build_getting_the_prerequisite_library`, but those can also be
-simply copied from the filesystem of a working BlueField platform. The following
-script can be run on a BlueField platform in order to create a supplementary
-tarball for the cross toolchain.
+Such header files and libraries can be cross-compiled and installed
+in the cross toolchain environment.
+They can also be simply copied from the filesystem of a working BlueField platform.
+The following script can be run on a BlueField platform in order to create
+a supplementary tarball for the cross toolchain.
.. code-block:: console
--
2.30.0
next reply other threads:[~2021-01-26 15:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-26 15:07 Thomas Monjalon [this message]
2021-01-26 15:32 ` Bruce Richardson
2021-01-26 15:35 ` Thomas Monjalon
2021-01-26 15:57 ` Bruce Richardson
2021-01-26 15:32 ` David Marchand
2021-01-26 15:42 ` Thomas Monjalon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210126150722.4018058-1-thomas@monjalon.net \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=juraj.linkes@pantheon.tech \
--cc=ruifeng.wang@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).