source: general/prog/rust.xml

trunk
Last change on this file was 5752f35, checked in by Xi Ruoyao <xry111@…>, 2 weeks ago

rust: Remove the hack for non-SSE2 system

We are going to unsupport BLFS on 32-bit x86, and the sed command just
doesn't work for recent Rust releases.

The upstream says you should configure for i586-unknown-linux-gnu (5
instead of 6) if the system does not support SSE2 but I've not tested it
at all. It's unlikely anyone will ever test it (who'll build LFS, LLVM,
and then Rustc on a Pentium III?)

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