source: general/prog/rust.xml@ a0ad432

trunk
Last change on this file since a0ad432 was c84b816d, checked in by Xi Ruoyao <xry111@…>, 4 weeks ago

rust: There's one more known failure

I didn't notice this because building with an existing toolchain
(setting build.rustc and build.cargo). When downloading the stage 0
compiler the test seems assuming everyone is using rust.channel = 'dev'
but we are using 'stable' instead.

  • Property mode set to 100644
File size: 29.4 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 "0b00381728b6c005e95194f7e44cff33">
10 <!ENTITY rust-size "191 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 = 125535
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
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 <para>
306 Compile <application>Rust</application> by running the following
307 commands:
308 </para>
309
310<!-- fixed in 1.58.0, retain as a reminder that fixed crates can be used
311<screen><userinput>sed -i -e '/^curl /s/0.4.38/0.4.40/' \
312 -e '/^curl-sys /s/0.4.48/0.4.50/' \
313 src/tools/cargo/Cargo.toml &amp;&amp; -->
314
315<screen><userinput>{ [ ! -e /usr/include/libssh2.h ] ||
316 export LIBSSH2_SYS_USE_PKG_CONFIG=1; } &amp;&amp;
317{ [ ! -e /usr/include/sqlite3.h ] ||
318 export LIBSQLITE3_SYS_USE_PKG_CONFIG=1; } &amp;&amp;
319python3 x.py build</userinput></screen>
320
321 <note>
322 <para>
323 The test suite will generate some messages in the
324 <phrase revision="sysv">system log</phrase>
325 <phrase revision="systemd">systemd journal</phrase>
326 for traps on invalid opcodes, and for segmentation faults.
327 In themselves these are nothing to worry about, just a way for the
328 test to be terminated.
329 </para>
330 </note>
331
332 <para>
333 To run the tests (again using all available CPUs) issue:
334 </para>
335
336<screen remap="test"><userinput>SSL_CERT_DIR=/etc/ssl/certs \
337python3 x.py test --verbose --no-fail-fast --keep-stage-std=1 | \
338 tee rustc-testlog</userinput></screen>
339
340 <!-- Both "unused import: `std::io::BufRead`"
341 Test suite internal issues and the unused imports are removed in
342 https://github.com/rust-lang/rust/pull/126097. -->
343 <para>
344 Three tests named <filename>tests/run-make/print-cfg</filename>,
345 <filename>tests/run-make/print-to-output</filename>, and
346 <literal>core::config::tests::download_ci_llvm</literal> are known to
347 fail.
348 </para>
349
350<!-- Let's just comment this out. Nobody has tested on a system w/o
351 FileCheck for a long time.
352 <para>
353 If <command>FileCheck</command> from <application>LLVM</application> has
354 not been installed, all 47 tests from the <quote>assembly</quote> suite
355 will fail.
356 </para>
357-->
358 <para>
359 As with all large test suites, some tests might fail on some machines -
360 if the number of additional failures is low,
361 check the log for 'failures:' and review lines above that, particularly the
362 'stderr:' lines. Any mention of
363 SIGSEGV or signal 11 in a failing test is a cause for concern.
364 </para>
365
366 <para>
367 If you get any <emphasis>other</emphasis> failing test which reports an
368 issue number then you should search for that issue. For example, when
369 rustc &gt;= 1.41.1 was built with a version of sysllvm before 10.0 the test
370 for issue 69225 failed <ulink
371 url="https://github.com/rust-lang/rust/issues/69225"/> and that should be
372 regarded as a critical failure (they released 1.41.1 because of it).
373 Most other failures will not be critical.
374 </para>
375
376 <para>
377 Therefore, you should determine the number of failures.
378 The number of tests which passed and failed can be found by running:
379 </para>
380
381<!-- split into two lines for narrower screen windows -->
382<screen remap="test"><userinput>grep '^test result:' rustc-testlog |
383 awk '{sum1 += $4; sum2 += $6} END { print sum1 " passed; " sum2 " failed" }'</userinput></screen>
384
385 <para>
386 The other available fields are $8 for those which were ignored
387 (i.e. skipped), $10 for 'measured' and $12 for 'filtered out' but both
388 those last two are probably zero.
389 </para>
390
391 <para>
392 Now, as the &root; user, install the package:
393 </para>
394
395 <note>
396 <para>
397 If <command>sudo</command> or <command>su</command> is invoked for
398 switching to the &root; user, ensure
399 <envar>LIBSSH2_SYS_USE_PKG_CONFIG</envar> and
400 <envar>LIBSQLITE3_SYS_USE_PKG_CONFIG</envar> are correctly passed or
401 the following command may rebuild <command>cargo</command> with
402 shipped copies of libssh2 and sqlite. For <command>sudo</command>,
403 use the
404 <option>--preserve-env=LIB{SSH2,SQLITE3}_SYS_USE_PKG_CONFIG</option>
405 option. For <command>su</command>, do <emphasis>not</emphasis> use
406 the <option>-</option> or <option>--login</option> options.
407 </para>
408 </note>
409
410<screen role='root'><userinput>python3 x.py install rustc std &amp;&amp;
411install -vm755 \
412 build/host/stage1-tools/*/*/{cargo{,-clippy,-fmt},clippy-driver,rustfmt} \
413 /opt/rustc-&rust-version;/bin &amp;&amp;</userinput>
414install -vDm644 \
415 src/tools/cargo/src/etc/_cargo \
416 /opt/rustc-&rust-version;/share/zsh/site-functions/_cargo &amp;&amp;
417install -vm644 src/tools/cargo/src/etc/man/* \
418 /opt/rustc-&rust-version;/share/man/man1</screen>
419
420 <para>
421 Still as the &root; user, fix the installation of documentation
422 and symlink a <application>Zsh</application>
423 completion file into the correct location:
424 </para>
425
426 <screen role='root'><userinput>rm -fv /opt/rustc-&rust-version;/share/doc/rustc-&rust-version;/*.old &amp;&amp;
427install -vm644 README.md \
428 /opt/rustc-&rust-version;/share/doc/rustc-&rust-version; &amp;&amp;
429
430install -vdm755 /usr/share/zsh/site-functions &amp;&amp;
431ln -sfv /opt/rustc/share/zsh/site-functions/_cargo \
432 /usr/share/zsh/site-functions</userinput></screen>
433
434 <para>
435 Finally, unset the exported environment variables:
436 </para>
437
438<screen><userinput>unset LIB{SSH2,SQLITE3}_SYS_USE_PKG_CONFIG</userinput></screen>
439
440 </sect2>
441
442 <sect2 role="commands">
443 <title>Command Explanations</title>
444
445 <para>
446 <command>ln -svfn rustc-&rust-version; /opt/rustc</command>: if this is
447 not the first use of the <filename class="directory">/opt/rustc</filename>
448 symlink, overwrite it by forcing, and use the '-n' flag to avoid getting
449 confusing results from e.g. <command>ls -l</command>.
450 </para>
451
452 <para>
453 <literal>targets = "X86"</literal>: this avoids building all the available
454 linux cross-compilers (AArch64, MIPS, PowerPC, SystemZ, etc). Unfortunately,
455 rust insists on installing source files for these below
456 <filename class="directory">/opt/rustc/lib/src</filename>.
457 </para>
458
459 <para>
460 <literal>extended = true</literal>: this installs several tools
461 (specified by the <literal>tools</literal> entry) alongside
462 <command>rustc</command>.
463 </para>
464
465 <para>
466 <literal>tools = ["cargo", "clippy", "rustdoc", "rustfmt"]</literal>:
467 only build the tools from the 'default' profile in binary command
468 <command>rustup</command> which are recommended for most users.
469 The other tools are unlikely to be useful unless using (old) code
470 analyzers or editing the standard library.
471 </para>
472
473 <para>
474 <literal>channel = "stable"</literal>: this ensures only stable features
475 can be used, the default in <filename>config.toml</filename> is to use
476 development features, which is not appropriate for a released version.
477 </para>
478
479 <!-- comment while using shipped LLVM -->
480 <para>
481 <literal>[target.x86_64-unknown-linux-gnu]</literal>: the syntax of
482 <filename>config.toml</filename> requires an <literal>llvm-config</literal>
483 entry for each target for which system-llvm is to be used. Change the target
484 to <literal>[target.i686-unknown-linux-gnu]</literal> if you are building
485 on 32-bit x86. This whole section may be omitted if you wish to build
486 against the shipped llvm, or do not have clang, but the resulting build will
487 be larger and take longer.
488 </para>
489
490<!--<para>
491 <command>sed -i -e '/^curl /s/0.4.38/0.4.40/' ... </command>: two crates
492 normally downloaded for this release do not correctly initialise
493 <application>curl</application> if using
494 <application>openssl-3.0.0</application>. Upstream has fixed that for a
495 future release, this sed causes the fixed versions to be used.
496 </para>-->
497
498 <!-- https://github.com/alexcrichton/ssh2-rs/issues/173 -->
499 <para>
500 <command>export LIBSSH2_SYS_USE_PKG_CONFIG=1</command>: Allow
501 <command>cargo</command> to link to system libssh2.
502 </para>
503
504 <!-- src/tools/cargo/Cargo.toml is specifying "bundled" as the
505 upstream is suggesting to avoid issues building for Windoge.
506 We don't care about Windoge so override this if we have
507 system sqlite3. -->
508 <para>
509 <command>export LIBSQLITE3_SYS_USE_PKG_CONFIG=1</command>: Allow
510 <command>cargo</command> to link to system sqlite.
511 </para>
512
513<!--<para>
514 <command>export RUSTFLAGS="$RUSTFLAGS -C link-args=-lffi"</command>:
515 This adds a link to libffi to any RUSTFLAGS you may already be passing
516 to the build. On some systems, linking fails to include libffi unless
517 this is used. The reason why this is needed is not clear.
518 2023-01-14 : assumed to be no longer needed, but it is some years
519 since one person reported needing this, keep it commented for the moment.
520 </para>-->
521
522 <!-- https://github.com/alexcrichton/openssl-probe/issues/25 -->
523 <para>
524 <envar>SSL_CERT_DIR=/etc/ssl/certs</envar>: Work around an issue
525 causing test failures with the CA certificate store layout used by
526 <xref linkend='make-ca'/>.
527 </para>
528
529 <para>
530 <parameter>--verbose</parameter>: this switch can sometimes provide more
531 information about a test which fails.
532 </para>
533
534 <para>
535 <parameter>--no-fail-fast</parameter>: this switch ensures that the test suite
536 will not stop at the first error.
537 </para>
538
539 <para>
540 <parameter>--keep-stage-std 1</parameter>: this switch prevents
541 <command>x.py test</command> from rebuilding the entire package for
542 some unknown reason.
543 </para>
544
545 <!-- https://github.com/rust-lang/rust/issues/94147
546 Do a manual installation for these 5 binaries for 1.80.0, the
547 build system insists to rebuild them even with this.
548 <para>
549 <parameter>- -stage=1</parameter>: this switch works around an issue
550 causing some Rustc components unnecessarily rebuilt running
551 <command>python3 x.py install</command>.
552 </para>-->
553
554 <para>
555 <command>install ... /opt/rustc-&rust-version;/...</command>:
556 these commands explicitly install some Rust components. They are
557 used instead of relying on <command>x.py install</command> because the
558 latter would rebuild these components for some unknown reason.
559 </para>
560
561 </sect2>
562
563 <sect2 role="configuration">
564 <title>Configuring Rust</title>
565
566 <sect3 id="rustc-config">
567 <title>Configuration Information</title>
568
569 <para>
570 If you installed <application>rustc</application> in
571 <filename class="directory">/opt</filename>, you need to update the
572 following configuration files so that <application>rustc</application>
573 is correctly found by other packages and system processes.
574 </para>
575
576 <para>
577 As the <systemitem class="username">root</systemitem> user, create
578 the <filename>/etc/profile.d/rustc.sh</filename> file:
579 </para>
580
581<screen role="root"><userinput>cat &gt; /etc/profile.d/rustc.sh &lt;&lt; "EOF"
582<literal># Begin /etc/profile.d/rustc.sh
583
584pathprepend /opt/rustc/bin PATH
585
586# End /etc/profile.d/rustc.sh</literal>
587EOF</userinput></screen>
588
589 <para>
590 Immediately after installation, update the current PATH
591 for your current shell as a normal user:
592 </para>
593
594<screen><userinput>source /etc/profile.d/rustc.sh</userinput></screen>
595
596 </sect3>
597 </sect2>
598
599
600 <sect2 role="content">
601 <title>Contents</title>
602
603 <segmentedlist>
604 <segtitle>Installed Programs</segtitle>
605 <segtitle>Installed Libraries</segtitle>
606 <segtitle>Installed Directories</segtitle>
607
608 <seglistitem>
609 <seg>
610 cargo-clippy, cargo-fmt, cargo, clippy-driver, rust-gdb,
611 rust-gdbgui, rust-lldb, rustc, rustdoc, and rustfmt
612 </seg>
613 <seg>
614 librustc-driver-&lt;16-byte-hash&gt;.so,
615 libstd-&lt;16-byte-hash&gt;.so, and
616 libtest-&lt;16-byte-hash&gt;.so
617 </seg>
618 <seg>
619 ~/.cargo,
620 /opt/rustc, symbolic link to
621 /opt/rustc-&rust-version;
622 </seg>
623 </seglistitem>
624 </segmentedlist>
625
626 <variablelist>
627 <bridgehead renderas="sect3">Short Descriptions</bridgehead>
628 <?dbfo list-presentation="list"?>
629 <?dbhtml list-presentation="table"?>
630
631 <varlistentry id="cargo-clippy">
632 <term><command>cargo-clippy</command></term>
633 <listitem>
634 <para>
635 provides lint checks for a cargo package
636 </para>
637 <indexterm zone="rust cargo-clippy">
638 <primary sortas="b-cargo-clippy">cargo-clippy</primary>
639 </indexterm>
640 </listitem>
641 </varlistentry>
642
643 <varlistentry id="cargo-fmt">
644 <term><command>cargo-fmt</command></term>
645 <listitem>
646 <para>
647 formats all bin and lib files of the current crate using
648 rustfmt
649 </para>
650 <indexterm zone="rust cargo-fmt">
651 <primary sortas="b-cargo-fmt">cargo-fmt</primary>
652 </indexterm>
653 </listitem>
654 </varlistentry>
655
656<!-- <varlistentry id="cargo-miri">
657 <term><command>cargo-miri</command></term>
658 <listitem>
659 <para>
660 is for use by Miri to interpret bin crates and tests. It is
661 not installed by default.
662 </para>
663 <indexterm zone="rust cargo-miri">
664 <primary sortas="b-cargo-miri">cargo-miri</primary>
665 </indexterm>
666 </listitem>
667 </varlistentry>-->
668
669 <varlistentry id="cargo">
670 <term><command>cargo</command></term>
671 <listitem>
672 <para>
673 is the Package Manager for Rust
674 </para>
675 <indexterm zone="rust cargo">
676 <primary sortas="b-cargo">cargo</primary>
677 </indexterm>
678 </listitem>
679 </varlistentry>
680
681 <varlistentry id="clippy-driver">
682 <term><command>clippy-driver</command></term>
683 <listitem>
684 <para>
685 provides lint checks for Rust
686 </para>
687 <indexterm zone="rust clippy-driver">
688 <primary sortas="b-clippy-driver">clippy-driver</primary>
689 </indexterm>
690 </listitem>
691 </varlistentry>
692
693<!-- <varlistentry id="miri">
694 <term><command>miri</command></term>
695 <listitem>
696 <para>
697 is an interpreter for Rust's mid-level intermediate representation
698 (MIR). It is not installed by default.
699 </para>
700 <indexterm zone="rust miri">
701 <primary sortas="b-miri">miri</primary>
702 </indexterm>
703 </listitem>
704 </varlistentry>
705
706 <varlistentry id="rls">
707 <term><command>rls</command></term>
708 <listitem>
709 <para>
710 is the Rust Language Server. This can run in the background to
711 provide IDEs, editors, and other tools with information about Rust
712 programs
713 </para>
714 <indexterm zone="rust rls">
715 <primary sortas="b-rls">rls</primary>
716 </indexterm>
717 </listitem>
718 </varlistentry>
719
720 <varlistentry id="rust-analyzer">
721 <term><command>rust-analyzer</command></term>
722 <listitem>
723 <para>
724 is an implementation of Language Server Protocol for the Rust
725 programming language.
726 </para>
727 <indexterm zone="rust rust-analyzer">
728 <primary sortas="b-rust-analyzer">rust-analyzer</primary>
729 </indexterm>
730 </listitem>
731 </varlistentry>
732
733 <varlistentry id="rust-demangler">
734 <term><command>rust-demangler</command></term>
735 <listitem>
736 <para>
737 converts a list of Rust mangled symbols into a
738 corresponding list of demangled symbols
739 </para>
740 <indexterm zone="rust rust-demangler">
741 <primary sortas="b-rust-demangler">rust-demangler</primary>
742 </indexterm>
743 </listitem>
744 </varlistentry> -->
745
746 <varlistentry id="rust-gdb">
747 <term><command>rust-gdb</command></term>
748 <listitem>
749 <para>
750 is a wrapper script for gdb, pulling in Python pretty-printing
751 modules installed in
752 <filename class="directory">/opt/rustc-&rust-version;/lib/rustlib/etc</filename>
753 </para>
754 <indexterm zone="rust rust-gdb">
755 <primary sortas="b-rust-gdb">rust-gdb</primary>
756 </indexterm>
757 </listitem>
758 </varlistentry>
759
760 <varlistentry id="rust-gdbgui">
761 <term><command>rust-gdbgui</command></term>
762 <listitem>
763 <para>
764 is a wrapper script for a graphical front end to gdb that runs in a
765 browser
766 </para>
767 <indexterm zone="rust rust-gdbgui">
768 <primary sortas="b-rust-gdbgui">rust-gdbgui</primary>
769 </indexterm>
770 </listitem>
771 </varlistentry>
772
773 <varlistentry id="rust-lldb">
774 <term><command>rust-lldb</command></term>
775 <listitem>
776 <para>
777 is a wrapper script for LLDB (the LLVM debugger)
778 pulling in the Python pretty-printing modules
779 </para>
780 <indexterm zone="rust rust-lldb">
781 <primary sortas="b-rust-lldb">rust=lldb</primary>
782 </indexterm>
783 </listitem>
784 </varlistentry>
785
786 <varlistentry id="rustc">
787 <term><command>rustc</command></term>
788 <listitem>
789 <para>
790 is the rust compiler
791 </para>
792 <indexterm zone="rust rustc">
793 <primary sortas="b-rustc">rustc</primary>
794 </indexterm>
795 </listitem>
796 </varlistentry>
797
798 <varlistentry id="rustdoc">
799 <term><command>rustdoc</command></term>
800 <listitem>
801 <para>
802 generates documentation from rust source code
803 </para>
804 <indexterm zone="rust rustdoc">
805 <primary sortas="b-rustdoc">rustdoc</primary>
806 </indexterm>
807 </listitem>
808 </varlistentry>
809
810 <varlistentry id="rustfmt">
811 <term><command>rustfmt</command></term>
812 <listitem>
813 <para>
814 formats rust code
815 </para>
816 <indexterm zone="rust rustfmt">
817 <primary sortas="b-rustfmt">rustfmt</primary>
818 </indexterm>
819 </listitem>
820 </varlistentry>
821
822 <varlistentry id="libstd">
823 <term><filename class="libraryfile">libstd-&lt;16-byte-hash&gt;.so</filename></term>
824 <listitem>
825 <para>
826 is the Rust Standard Library, the foundation of portable Rust software
827 </para>
828 <indexterm zone="rust libstd">
829 <primary sortas="c-libstd">libstd-&lt;16-byte-hash&gt;.so</primary>
830 </indexterm>
831 </listitem>
832 </varlistentry>
833 </variablelist>
834 </sect2>
835
836</sect1>
Note: See TracBrowser for help on using the repository browser.