source: general/prog/rust.xml@ 8dbc9094

12.1 ken/TL2024 lazarus trunk xry111/llvm18
Last change on this file since 8dbc9094 was 8dbc9094, checked in by Douglas R. Reno <renodr@…>, 3 months ago

Update to rustc-1.76.0

  • Property mode set to 100644
File size: 29.1 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 "14a8ac688b461a3127090cad513aee05">
10 <!ENTITY rust-size "155 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 &lfs120_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
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"/> and
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)
177 </para>
178
179 <note>
180 <para>
181 If a recommended dependency is not installed, a shipped copy in the
182 Rustc source tarball will be built and used.
183 </para>
184 </note>
185
186 <bridgehead renderas="sect4">Optional</bridgehead>
187 <para role="optional">
188 <xref linkend="gdb"/> (used by the test suite if it is present),
189 <xref linkend="git"/> (required by the test suite),
190 <ulink url="https://github.com/bytecodealliance/wasmtime/tree/main/cranelift">cranelift</ulink>,
191 <ulink url="https://jemalloc.net/">jemalloc</ulink>,
192 libgccjit (read command explanation in
193 <xref role="nodep" linkend="gcc"/>), and
194 <ulink url='https://libgit2.org/'>libgit2</ulink>
195 </para>
196
197 <para condition="html" role="usernotes">
198 Editor Notes: <ulink url="&blfs-wiki;/rust"/>
199 </para>
200 </sect2>
201
202 <sect2 role="installation">
203 <title>Installation of Rust</title>
204
205 <note>
206 <para>
207 Currently the rust compiler produces SSE2 instructions for 32-bit x86,
208 causing the generated code to be broken on 32-bit systems without a
209 SSE2-capable processor. All x86 processor models released after
210 2004 should be SSE2-capable. Run
211 <command>lscpu | grep sse2</command> as a test. If it outputs
212 anything, your CPU is SSE2-capable and OK. Otherwise you may try
213 to build this package <emphasis>on a SSE2-capable system</emphasis>
214 with the following fix applied:
215 </para>
216
217 <!-- computeroutput used deliberately to stop anyone from copying
218 blindly -->
219<screen role="nodump"><computeroutput>sed 's@pentium4@pentiumpro@' -i \
220 compiler/rustc_target/src/spec/i686_unknown_linux_gnu.rs</computeroutput></screen>
221
222 <para>
223 And copy the resulting
224 <filename class="directory">/opt/rustc-&rust-version;</filename>
225 to the system without SSE2 capability. But this change is still
226 under upstream review and not tested by BLFS editors.
227 </para>
228 </note>
229
230 <para>
231 To install into the
232 <filename class="directory">/opt</filename> directory, remove any
233 existing <filename>/opt/rustc</filename> symlink
234 and create a new directory (i.e. with a different name if trying a
235 modified build of the same version).
236 As the <systemitem class="username">root</systemitem>
237 user:
238 </para>
239
240<screen role="root"><userinput>mkdir -pv /opt/rustc-&rust-version; &amp;&amp;
241ln -svfn rustc-&rust-version; /opt/rustc</userinput></screen>
242
243 <note>
244 <para>
245 If multiple versions of <application>Rust</application> are installed
246 in <filename class="directory">/opt</filename>, changing to another
247 version only requires changing the <filename> /opt/rustc</filename>
248 symbolic link and then running <command>ldconfig</command>.
249 </para>
250 </note>
251
252 <para>
253 If running the test suite, apply a patch to prevent the build
254 system from unnecessarily rebuilding the compiler:
255 </para>
256
257 <screen><userinput>patch -Np1 -i ../rustc-&rust-version;-testsuite_fix-1.patch</userinput></screen>
258
259 <para>
260 Create a suitable <filename>config.toml</filename> file which will
261 configure the build.
262 </para>
263
264<screen><userinput>cat &lt;&lt; EOF &gt; config.toml
265<literal># see config.toml.example for more possible options
266# See the 8.4 book for an old example using shipped LLVM
267# e.g. if not installing clang, or using a version before 13.0
268
269# Tell x.py the editors have reviewed the content of this file
270# and updated it to follow the major changes of the building system,
271# so x.py will not warn us to do such a review.
272change-id = 118703
273
274[llvm]
275# by default, rust will build for a myriad of architectures
276targets = "X86"
277
278# When using system llvm prefer shared libraries
279link-shared = true
280
281[build]
282# omit docs to save time and space (default is to build them)
283docs = false
284
285# install extended tools: cargo, clippy, etc
286extended = true
287
288# Do not query new versions of dependencies online.
289locked-deps = true
290
291# Specify which extended tools (those from the default install).
292tools = ["cargo", "clippy", "rustdoc", "rustfmt"]
293
294# Use the source code shipped in the tarball for the dependencies.
295# The combination of this and the "locked-deps" entry avoids downloading
296# many crates from Internet, and makes the Rustc build more stable.
297vendor = true
298
299[install]
300prefix = "/opt/rustc-&rust-version;"
301docdir = "share/doc/rustc-&rust-version;"
302
303[rust]
304channel = "stable"
305description = "for BLFS &version;"
306
307# BLFS used to not install the FileCheck executable from llvm,
308# so disabled codegen tests. The assembly tests rely on FileCheck
309# and cannot easily be disabled, so those will anyway fail if
310# FileCheck has not been installed.
311#codegen-tests = false
312
313# Enable the same optimizations as the official upstream build.
314lto = "thin"
315codegen-units = 1
316
317[target.x86_64-unknown-linux-gnu]
318# NB the output of llvm-config (i.e. help options) may be
319# dumped to the screen when config.toml is parsed.
320llvm-config = "/usr/bin/llvm-config"
321
322[target.i686-unknown-linux-gnu]
323# NB the output of llvm-config (i.e. help options) may be
324# dumped to the screen when config.toml is parsed.
325llvm-config = "/usr/bin/llvm-config"</literal>
326EOF</userinput></screen>
327
328 <note>
329 <para>
330 The <command>python3 x.py</command> commands may output a warning
331 message complaining <quote><computeroutput>no codegen-backends
332 config matched the requested path to build a codegen
333 backend</computeroutput></quote>. And the provided
334 <quote>suggestion</quote> (<computeroutput>add backend to
335 codegen-backends in config.toml</computeroutput>) will not silence
336 it. This warning is <ulink
337 url='https://github.com/rust-lang/rust/issues/110692'>bogus</ulink>
338 and it should be ignored.
339 </para>
340 </note>
341
342 <para>
343 Compile <application>Rust</application> by running the following
344 commands:
345 </para>
346
347<!-- fixed in 1.58.0, retain as a reminder that fixed crates can be used
348<screen><userinput>sed -i -e '/^curl /s/0.4.38/0.4.40/' \
349 -e '/^curl-sys /s/0.4.48/0.4.50/' \
350 src/tools/cargo/Cargo.toml &amp;&amp; -->
351
352<screen><userinput>{ [ ! -e /usr/include/libssh2.h ] ||
353 export LIBSSH2_SYS_USE_PKG_CONFIG=1; } &amp;&amp;
354python3 x.py build</userinput></screen>
355
356 <note>
357 <para>
358 The test suite will generate some messages in the
359 <phrase revision="sysv">system log</phrase>
360 <phrase revision="systemd">systemd journal</phrase>
361 for traps on invalid opcodes, and for segmentation faults.
362 In themselves these are nothing to worry about, just a way for the
363 test to be terminated.
364 </para>
365 </note>
366
367 <para>
368 To run the tests (again using all available CPUs) issue:
369 </para>
370
371<screen remap="test"><userinput>SSL_CERT_DIR=/etc/ssl/certs \
372python3 x.py test --verbose --no-fail-fast | tee rustc-testlog</userinput></screen>
373
374 <!-- https://github.com/rust-lang/rust/pull/115869 -->
375 <para>
376 Two tests,<filename>tests/ui/issues/issue-21763.rs</filename> and
377 <filename>tests/debuginfo/regression-bad-location-list-67992.rs</filename>,
378 are known to fail.
379 </para>
380
381 <para>
382 If <command>FileCheck</command> from <application>LLVM</application> has
383 not been installed, all 47 tests from the <quote>assembly</quote> suite
384 will fail.
385 </para>
386
387 <para>
388 As with all large test suites, other tests might fail on some machines -
389 if the number of additional failures is low,
390 check the log for 'failures:' and review lines above that, particularly the
391 'stderr:' lines. Any mention of
392 SIGSEGV or signal 11 in a failing test is a cause for concern.
393 </para>
394
395 <para>
396 If you get any <emphasis>other</emphasis> failing test which reports an
397 issue number then you should search for that issue. For example, when
398 rustc &gt;= 1.41.1 was built with a version of sysllvm before 10.0 the test
399 for issue 69225 failed <ulink
400 url="https://github.com/rust-lang/rust/issues/69225"/> and that should be
401 regarded as a critical failure (they released 1.41.1 because of it).
402 Most other failures will not be critical.
403 </para>
404
405 <para>
406 Therefore, you should determine the number of failures.
407 </para>
408
409 <para>
410 The number of tests which passed and failed can be found by running:
411 </para>
412
413<!-- split into two lines for narrower screen windows -->
414<screen remap="test"><userinput>grep '^test result:' rustc-testlog |
415 awk '{sum1 += $4; sum2 += $6} END { print sum1 " passed; " sum2 " failed" }'</userinput></screen>
416
417 <para>
418 The other available fields are $8 for those which were ignored
419 (i.e. skipped), $10 for 'measured' and $12 for 'filtered out' but both
420 those last two are probably zero.
421 </para>
422
423 <para>
424 Now, as the &root; user, install the package:
425 </para>
426
427 <note>
428 <para>
429 If <command>sudo</command> or <command>su</command> is invoked for
430 switching to the &root; user, ensure
431 <envar>LIBSSH2_SYS_USE_PKG_CONFIG</envar> is correctly passed or the
432 following command may completely rebuild this package. For
433 <command>sudo</command>, use the
434 <option>--preserve-env=LIBSSH2_SYS_USE_PKG_CONFIG</option> option.
435 For <command>su</command>, do <emphasis>not</emphasis> use the
436 <option>-</option> or <option>--login</option> options.
437 </para>
438 </note>
439
440<screen role='root'><userinput>python3 x.py install</userinput></screen>
441
442 <!-- https://github.com/rust-lang/rust/issues/115213 -->
443 <para>
444 The building system attempts to install some files twice, and during
445 the second attempt it renames the old one (installed in the first
446 attempt) with the <filename class='extension'>.old</filename> suffix.
447 As the &root; user, remove these files:
448 </para>
449
450 <screen role='root'><userinput>find /opt/rustc-&rust-version; -name "*.old" -delete</userinput></screen>
451
452 <para>
453 Still as the &root; user, symlink a <application>Zsh</application>
454 completion file into the correct location:
455 </para>
456
457<screen role='root'><userinput>install -vdm755 /usr/share/zsh/site-functions &amp;&amp;
458ln -sfv /opt/rustc/share/zsh/site-functions/_cargo \
459 /usr/share/zsh/site-functions</userinput></screen>
460
461 <para>
462 Finally, unset the <envar>LIBSSH2_SYS_USE_PKG_CONFIG</envar> variable:
463 </para>
464
465<screen><userinput>unset LIBSSH2_SYS_USE_PKG_CONFIG</userinput></screen>
466
467 </sect2>
468
469 <sect2 role="commands">
470 <title>Command Explanations</title>
471
472 <para>
473 <command>ln -svfn rustc-&rust-version; /opt/rustc</command>: if this is
474 not the first use of the <filename class="directory">/opt/rustc</filename>
475 symlink, overwrite it by forcing, and use the '-n' flag to avoid getting
476 confusing results from e.g. <command>ls -l</command>.
477 </para>
478
479 <para>
480 <literal>targets = "X86"</literal>: this avoids building all the available
481 linux cross-compilers (AArch64, MIPS, PowerPC, SystemZ, etc). Unfortunately,
482 rust insists on installing source files for these below
483 <filename class="directory">/opt/rustc/lib/src</filename>.
484 </para>
485
486 <para>
487 <literal>extended = true</literal>: this installs several tools
488 (specified by the <literal>tools</literal> entry) alongside
489 <command>rustc</command>.
490 </para>
491
492 <para>
493 <literal>tools = ["cargo", "clippy", "rustdoc", "rustfmt"]</literal>:
494 only build the tools from the 'default' profile in binary command
495 <command>rustup</command> which are recommended for most users.
496 The other tools are unlikely to be useful unless using (old) code
497 analyzers or editing the standard library.
498 </para>
499
500 <para>
501 <literal>channel = "stable"</literal>: this ensures only stable features
502 can be used, the default in <filename>config.toml</filename> is to use
503 development features, which is not appropriate for a released version.
504 </para>
505
506 <!-- comment while using shipped LLVM -->
507 <para>
508 <literal>[target.x86_64-unknown-linux-gnu]</literal>: the syntax of
509 <filename>config.toml</filename> requires an <literal>llvm-config</literal>
510 entry for each target for which system-llvm is to be used. Change the target
511 to <literal>[target.i686-unknown-linux-gnu]</literal> if you are building
512 on 32-bit x86. This whole section may be omitted if you wish to build
513 against the shipped llvm, or do not have clang, but the resulting build will
514 be larger and take longer.
515 </para>
516
517<!--<para>
518 <command>sed -i -e '/^curl /s/0.4.38/0.4.40/' ... </command>: two crates
519 normally downloaded for this release do not correctly initialise
520 <application>curl</application> if using
521 <application>openssl-3.0.0</application>. Upstream has fixed that for a
522 future release, this sed causes the fixed versions to be used.
523 </para>-->
524
525 <!-- https://github.com/alexcrichton/ssh2-rs/issues/173 -->
526 <para>
527 <command>export LIBSSH2_SYS_USE_PKG_CONFIG=1</command>: Allow
528 <command>cargo</command> to link to system libssh2.
529 </para>
530
531<!--<para>
532 <command>export RUSTFLAGS="$RUSTFLAGS -C link-args=-lffi"</command>:
533 This adds a link to libffi to any RUSTFLAGS you may already be passing
534 to the build. On some systems, linking fails to include libffi unless
535 this is used. The reason why this is needed is not clear.
536 2023-01-14 : assumed to be no longer needed, but it is some years
537 since one person reported needing this, keep it commented for the moment.
538 </para>-->
539
540 <!-- https://github.com/alexcrichton/openssl-probe/issues/25 -->
541 <para>
542 <envar>SSL_CERT_DIR=/etc/ssl/certs</envar>: Work around an issue
543 causing test failures with the CA certificate store layout used by
544 <xref linkend='make-ca'/>.
545 </para>
546
547 <para>
548 <parameter>--verbose</parameter>: this switch can sometimes provide more
549 information about a test which fails.
550 </para>
551
552 <para>
553 <parameter>--no-fail-fast</parameter>: this switch ensures that the test suite
554 will not stop at the first error.
555 </para>
556
557 </sect2>
558
559 <sect2 role="configuration">
560 <title>Configuring Rust</title>
561
562 <sect3 id="rustc-config">
563 <title>Configuration Information</title>
564
565 <para>
566 If you installed <application>rustc</application> in
567 <filename class="directory">/opt</filename>, you need to update the
568 following configuration files so that <application>rustc</application>
569 is correctly found by other packages and system processes.
570 </para>
571
572 <para>
573 As the <systemitem class="username">root</systemitem> user, create
574 the <filename>/etc/profile.d/rustc.sh</filename> file:
575 </para>
576
577<screen role="root"><userinput>cat &gt; /etc/profile.d/rustc.sh &lt;&lt; "EOF"
578<literal># Begin /etc/profile.d/rustc.sh
579
580pathprepend /opt/rustc/bin PATH
581
582# Include /opt/rustc/man in the MANPATH variable to access manual pages
583pathappend /opt/rustc/share/man MANPATH
584
585# End /etc/profile.d/rustc.sh</literal>
586EOF</userinput></screen>
587
588 <para>
589 Immediately after installation, update the current PATH
590 for your current shell as a normal user:
591 </para>
592
593<screen><userinput>source /etc/profile.d/rustc.sh</userinput></screen>
594
595 </sect3>
596 </sect2>
597
598
599 <sect2 role="content">
600 <title>Contents</title>
601
602 <segmentedlist>
603 <segtitle>Installed Programs</segtitle>
604 <segtitle>Installed Libraries</segtitle>
605 <segtitle>Installed Directories</segtitle>
606
607 <seglistitem>
608 <seg>
609 cargo-clippy, cargo-fmt, cargo, clippy-driver, rust-gdb,
610 rust-gdbgui, rust-lldb, rustc, rustdoc, and rustfmt
611 </seg>
612 <seg>
613 librustc-driver-&lt;16-byte-hash&gt;.so,
614 libstd-&lt;16-byte-hash&gt;.so, and
615 libtest-&lt;16-byte-hash&gt;.so
616 </seg>
617 <seg>
618 ~/.cargo,
619 /opt/rustc, symbolic link to
620 /opt/rustc-&rust-version;
621 </seg>
622 </seglistitem>
623 </segmentedlist>
624
625 <variablelist>
626 <bridgehead renderas="sect3">Short Descriptions</bridgehead>
627 <?dbfo list-presentation="list"?>
628 <?dbhtml list-presentation="table"?>
629
630 <varlistentry id="cargo-clippy">
631 <term><command>cargo-clippy</command></term>
632 <listitem>
633 <para>
634 provides lint checks for a cargo package
635 </para>
636 <indexterm zone="rust cargo-clippy">
637 <primary sortas="b-cargo-clippy">cargo-clippy</primary>
638 </indexterm>
639 </listitem>
640 </varlistentry>
641
642 <varlistentry id="cargo-fmt">
643 <term><command>cargo-fmt</command></term>
644 <listitem>
645 <para>
646 formats all bin and lib files of the current crate using
647 rustfmt
648 </para>
649 <indexterm zone="rust cargo-fmt">
650 <primary sortas="b-cargo-fmt">cargo-fmt</primary>
651 </indexterm>
652 </listitem>
653 </varlistentry>
654
655<!-- <varlistentry id="cargo-miri">
656 <term><command>cargo-miri</command></term>
657 <listitem>
658 <para>
659 is for use by Miri to interpret bin crates and tests. It is
660 not installed by default.
661 </para>
662 <indexterm zone="rust cargo-miri">
663 <primary sortas="b-cargo-miri">cargo-miri</primary>
664 </indexterm>
665 </listitem>
666 </varlistentry>-->
667
668 <varlistentry id="cargo">
669 <term><command>cargo</command></term>
670 <listitem>
671 <para>
672 is the Package Manager for Rust
673 </para>
674 <indexterm zone="rust cargo">
675 <primary sortas="b-cargo">cargo</primary>
676 </indexterm>
677 </listitem>
678 </varlistentry>
679
680 <varlistentry id="clippy-driver">
681 <term><command>clippy-driver</command></term>
682 <listitem>
683 <para>
684 provides lint checks for Rust
685 </para>
686 <indexterm zone="rust clippy-driver">
687 <primary sortas="b-clippy-driver">clippy-driver</primary>
688 </indexterm>
689 </listitem>
690 </varlistentry>
691
692<!-- <varlistentry id="miri">
693 <term><command>miri</command></term>
694 <listitem>
695 <para>
696 is an interpreter for Rust's mid-level intermediate representation
697 (MIR). It is not installed by default.
698 </para>
699 <indexterm zone="rust miri">
700 <primary sortas="b-miri">miri</primary>
701 </indexterm>
702 </listitem>
703 </varlistentry>
704
705 <varlistentry id="rls">
706 <term><command>rls</command></term>
707 <listitem>
708 <para>
709 is the Rust Language Server. This can run in the background to
710 provide IDEs, editors, and other tools with information about Rust
711 programs
712 </para>
713 <indexterm zone="rust rls">
714 <primary sortas="b-rls">rls</primary>
715 </indexterm>
716 </listitem>
717 </varlistentry>
718
719 <varlistentry id="rust-analyzer">
720 <term><command>rust-analyzer</command></term>
721 <listitem>
722 <para>
723 is an implementation of Language Server Protocol for the Rust
724 programming language.
725 </para>
726 <indexterm zone="rust rust-analyzer">
727 <primary sortas="b-rust-analyzer">rust-analyzer</primary>
728 </indexterm>
729 </listitem>
730 </varlistentry>
731
732 <varlistentry id="rust-demangler">
733 <term><command>rust-demangler</command></term>
734 <listitem>
735 <para>
736 converts a list of Rust mangled symbols into a
737 corresponding list of demangled symbols
738 </para>
739 <indexterm zone="rust rust-demangler">
740 <primary sortas="b-rust-demangler">rust-demangler</primary>
741 </indexterm>
742 </listitem>
743 </varlistentry> -->
744
745 <varlistentry id="rust-gdb">
746 <term><command>rust-gdb</command></term>
747 <listitem>
748 <para>
749 is a wrapper script for gdb, pulling in Python pretty-printing
750 modules installed in
751 <filename class="directory">/opt/rustc-&rust-version;/lib/rustlib/etc</filename>
752 </para>
753 <indexterm zone="rust rust-gdb">
754 <primary sortas="b-rust-gdb">rust-gdb</primary>
755 </indexterm>
756 </listitem>
757 </varlistentry>
758
759 <varlistentry id="rust-gdbgui">
760 <term><command>rust-gdbgui</command></term>
761 <listitem>
762 <para>
763 is a wrapper script for a graphical front end to gdb that runs in a
764 browser
765 </para>
766 <indexterm zone="rust rust-gdbgui">
767 <primary sortas="b-rust-gdbgui">rust-gdbgui</primary>
768 </indexterm>
769 </listitem>
770 </varlistentry>
771
772 <varlistentry id="rust-lldb">
773 <term><command>rust-lldb</command></term>
774 <listitem>
775 <para>
776 is a wrapper script for LLDB (the LLVM debugger)
777 pulling in the Python pretty-printing modules
778 </para>
779 <indexterm zone="rust rust-lldb">
780 <primary sortas="b-rust-lldb">rust=lldb</primary>
781 </indexterm>
782 </listitem>
783 </varlistentry>
784
785 <varlistentry id="rustc">
786 <term><command>rustc</command></term>
787 <listitem>
788 <para>
789 is the rust compiler
790 </para>
791 <indexterm zone="rust rustc">
792 <primary sortas="b-rustc">rustc</primary>
793 </indexterm>
794 </listitem>
795 </varlistentry>
796
797 <varlistentry id="rustdoc">
798 <term><command>rustdoc</command></term>
799 <listitem>
800 <para>
801 generates documentation from rust source code
802 </para>
803 <indexterm zone="rust rustdoc">
804 <primary sortas="b-rustdoc">rustdoc</primary>
805 </indexterm>
806 </listitem>
807 </varlistentry>
808
809 <varlistentry id="rustfmt">
810 <term><command>rustfmt</command></term>
811 <listitem>
812 <para>
813 formats rust code
814 </para>
815 <indexterm zone="rust rustfmt">
816 <primary sortas="b-rustfmt">rustfmt</primary>
817 </indexterm>
818 </listitem>
819 </varlistentry>
820
821 <varlistentry id="libstd">
822 <term><filename class="libraryfile">libstd-&lt;16-byte-hash&gt;.so</filename></term>
823 <listitem>
824 <para>
825 is the Rust Standard Library, the foundation of portable Rust software
826 </para>
827 <indexterm zone="rust libstd">
828 <primary sortas="c-libstd">libstd-&lt;16-byte-hash&gt;.so</primary>
829 </indexterm>
830 </listitem>
831 </varlistentry>
832 </variablelist>
833 </sect2>
834
835</sect1>
Note: See TracBrowser for help on using the repository browser.