rebuild manuals for host target specifier

Author: zdivelbiss

src/doc/src/commands/cargo-bench.md

@@ -262,7 +262,7 @@ be specified multiple times, which enables all specified features.</dd>
 <ul>
 <li>Any supported target in <code>rustc --print target-list</code>.</li>
 <li><code>"host"</code>, which will internally be substituted by the host’s target. This can be particularly useful if you’re cross-compiling some crates, and don’t want to specify your host’s machine as a target (for instance, an <code>xtask</code> in a shared project that may be worked on by many hosts).</li>
-<li>A path to a custom target specification. See <a href="https://doc.rust-lang.org/rustc/targets/custom.html#custom-target-lookup-path">Custom Target Lookup Path</a> for more information.</li>
+<li>A path to a custom target specification. See <a href="../../rustc/targets/custom.html#custom-target-lookup-path">Custom Target Lookup Path</a> for more information.</li>
 </ul>
 <p>This may also be specified with the <code>build.target</code> <a href="../reference/config.html">config value</a>.</p>
 <p>Note that specifying this flag makes Cargo run in a different mode where the

src/doc/src/commands/cargo-build.md

@@ -177,7 +177,7 @@ be specified multiple times, which enables all specified features.</dd>
 <ul>
 <li>Any supported target in <code>rustc --print target-list</code>.</li>
 <li><code>"host"</code>, which will internally be substituted by the host’s target. This can be particularly useful if you’re cross-compiling some crates, and don’t want to specify your host’s machine as a target (for instance, an <code>xtask</code> in a shared project that may be worked on by many hosts).</li>
-<li>A path to a custom target specification. See <a href="https://doc.rust-lang.org/rustc/targets/custom.html#custom-target-lookup-path">Custom Target Lookup Path</a> for more information.</li>
+<li>A path to a custom target specification. See <a href="../../rustc/targets/custom.html#custom-target-lookup-path">Custom Target Lookup Path</a> for more information.</li>
 </ul>
 <p>This may also be specified with the <code>build.target</code> <a href="../reference/config.html">config value</a>.</p>
 <p>Note that specifying this flag makes Cargo run in a different mode where the

src/doc/src/commands/cargo-check.md

@@ -173,7 +173,7 @@ be specified multiple times, which enables all specified features.</dd>
 <ul>
 <li>Any supported target in <code>rustc --print target-list</code>.</li>
 <li><code>"host"</code>, which will internally be substituted by the host’s target. This can be particularly useful if you’re cross-compiling some crates, and don’t want to specify your host’s machine as a target (for instance, an <code>xtask</code> in a shared project that may be worked on by many hosts).</li>
-<li>A path to a custom target specification. See <a href="https://doc.rust-lang.org/rustc/targets/custom.html#custom-target-lookup-path">Custom Target Lookup Path</a> for more information.</li>
+<li>A path to a custom target specification. See <a href="../../rustc/targets/custom.html#custom-target-lookup-path">Custom Target Lookup Path</a> for more information.</li>
 </ul>
 <p>This may also be specified with the <code>build.target</code> <a href="../reference/config.html">config value</a>.</p>
 <p>Note that specifying this flag makes Cargo run in a different mode where the

src/doc/src/commands/cargo-clean.md

@@ -65,7 +65,7 @@ Defaults to <code>target</code> in the root of the workspace.</dd>
 <ul>
 <li>Any supported target in <code>rustc --print target-list</code>.</li>
 <li><code>"host"</code>, which will internally be substituted by the host’s target. This can be particularly useful if you’re cross-compiling some crates, and don’t want to specify your host’s machine as a target (for instance, an <code>xtask</code> in a shared project that may be worked on by many hosts).</li>
-<li>A path to a custom target specification. See <a href="https://doc.rust-lang.org/rustc/targets/custom.html#custom-target-lookup-path">Custom Target Lookup Path</a> for more information.</li>
+<li>A path to a custom target specification. See <a href="../../rustc/targets/custom.html#custom-target-lookup-path">Custom Target Lookup Path</a> for more information.</li>
 </ul>
 <p>This may also be specified with the <code>build.target</code> <a href="../reference/config.html">config value</a>.</p>
 <p>Note that specifying this flag makes Cargo run in a different mode where the

src/doc/src/commands/cargo-doc.md

@@ -152,7 +152,7 @@ be specified multiple times, which enables all specified features.</dd>
 <ul>
 <li>Any supported target in <code>rustc --print target-list</code>.</li>
 <li><code>"host"</code>, which will internally be substituted by the host’s target. This can be particularly useful if you’re cross-compiling some crates, and don’t want to specify your host’s machine as a target (for instance, an <code>xtask</code> in a shared project that may be worked on by many hosts).</li>
-<li>A path to a custom target specification. See <a href="https://doc.rust-lang.org/rustc/targets/custom.html#custom-target-lookup-path">Custom Target Lookup Path</a> for more information.</li>
+<li>A path to a custom target specification. See <a href="../../rustc/targets/custom.html#custom-target-lookup-path">Custom Target Lookup Path</a> for more information.</li>
 </ul>
 <p>This may also be specified with the <code>build.target</code> <a href="../reference/config.html">config value</a>.</p>
 <p>Note that specifying this flag makes Cargo run in a different mode where the

src/doc/src/commands/cargo-fetch.md

@@ -35,7 +35,7 @@ you plan to use Cargo without a network with the `--offline` flag.
 <ul>
 <li>Any supported target in <code>rustc --print target-list</code>.</li>
 <li><code>"host"</code>, which will internally be substituted by the host’s target. This can be particularly useful if you’re cross-compiling some crates, and don’t want to specify your host’s machine as a target (for instance, an <code>xtask</code> in a shared project that may be worked on by many hosts).</li>
-<li>A path to a custom target specification. See <a href="https://doc.rust-lang.org/rustc/targets/custom.html#custom-target-lookup-path">Custom Target Lookup Path</a> for more information.</li>
+<li>A path to a custom target specification. See <a href="../../rustc/targets/custom.html#custom-target-lookup-path">Custom Target Lookup Path</a> for more information.</li>
 </ul>
 <p>This may also be specified with the <code>build.target</code> <a href="../reference/config.html">config value</a>.</p>
 <p>Note that specifying this flag makes Cargo run in a different mode where the

src/doc/src/commands/cargo-fix.md

@@ -253,7 +253,7 @@ be specified multiple times, which enables all specified features.</dd>
 <ul>
 <li>Any supported target in <code>rustc --print target-list</code>.</li>
 <li><code>"host"</code>, which will internally be substituted by the host’s target. This can be particularly useful if you’re cross-compiling some crates, and don’t want to specify your host’s machine as a target (for instance, an <code>xtask</code> in a shared project that may be worked on by many hosts).</li>
-<li>A path to a custom target specification. See <a href="https://doc.rust-lang.org/rustc/targets/custom.html#custom-target-lookup-path">Custom Target Lookup Path</a> for more information.</li>
+<li>A path to a custom target specification. See <a href="../../rustc/targets/custom.html#custom-target-lookup-path">Custom Target Lookup Path</a> for more information.</li>
 </ul>
 <p>This may also be specified with the <code>build.target</code> <a href="../reference/config.html">config value</a>.</p>
 <p>Note that specifying this flag makes Cargo run in a different mode where the

src/doc/src/commands/cargo-install.md

@@ -218,7 +218,7 @@ be specified multiple times, which enables all specified features.</dd>
 <ul>
 <li>Any supported target in <code>rustc --print target-list</code>.</li>
 <li><code>"host"</code>, which will internally be substituted by the host’s target. This can be particularly useful if you’re cross-compiling some crates, and don’t want to specify your host’s machine as a target (for instance, an <code>xtask</code> in a shared project that may be worked on by many hosts).</li>
-<li>A path to a custom target specification. See <a href="https://doc.rust-lang.org/rustc/targets/custom.html#custom-target-lookup-path">Custom Target Lookup Path</a> for more information.</li>
+<li>A path to a custom target specification. See <a href="../../rustc/targets/custom.html#custom-target-lookup-path">Custom Target Lookup Path</a> for more information.</li>
 </ul>
 <p>This may also be specified with the <code>build.target</code> <a href="../reference/config.html">config value</a>.</p>
 <p>Note that specifying this flag makes Cargo run in a different mode where the

src/doc/src/commands/cargo-package.md

@@ -208,7 +208,7 @@ single quotes or double quotes around each pattern.</dd>
 <ul>
 <li>Any supported target in <code>rustc --print target-list</code>.</li>
 <li><code>"host"</code>, which will internally be substituted by the host’s target. This can be particularly useful if you’re cross-compiling some crates, and don’t want to specify your host’s machine as a target (for instance, an <code>xtask</code> in a shared project that may be worked on by many hosts).</li>
-<li>A path to a custom target specification. See <a href="https://doc.rust-lang.org/rustc/targets/custom.html#custom-target-lookup-path">Custom Target Lookup Path</a> for more information.</li>
+<li>A path to a custom target specification. See <a href="../../rustc/targets/custom.html#custom-target-lookup-path">Custom Target Lookup Path</a> for more information.</li>
 </ul>
 <p>This may also be specified with the <code>build.target</code> <a href="../reference/config.html">config value</a>.</p>
 <p>Note that specifying this flag makes Cargo run in a different mode where the

src/doc/src/commands/cargo-publish.md

@@ -128,7 +128,7 @@ single quotes or double quotes around each pattern.</dd>
 <ul>
 <li>Any supported target in <code>rustc --print target-list</code>.</li>
 <li><code>"host"</code>, which will internally be substituted by the host’s target. This can be particularly useful if you’re cross-compiling some crates, and don’t want to specify your host’s machine as a target (for instance, an <code>xtask</code> in a shared project that may be worked on by many hosts).</li>
-<li>A path to a custom target specification. See <a href="https://doc.rust-lang.org/rustc/targets/custom.html#custom-target-lookup-path">Custom Target Lookup Path</a> for more information.</li>
+<li>A path to a custom target specification. See <a href="../../rustc/targets/custom.html#custom-target-lookup-path">Custom Target Lookup Path</a> for more information.</li>
 </ul>
 <p>This may also be specified with the <code>build.target</code> <a href="../reference/config.html">config value</a>.</p>
 <p>Note that specifying this flag makes Cargo run in a different mode where the