source: general/prog/rust.xml@ ba1228a

trunk
Last change on this file since ba1228a was 8cbf4f3, checked in by Xi Ruoyao <xry111@…>, 41 hours ago

Update to rustc-1.82.0

  • Property mode set to 100644
File size: 29.6 KB
Line 
1<?xml version="1.0" encoding="UTF-8"?>
2<!DOCTYPE sect1 PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
3 "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd" [
4 <!ENTITY % general-entities SYSTEM "../../general.ent">
5 %general-entities;
6
7 <!ENTITY rust-download-http "https://static.rust-lang.org/dist/rustc-&rust-version;-src.tar.xz">
8 <!ENTITY rust-download-ftp " ">
9 <!ENTITY rust-md5sum "8d6a14f1c8d0ab03dffbc81f7a839aa7">
10 <!ENTITY rust-size "210 MB">
11 <!ENTITY rust-buildsize "8.9 GB (298 MB installed); add 6.4 GB if running the tests">
12 <!ENTITY rust-time "6.7 SBU (including download time; add 6.2 SBU for tests, both using parallelism=8)">
13]>
14
15<sect1 id="rust" xreflabel="rustc-&rust-version;">
16 <?dbhtml filename="rust.html"?>
17
18
19 <title>Rustc-&rust-version;</title>
20
21 <indexterm zone="rust">
22 <primary sortas="a-rust">Rust</primary>
23 </indexterm>
24
25 <sect2 role="package">
26 <title>Introduction to Rust</title>
27 <para>
28 The <application>Rust</application> programming language is designed
29 to be a safe, concurrent, practical language.
30 </para>
31
32 <para>
33 This package is updated on a six-weekly release cycle. Because it is
34 such a large and slow package to build, is at the moment only required
35 by a few packages in this book, and particularly because newer versions
36 tend to break older mozilla packages, the BLFS editors take the view that
37 it should only be updated when that is necessary (either to fix problems,
38 or to allow a new version of a package to build).
39 </para>
40
41 <para>
42 As with many other programming languages, rustc (the rust compiler)
43 needs a binary from which to bootstrap. It will download a stage0
44 binary at the start of the build, so you cannot compile it without an
45 Internet connection.
46 </para>
47
48 <note>
49 <para>
50 Although BLFS usually installs in <filename
51 class="directory">/usr</filename>, when you later upgrade to a newer
52 version of <application>rust</application> the old libraries in <filename
53 class="directory">/usr/lib/rustlib</filename> will remain, with various
54 hashes in their names, but will not be usable and will waste space. The
55 editors recommend placing the files in the <filename
56 class="directory">/opt</filename> directory. In particular, if you
57 have reason to rebuild with a modified configuration (e.g. using the
58 shipped LLVM after building with shared LLVM, perhaps to compile crates
59 for architectures which the BLFS LLVM build does not support)
60 it is possible for the install to leave a broken
61 <command>cargo</command> program. In such a situation, either remove
62 the existing installation first, or use a different prefix such as
63 /opt/rustc-&rust-version;-build2.
64 </para>
65
66 <para>
67 If you prefer, you can of course change the prefix to <filename
68 class="directory">/usr</filename>.
69 </para>
70 </note>
71
72 <para>
73 The current <application>rustbuild</application> build-system will use
74 all processors, although it does not scale well and often falls
75 back to just using one core while waiting for a library to compile.
76 However it can be mostly limited to a specified number of processors by
77 a combination of adding the switch <literal>--jobs &lt;N&gt;</literal>
78 (e.g. '--jobs 4' to limit to 4 processors) on each invocation of
79 <command>python3 x.py</command> <emphasis>and</emphasis> using an
80 environment variable <envar>CARGO_BUILD_JOBS=&lt;N&gt;</envar>. At the
81 moment this is not effective when some of the rustc tests are run.
82 </para>
83
84 <para>
85 The current version of rust's num_cpus crate now recognizes that cgroups
86 can be used to restrict which processors it is allowed to use. So if your
87 machine lacks DRAM (typically, less than 2 GB DRAM per core) that might be
88 an alternative to taking CPUs offline.
89 Read <xref linkend='build-in-cgroup'/> for how to use a cgroup.
90 </para>
91
92 <para>
93 At the moment <application>Rust</application> does not provide any
94 guarantees of a stable ABI.
95 </para>
96
97 <note>
98 <para>
99 Rustc defaults to building for ALL supported architectures, using a
100 shipped copy of LLVM. In BLFS the build is only for the X86
101 architecture.
102 If you intend to develop rust crates, this build may not be good
103 enough for your purposes.
104 </para>
105 <para>
106 The build times of this version when repeated on the same machine are
107 often reasonably consistent, but as with all compilations using
108 <command>rustc</command> there can be some very slow outliers.
109 </para>
110 </note>
111
112 &lfs122_checked;
113
114 <bridgehead renderas="sect3">Package Information</bridgehead>
115 <itemizedlist spacing="compact">
116 <listitem>
117 <para>
118 Download (HTTP): <ulink url="&rust-download-http;"/>
119 </para>
120 </listitem>
121 <listitem>
122 <para>
123 Download (FTP): <ulink url="&rust-download-ftp;"/>
124 </para>
125 </listitem>
126 <listitem>
127 <para>
128 Download MD5 sum: &rust-md5sum;
129 </para>
130 </listitem>
131 <listitem>
132 <para>
133 Download size: &rust-size;
134 </para>
135 </listitem>
136 <listitem>
137 <para>
138 Estimated disk space required: &rust-buildsize;
139 </para>
140 </listitem>
141 <listitem>
142 <para>
143 Estimated build time: &rust-time;
144 </para>
145 </listitem>
146 </itemizedlist>
147 <!-- only keep this here for reuse in case we need a patch
148 <bridgehead renderas="sect3">Additional Downloads</bridgehead>
149 <itemizedlist spacing="compact">
150 <listitem>
151 <para>
152 Optional patch (recommended if running the test suite):
153 <ulink url="&patch-root;/rustc-&rust-version;-testsuite_fix-1.patch"/>
154 </para>
155 </listitem>
156 </itemizedlist>
157 -->
158 <bridgehead renderas="sect3">Rust Dependencies</bridgehead>
159
160 <bridgehead renderas="sect4">Required</bridgehead>
161 <para role="required">
162 <xref linkend="cmake"/> and
163 <!-- Required for downloading stage 0 binaries.
164 Otherwise it's recommended (if not installed, a vendored copy
165 will be built). -->
166 <xref linkend="curl"/>
167 </para>
168
169 &build-use-internet;
170
171 <bridgehead renderas="sect4">Recommended</bridgehead>
172 <para role="recommended">
173 <xref linkend="libssh2"/>,
174 <xref linkend="llvm"/>
175 (built with -D LLVM_LINK_LLVM_DYLIB=ON so that rust can link to
176 system LLVM instead of building its shipped version), and
177 <xref linkend="sqlite"/>
178 </para>
179
180 <note>
181 <para>
182 If a recommended dependency is not installed, a shipped copy in the
183 Rustc source tarball will be built and used.
184 </para>
185 </note>
186
187 <bridgehead renderas="sect4">Optional</bridgehead>
188 <para role="optional">
189 <xref linkend="gdb"/> (used by the test suite if it is present),
190 <xref linkend="git"/> (required by the test suite),
191 <ulink url="https://github.com/bytecodealliance/wasmtime/tree/main/cranelift">cranelift</ulink>,
192 <ulink url="https://jemalloc.net/">jemalloc</ulink>,
193 libgccjit (read command explanation in
194 <xref role="nodep" linkend="gcc"/>), and
195 <ulink url='https://libgit2.org/'>libgit2</ulink>
196 </para>
197
198 <para condition="html" role="usernotes">
199 Editor Notes: <ulink url="&blfs-wiki;/rust"/>
200 </para>
201 </sect2>
202
203 <sect2 role="installation">
204 <title>Installation of Rust</title>
205
206 <para>
207 To install into the
208 <filename class="directory">/opt</filename> directory, remove any
209 existing <filename>/opt/rustc</filename> symlink
210 and create a new directory (i.e. with a different name if trying a
211 modified build of the same version).
212 As the <systemitem class="username">root</systemitem>
213 user:
214 </para>
215
216<screen role="root"><userinput>mkdir -pv /opt/rustc-&rust-version; &amp;&amp;
217ln -svfn rustc-&rust-version; /opt/rustc</userinput></screen>
218
219 <note>
220 <para>
221 If multiple versions of <application>Rust</application> are installed
222 in <filename class="directory">/opt</filename>, changing to another
223 version only requires changing the <filename> /opt/rustc</filename>
224 symbolic link and then running <command>ldconfig</command>.
225 </para>
226 </note>
227
228 <para>
229 Create a suitable <filename>config.toml</filename> file which will
230 configure the build.
231 </para>
232
233<screen><userinput>cat &lt;&lt; EOF &gt; config.toml
234<literal># see config.toml.example for more possible options
235# See the 8.4 book for an old example using shipped LLVM
236# e.g. if not installing clang, or using a version before 13.0
237
238# Tell x.py the editors have reviewed the content of this file
239# and updated it to follow the major changes of the building system,
240# so x.py will not warn us to do such a review.
241change-id = 129295
242
243[llvm]
244# by default, rust will build for a myriad of architectures
245targets = "X86"
246
247# When using system llvm prefer shared libraries
248link-shared = true
249
250[build]
251# omit docs to save time and space (default is to build them)
252docs = false
253
254# install extended tools: cargo, clippy, etc
255extended = true
256
257# Do not query new versions of dependencies online.
258locked-deps = true
259
260# Specify which extended tools (those from the default install).
261tools = ["cargo", "clippy", "rustdoc", "rustfmt"]
262
263# Use the source code shipped in the tarball for the dependencies.
264# The combination of this and the "locked-deps" entry avoids downloading
265# many crates from Internet, and makes the Rustc build more stable.
266vendor = true
267
268[install]
269prefix = "/opt/rustc-&rust-version;"
270docdir = "share/doc/rustc-&rust-version;"
271
272[rust]
273channel = "stable"
274description = "for BLFS &version;"
275
276# Enable the same optimizations as the official upstream build.
277lto = "thin"
278codegen-units = 1
279
280[target.x86_64-unknown-linux-gnu]
281# NB the output of llvm-config (i.e. help options) may be
282# dumped to the screen when config.toml is parsed.
283llvm-config = "/usr/bin/llvm-config"
284
285[target.i686-unknown-linux-gnu]
286# NB the output of llvm-config (i.e. help options) may be
287# dumped to the screen when config.toml is parsed.
288llvm-config = "/usr/bin/llvm-config"</literal>
289EOF</userinput></screen>
290<!-- It seems gone in 1.81.0 but not confirmed upstream
291 <note>
292 <para>
293 The <command>python3 x.py</command> commands may output a warning
294 message complaining <computeroutput>no codegen-backends
295 config matched the requested path to build a codegen
296 backend</computeroutput>. And the provided
297 <quote>suggestion</quote> (<computeroutput>add backend to
298 codegen-backends in config.toml</computeroutput>) will not silence
299 it. This warning is <ulink
300 url='https://github.com/rust-lang/rust/issues/110692'>bogus</ulink>
301 and it should be ignored.
302 </para>
303 </note>
304-->
305 <!-- https://github.com/rust-lang/rust/issues/128493
306 https://github.com/rust-lang/rust/issues/130018 will be fixed 1.83
307 https://github.com/rust-lang/rust/pull/130034 will be fixed 1.83 -->
308 <para>
309 Now remove some tests triggering a full rebuild of the Rust standard
310 library and compiler, remove a special case for supporting the
311 <command>cargo</command> test suite (that we don't run because it's
312 expected to be running in a Rustc git repository) but triggering a rebuild
313 of <command>cargo</command> when running
314 <command>python3 x.py install</command>, and prevent building one
315 component useless for BLFS:
316 </para>
317
318 <screen><userinput>sed '/MirOpt/d' -i src/bootstrap/src/core/builder.rs &amp;&amp;
319
320sed 's/!path.ends_with("cargo")/true/' \
321 -i src/bootstrap/src/core/build_steps/tool.rs &amp;&amp;
322
323sed 's/^.*build_wasm.*$/#[allow(unreachable_code)]&amp;return false;/' \
324 -i src/bootstrap/src/lib.rs</userinput></screen>
325
326 <para>
327 Compile <application>Rust</application> by running the following
328 commands:
329 </para>
330
331<!-- fixed in 1.58.0, retain as a reminder that fixed crates can be used
332<screen><userinput>sed -i -e '/^curl /s/0.4.38/0.4.40/' \
333 -e '/^curl-sys /s/0.4.48/0.4.50/' \
334 src/tools/cargo/Cargo.toml &amp;&amp; -->
335
336<screen><userinput>[ ! -e /usr/include/libssh2.h ] || export LIBSSH2_SYS_USE_PKG_CONFIG=1
337[ ! -e /usr/include/sqlite3.h ] || export LIBSQLITE3_SYS_USE_PKG_CONFIG=1
338python3 x.py build</userinput></screen>
339
340 <note>
341 <para>
342 The test suite will generate some messages in the
343 <phrase revision="sysv">system log</phrase>
344 <phrase revision="systemd">systemd journal</phrase>
345 for traps on invalid opcodes, and for segmentation faults.
346 In themselves these are nothing to worry about, just a way for the
347 test to be terminated.
348 </para>
349 </note>
350
351 <para>
352 To run the tests (again using all available CPUs) issue:
353 </para>
354
355<screen remap="test"><userinput>python3 x.py test --verbose --no-fail-fast | tee rustc-testlog</userinput></screen>
356
357 <para>
358 Four tests in the
359 <filename class='directory'>tests/run-make</filename> directory are
360 known to fail because they need targets not enabled
361 in the BLFS <xref linkend='llvm'/> configuration (nor the
362 <literal>llvm.targets</literal> in <filename>config.toml</filename>,
363 in case building with the shipped LLVM). One test named
364 <literal>core::config::tests::download_ci_llvm</literal> is known to
365 fail. And, one test named <filename>121444.rs</filename> is known
366 to fail with LLVM 19.1 or newer because a crash is fixed with the new
367 LLVM but the Rustc test harness does not have the concept of
368 unexpected passes.
369 </para>
370
371<!-- Let's just comment this out. Nobody has tested on a system w/o
372 FileCheck for a long time.
373 <para>
374 If <command>FileCheck</command> from <application>LLVM</application> has
375 not been installed, all 47 tests from the <quote>assembly</quote> suite
376 will fail.
377 </para>
378-->
379 <para>
380 As with all large test suites, some tests might fail on some machines -
381 if the number of additional failures is low,
382 check the log for 'failures:' and review lines above that, particularly the
383 'stderr:' lines. Any mention of
384 SIGSEGV or signal 11 in a failing test is a cause for concern.
385 </para>
386
387 <para>
388 If you get any <emphasis>other</emphasis> failing test which reports an
389 issue number then you should search for that issue. For example, when
390 rustc &gt;= 1.41.1 was built with a version of sysllvm before 10.0 the test
391 for issue 69225 failed <ulink
392 url="https://github.com/rust-lang/rust/issues/69225"/> and that should be
393 regarded as a critical failure (they released 1.41.1 because of it).
394 Most other failures will not be critical.
395 </para>
396
397 <para>
398 Therefore, you should determine the number of failures.
399 The number of tests which passed and failed can be found by running:
400 </para>
401
402<!-- split into two lines for narrower screen windows -->
403<screen remap="test"><userinput>grep '^test result:' rustc-testlog |
404 awk '{sum1 += $4; sum2 += $6} END { print sum1 " passed; " sum2 " failed" }'</userinput></screen>
405
406 <para>
407 The other available fields are $8 for those which were ignored
408 (i.e. skipped), $10 for 'measured' and $12 for 'filtered out' but both
409 those last two are probably zero.
410 </para>
411
412 <para>
413 Now, as the &root; user, install the package:
414 </para>
415
416 <note>
417 <para>
418 If <command>sudo</command> or <command>su</command> is invoked for
419 switching to the &root; user, ensure
420 <envar>LIBSSH2_SYS_USE_PKG_CONFIG</envar> and
421 <envar>LIBSQLITE3_SYS_USE_PKG_CONFIG</envar> are correctly passed or
422 the following command may rebuild <command>cargo</command> with
423 shipped copies of libssh2 and sqlite. For <command>sudo</command>,
424 use the
425 <option>--preserve-env=LIB{SSH2,SQLITE3}_SYS_USE_PKG_CONFIG</option>
426 option. For <command>su</command>, do <emphasis>not</emphasis> use
427 the <option>-</option> or <option>--login</option> options.
428 </para>
429 </note>
430
431<screen role='root'><userinput>python3 x.py install rustc std &amp;&amp;
432python3 x.py install --stage=1 cargo clippy rustfmt</userinput></screen>
433
434 <para>
435 Still as the &root; user, fix the installation of documentation,
436 symlink a <application>Zsh</application>
437 completion file into the correct location, and move a
438 <application>Bash</application> completion file into the location
439 recommended by the <application>Bash</application> completion
440 maintainers:
441 </para>
442
443 <screen role='root'><userinput>rm -fv /opt/rustc-&rust-version;/share/doc/rustc-&rust-version;/*.old &amp;&amp;
444install -vm644 README.md \
445 /opt/rustc-&rust-version;/share/doc/rustc-&rust-version; &amp;&amp;
446
447install -vdm755 /usr/share/zsh/site-functions &amp;&amp;
448ln -sfv /opt/rustc/share/zsh/site-functions/_cargo \
449 /usr/share/zsh/site-functions
450
451mv -v /etc/bash_completion.d/cargo /usr/share/bash-completion/completions</userinput></screen>
452
453 <para>
454 Finally, unset the exported environment variables:
455 </para>
456
457<screen><userinput>unset LIB{SSH2,SQLITE3}_SYS_USE_PKG_CONFIG</userinput></screen>
458
459 </sect2>
460
461 <sect2 role="commands">
462 <title>Command Explanations</title>
463
464 <para>
465 <command>ln -svfn rustc-&rust-version; /opt/rustc</command>: if this is
466 not the first use of the <filename class="directory">/opt/rustc</filename>
467 symlink, overwrite it by forcing, and use the '-n' flag to avoid getting
468 confusing results from e.g. <command>ls -l</command>.
469 </para>
470
471 <para>
472 <literal>targets = "X86"</literal>: this avoids building all the available
473 linux cross-compilers (AArch64, MIPS, PowerPC, SystemZ, etc). Unfortunately,
474 rust insists on installing source files for these below
475 <filename class="directory">/opt/rustc/lib/src</filename>.
476 </para>
477
478 <para>
479 <literal>extended = true</literal>: this installs several tools
480 (specified by the <literal>tools</literal> entry) alongside
481 <command>rustc</command>.
482 </para>
483
484 <para>
485 <literal>tools = ["cargo", "clippy", "rustdoc", "rustfmt"]</literal>:
486 only build the tools from the 'default' profile in binary command
487 <command>rustup</command> which are recommended for most users.
488 The other tools are unlikely to be useful unless using (old) code
489 analyzers or editing the standard library.
490 </para>
491
492 <para>
493 <literal>channel = "stable"</literal>: this ensures only stable features
494 can be used, the default in <filename>config.toml</filename> is to use
495 development features, which is not appropriate for a released version.
496 </para>
497
498 <!-- comment while using shipped LLVM -->
499 <para>
500 <literal>[target.x86_64-unknown-linux-gnu]</literal>: the syntax of
501 <filename>config.toml</filename> requires an <literal>llvm-config</literal>
502 entry for each target for which system-llvm is to be used. Change the target
503 to <literal>[target.i686-unknown-linux-gnu]</literal> if you are building
504 on 32-bit x86. This whole section may be omitted if you wish to build
505 against the shipped llvm, or do not have clang, but the resulting build will
506 be larger and take longer.
507 </para>
508
509<!--<para>
510 <command>sed -i -e '/^curl /s/0.4.38/0.4.40/' ... </command>: two crates
511 normally downloaded for this release do not correctly initialise
512 <application>curl</application> if using
513 <application>openssl-3.0.0</application>. Upstream has fixed that for a
514 future release, this sed causes the fixed versions to be used.
515 </para>-->
516
517 <!-- https://github.com/alexcrichton/ssh2-rs/issues/173 -->
518 <para>
519 <command>export LIBSSH2_SYS_USE_PKG_CONFIG=1</command>: Allow
520 <command>cargo</command> to link to system libssh2.
521 </para>
522
523 <!-- src/tools/cargo/Cargo.toml is specifying "bundled" as the
524 upstream is suggesting to avoid issues building for Windoge.
525 We don't care about Windoge so override this if we have
526 system sqlite3. -->
527 <para>
528 <command>export LIBSQLITE3_SYS_USE_PKG_CONFIG=1</command>: Allow
529 <command>cargo</command> to link to system sqlite.
530 </para>
531
532<!--<para>
533 <command>export RUSTFLAGS="$RUSTFLAGS -C link-args=-lffi"</command>:
534 This adds a link to libffi to any RUSTFLAGS you may already be passing
535 to the build. On some systems, linking fails to include libffi unless
536 this is used. The reason why this is needed is not clear.
537 2023-01-14 : assumed to be no longer needed, but it is some years
538 since one person reported needing this, keep it commented for the moment.
539 </para>-->
540
541 <para>
542 <parameter>--verbose</parameter>: this switch can sometimes provide more
543 information about a test which fails.
544 </para>
545
546 <para>
547 <parameter>--no-fail-fast</parameter>: this switch ensures that the test suite
548 will not stop at the first error.
549 </para>
550
551 <!-- https://github.com/rust-lang/rust/issues/94147 -->
552 <para>
553 <parameter>--stage=1</parameter>: this switch works around an issue
554 causing some Rustc components unnecessarily rebuilt running
555 <command>python3 x.py install</command>.
556 </para>
557
558 </sect2>
559
560 <sect2 role="configuration">
561 <title>Configuring Rust</title>
562
563 <sect3 id="rustc-config">
564 <title>Configuration Information</title>
565
566 <para>
567 If you installed <application>rustc</application> in
568 <filename class="directory">/opt</filename>, you need to update the
569 following configuration files so that <application>rustc</application>
570 is correctly found by other packages and system processes.
571 </para>
572
573 <para>
574 As the <systemitem class="username">root</systemitem> user, create
575 the <filename>/etc/profile.d/rustc.sh</filename> file:
576 </para>
577
578<screen role="root"><userinput>cat &gt; /etc/profile.d/rustc.sh &lt;&lt; "EOF"
579<literal># Begin /etc/profile.d/rustc.sh
580
581pathprepend /opt/rustc/bin PATH
582
583# End /etc/profile.d/rustc.sh</literal>
584EOF</userinput></screen>
585
586 <para>
587 Immediately after installation, update the current PATH
588 for your current shell as a normal user:
589 </para>
590
591<screen><userinput>source /etc/profile.d/rustc.sh</userinput></screen>
592
593 </sect3>
594 </sect2>
595
596
597 <sect2 role="content">
598 <title>Contents</title>
599
600 <segmentedlist>
601 <segtitle>Installed Programs</segtitle>
602 <segtitle>Installed Libraries</segtitle>
603 <segtitle>Installed Directories</segtitle>
604
605 <seglistitem>
606 <seg>
607 cargo-clippy, cargo-fmt, cargo, clippy-driver, rust-gdb,
608 rust-gdbgui, rust-lldb, rustc, rustdoc, and rustfmt
609 </seg>
610 <seg>
611 librustc-driver-&lt;16-byte-hash&gt;.so,
612 libstd-&lt;16-byte-hash&gt;.so, and
613 libtest-&lt;16-byte-hash&gt;.so
614 </seg>
615 <seg>
616 ~/.cargo,
617 /opt/rustc, symbolic link to
618 /opt/rustc-&rust-version;
619 </seg>
620 </seglistitem>
621 </segmentedlist>
622
623 <variablelist>
624 <bridgehead renderas="sect3">Short Descriptions</bridgehead>
625 <?dbfo list-presentation="list"?>
626 <?dbhtml list-presentation="table"?>
627
628 <varlistentry id="cargo-clippy">
629 <term><command>cargo-clippy</command></term>
630 <listitem>
631 <para>
632 provides lint checks for a cargo package
633 </para>
634 <indexterm zone="rust cargo-clippy">
635 <primary sortas="b-cargo-clippy">cargo-clippy</primary>
636 </indexterm>
637 </listitem>
638 </varlistentry>
639
640 <varlistentry id="cargo-fmt">
641 <term><command>cargo-fmt</command></term>
642 <listitem>
643 <para>
644 formats all bin and lib files of the current crate using
645 rustfmt
646 </para>
647 <indexterm zone="rust cargo-fmt">
648 <primary sortas="b-cargo-fmt">cargo-fmt</primary>
649 </indexterm>
650 </listitem>
651 </varlistentry>
652
653<!-- <varlistentry id="cargo-miri">
654 <term><command>cargo-miri</command></term>
655 <listitem>
656 <para>
657 is for use by Miri to interpret bin crates and tests. It is
658 not installed by default.
659 </para>
660 <indexterm zone="rust cargo-miri">
661 <primary sortas="b-cargo-miri">cargo-miri</primary>
662 </indexterm>
663 </listitem>
664 </varlistentry>-->
665
666 <varlistentry id="cargo">
667 <term><command>cargo</command></term>
668 <listitem>
669 <para>
670 is the Package Manager for Rust
671 </para>
672 <indexterm zone="rust cargo">
673 <primary sortas="b-cargo">cargo</primary>
674 </indexterm>
675 </listitem>
676 </varlistentry>
677
678 <varlistentry id="clippy-driver">
679 <term><command>clippy-driver</command></term>
680 <listitem>
681 <para>
682 provides lint checks for Rust
683 </para>
684 <indexterm zone="rust clippy-driver">
685 <primary sortas="b-clippy-driver">clippy-driver</primary>
686 </indexterm>
687 </listitem>
688 </varlistentry>
689
690<!-- <varlistentry id="miri">
691 <term><command>miri</command></term>
692 <listitem>
693 <para>
694 is an interpreter for Rust's mid-level intermediate representation
695 (MIR). It is not installed by default.
696 </para>
697 <indexterm zone="rust miri">
698 <primary sortas="b-miri">miri</primary>
699 </indexterm>
700 </listitem>
701 </varlistentry>
702
703 <varlistentry id="rls">
704 <term><command>rls</command></term>
705 <listitem>
706 <para>
707 is the Rust Language Server. This can run in the background to
708 provide IDEs, editors, and other tools with information about Rust
709 programs
710 </para>
711 <indexterm zone="rust rls">
712 <primary sortas="b-rls">rls</primary>
713 </indexterm>
714 </listitem>
715 </varlistentry>
716
717 <varlistentry id="rust-analyzer">
718 <term><command>rust-analyzer</command></term>
719 <listitem>
720 <para>
721 is an implementation of Language Server Protocol for the Rust
722 programming language.
723 </para>
724 <indexterm zone="rust rust-analyzer">
725 <primary sortas="b-rust-analyzer">rust-analyzer</primary>
726 </indexterm>
727 </listitem>
728 </varlistentry>
729
730 <varlistentry id="rust-demangler">
731 <term><command>rust-demangler</command></term>
732 <listitem>
733 <para>
734 converts a list of Rust mangled symbols into a
735 corresponding list of demangled symbols
736 </para>
737 <indexterm zone="rust rust-demangler">
738 <primary sortas="b-rust-demangler">rust-demangler</primary>
739 </indexterm>
740 </listitem>
741 </varlistentry> -->
742
743 <varlistentry id="rust-gdb">
744 <term><command>rust-gdb</command></term>
745 <listitem>
746 <para>
747 is a wrapper script for gdb, pulling in Python pretty-printing
748 modules installed in
749 <filename class="directory">/opt/rustc-&rust-version;/lib/rustlib/etc</filename>
750 </para>
751 <indexterm zone="rust rust-gdb">
752 <primary sortas="b-rust-gdb">rust-gdb</primary>
753 </indexterm>
754 </listitem>
755 </varlistentry>
756
757 <varlistentry id="rust-gdbgui">
758 <term><command>rust-gdbgui</command></term>
759 <listitem>
760 <para>
761 is a wrapper script for a graphical front end to gdb that runs in a
762 browser
763 </para>
764 <indexterm zone="rust rust-gdbgui">
765 <primary sortas="b-rust-gdbgui">rust-gdbgui</primary>
766 </indexterm>
767 </listitem>
768 </varlistentry>
769
770 <varlistentry id="rust-lldb">
771 <term><command>rust-lldb</command></term>
772 <listitem>
773 <para>
774 is a wrapper script for LLDB (the LLVM debugger)
775 pulling in the Python pretty-printing modules
776 </para>
777 <indexterm zone="rust rust-lldb">
778 <primary sortas="b-rust-lldb">rust=lldb</primary>
779 </indexterm>
780 </listitem>
781 </varlistentry>
782
783 <varlistentry id="rustc">
784 <term><command>rustc</command></term>
785 <listitem>
786 <para>
787 is the rust compiler
788 </para>
789 <indexterm zone="rust rustc">
790 <primary sortas="b-rustc">rustc</primary>
791 </indexterm>
792 </listitem>
793 </varlistentry>
794
795 <varlistentry id="rustdoc">
796 <term><command>rustdoc</command></term>
797 <listitem>
798 <para>
799 generates documentation from rust source code
800 </para>
801 <indexterm zone="rust rustdoc">
802 <primary sortas="b-rustdoc">rustdoc</primary>
803 </indexterm>
804 </listitem>
805 </varlistentry>
806
807 <varlistentry id="rustfmt">
808 <term><command>rustfmt</command></term>
809 <listitem>
810 <para>
811 formats rust code
812 </para>
813 <indexterm zone="rust rustfmt">
814 <primary sortas="b-rustfmt">rustfmt</primary>
815 </indexterm>
816 </listitem>
817 </varlistentry>
818
819 <varlistentry id="libstd">
820 <term><filename class="libraryfile">libstd-&lt;16-byte-hash&gt;.so</filename></term>
821 <listitem>
822 <para>
823 is the Rust Standard Library, the foundation of portable Rust software
824 </para>
825 <indexterm zone="rust libstd">
826 <primary sortas="c-libstd">libstd-&lt;16-byte-hash&gt;.so</primary>
827 </indexterm>
828 </listitem>
829 </varlistentry>
830 </variablelist>
831 </sect2>
832
833</sect1>
Note: See TracBrowser for help on using the repository browser.