Rustc-1.82.0

Installation of Rust

To install into the /opt directory, remove any existing /opt/rustc symlink and create a new directory (i.e. with a different name if trying a modified build of the same version). As the root user:

mkdir -pv /opt/rustc-1.82.0      &&
ln -svfn rustc-1.82.0 /opt/rustc

Create a suitable config.toml file which will configure the build.

cat << EOF > config.toml
# see config.toml.example for more possible options
# See the 8.4 book for an old example using shipped LLVM
# e.g. if not installing clang, or using a version before 13.0

# Tell x.py the editors have reviewed the content of this file
# and updated it to follow the major changes of the building system,
# so x.py will not warn us to do such a review.
change-id = 129295

[llvm]
# by default, rust will build for a myriad of architectures
targets = "X86"

# When using system llvm prefer shared libraries
link-shared = true

[build]
# omit docs to save time and space (default is to build them)
docs = false

# install extended tools: cargo, clippy, etc
extended = true

# Do not query new versions of dependencies online.
locked-deps = true

# Specify which extended tools (those from the default install).
tools = ["cargo", "clippy", "rustdoc", "rustfmt"]

# Use the source code shipped in the tarball for the dependencies.
# The combination of this and the "locked-deps" entry avoids downloading
# many crates from Internet, and makes the Rustc build more stable.
vendor = true

[install]
prefix = "/opt/rustc-1.82.0"
docdir = "share/doc/rustc-1.82.0"

[rust]
channel = "stable"
description = "for BLFS r12.2-628"

# Enable the same optimizations as the official upstream build.
lto = "thin"
codegen-units = 1

[target.x86_64-unknown-linux-gnu]
# NB the output of llvm-config (i.e. help options) may be
# dumped to the screen when config.toml is parsed.
llvm-config = "/usr/bin/llvm-config"

[target.i686-unknown-linux-gnu]
# NB the output of llvm-config (i.e. help options) may be
# dumped to the screen when config.toml is parsed.
llvm-config = "/usr/bin/llvm-config"
EOF

Now remove some tests triggering a full rebuild of the Rust standard library and compiler, remove a special case for supporting the cargo test suite (that we don't run because it's expected to be running in a Rustc git repository) but triggering a rebuild of cargo when running python3 x.py install, and prevent building one component useless for BLFS:

sed '/MirOpt/d' -i src/bootstrap/src/core/builder.rs &&

sed 's/!path.ends_with("cargo")/true/' \
    -i src/bootstrap/src/core/build_steps/tool.rs &&

sed 's/^.*build_wasm.*$/#[allow(unreachable_code)]&return false;/' \
    -i src/bootstrap/src/lib.rs

Compile Rust by running the following commands:

[ ! -e /usr/include/libssh2.h ] || export LIBSSH2_SYS_USE_PKG_CONFIG=1
[ ! -e /usr/include/sqlite3.h ] || export LIBSQLITE3_SYS_USE_PKG_CONFIG=1
python3 x.py build

To run the tests (again using all available CPUs) issue:

python3 x.py test --verbose --no-fail-fast | tee rustc-testlog

Four tests in the tests/run-make directory are known to fail because they need targets not enabled in the BLFS LLVM-19.1.0 configuration (nor the llvm.targets in config.toml, in case building with the shipped LLVM). One test named core::config::tests::download_ci_llvm is known to fail. And, one test named 121444.rs is known to fail with LLVM 19.1 or newer because a crash is fixed with the new LLVM but the Rustc test harness does not have the concept of unexpected passes.

As with all large test suites, some tests might fail on some machines - if the number of additional failures is low, check the log for 'failures:' and review lines above that, particularly the 'stderr:' lines. Any mention of SIGSEGV or signal 11 in a failing test is a cause for concern.

If you get any other failing test which reports an issue number then you should search for that issue. For example, when rustc >= 1.41.1 was built with a version of sysllvm before 10.0 the test for issue 69225 failed https://github.com/rust-lang/rust/issues/69225 and that should be regarded as a critical failure (they released 1.41.1 because of it). Most other failures will not be critical.

Therefore, you should determine the number of failures. The number of tests which passed and failed can be found by running:

grep '^test result:' rustc-testlog |
 awk '{sum1 += $4; sum2 += $6} END { print sum1 " passed; " sum2 " failed" }'

The other available fields are $8 for those which were ignored (i.e. skipped), $10 for 'measured' and $12 for 'filtered out' but both those last two are probably zero.

Now, as the root user, install the package:

python3 x.py install rustc std &&
python3 x.py install --stage=1 cargo clippy rustfmt

Still as the root user, fix the installation of documentation, symlink a Zsh completion file into the correct location, and move a Bash completion file into the location recommended by the Bash completion maintainers:

rm -fv /opt/rustc-1.82.0/share/doc/rustc-1.82.0/*.old   &&
install -vm644 README.md                                \
               /opt/rustc-1.82.0/share/doc/rustc-1.82.0 &&

install -vdm755 /usr/share/zsh/site-functions      &&
ln -sfv /opt/rustc/share/zsh/site-functions/_cargo \
        /usr/share/zsh/site-functions

mv -v /etc/bash_completion.d/cargo /usr/share/bash-completion/completions

Finally, unset the exported environment variables:

unset LIB{SSH2,SQLITE3}_SYS_USE_PKG_CONFIG

cat > /etc/profile.d/rustc.sh << "EOF"
# Begin /etc/profile.d/rustc.sh

pathprepend /opt/rustc/bin           PATH

# End /etc/profile.d/rustc.sh
EOF

source /etc/profile.d/rustc.sh