Rustc-1.37.0

Installation of Rust

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

mkdir /opt/rustc-1.37.0             &&
ln -svfin rustc-1.37.0 /opt/rustc

Note

If multiple versions of Rust are installed in /opt, changing to another version only requires changing the /opt/rustc symbolic link and then running ldconfig.

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 example using shipped LLVM
# e.g. if not installing clang, or using a version before 8.0.
[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 cargo as well as rust
extended = true

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

[rust]
channel = "stable"
rpath = false

# BLFS does not install the FileCheck executable from llvm,
# so disable codegen tests
codegen-tests = false

[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

Adapt rustc to allow it to build and function with the changes in LLVM-9:

patch -Np1 -i ../rustc-1.37.0-llvm9_fixes-1.patch

Now compile Rust by running the following commands:

export RUSTFLAGS="$RUSTFLAGS -C link-args=-lffi" &&
python3 ./x.py build --exclude src/tools/miri

Note

The testsuite will generate some messages in the system log for traps on invalid opcodes, and for segmentation faults. In themselves these are nothing to worry about, just a way for the test to be terminated.

To run the tests issue python3 ./x.py test --verbose --no-fail-fast | tee rustc-testlog: as with the build, that will use all available CPUs.

The instructions above do not build ARM compilers, so the testsuite will fail and the tests will be reported to end in error, with a backtrace of the last failing test. On a good run, 3 tests which need Thumb (ARM) compilers will fail, all in ui/issues for issues 37131, 49851 and 50993. A fourth test, run-make-fulldeps/sysroot-crates-are-unstable fails, presumably because we are using only stable features. As with all large testsuites, other tests might fail on some machines - if the number of failures is in the single digits, check the log for 'FAILED' 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. A fifth test, run-make-fulldeps/linker-output-non-utf8, is known to fail.

Therefore, you should determine the number of tests, failures, etc. The total number of tests which were considered is found by running:

grep 'running .* tests' rustc-testlog | awk '{ sum += $2 } END { print sum }'

That should report 16499 tests. Similarly, the total tests which failed can be found by running:

grep '^test result:' rustc-testlog | awk  '{ sum += $6 } END { print sum }'

And similarly for the tests which passed use $4, for those which were ignored (i.e. skipped) use $8 (and $10 for 'measured', $12 for 'filtered out' but both are probably zero). The breakdown does not quite match the overall total.

Still as your normal user, do a DESTDIR install:

export LIBSSH2_SYS_USE_PKG_CONFIG=1 &&
DESTDIR=${PWD}/install python3 ./x.py install &&
unset LIBSSH2_SYS_USE_PKG_CONFIG

Now, as the root user install the files from the DESTDIR:

chown -R root:root install &&
cp -a install/* /