User:gYakovlev/Rust

Resources

This article provides an introduction to using app-lang/rust or dev-lang/rust-bin on Gentoo, optimizing compiled code using safe, sane RUSTFLAGS.

Installation

Emerge

Install

root #emerge --ask dev-lang/rust

or

root #emerge --ask dev-lang/rust-bin

USE fags

USE flags for dev-lang/rust Systems programming language from Mozilla

`big-endian`	Big-endian toolchain support
`clippy`	Install clippy, Rust code linter
`debug`	Enable extra debug codepaths, like asserts and extra output. If you want to get meaningful backtraces see https://wiki.gentoo.org/wiki/Project:Quality_Assurance/Backtraces
`dist`	Install dist tarballs (used for bootstrapping)
`doc`	Add extra documentation (API, Javadoc, etc). It is recommended to enable per package instead of globally
`llvm-libunwind`	Use sys-libs/llvm-libunwind instead of sys-libs/libunwind
`lto`	Enable Link-Time Optimization (LTO) to optimize the build
`miri`	Install miri, an interpreter for Rust's mid-level intermediate representation (requires USE=nightly, sometimes is broken)
`nightly`	Enable nightly (UNSTABLE) features (NOTE: it does not install nightly version, just enables features marked as nightly at time of release)
`parallel-compiler`	Build a multi-threaded rustc (experimental, not tested by upstream)
`profiler`	Build the profiler runtime and rust-demangler tool (needed for '-C profile-generate' or '-C instrument-coverage' codegen opts)
`rust-analyzer`	Install rust-analyzer, A Rust compiler front-end for IDEs (language server)
`rust-src`	Install rust-src, needed by developer tools and for build-std (cross)
`rustfmt`	Install rustfmt, Rust code formatter
`system-bootstrap`	Bootstrap using installed rust compiler
`system-llvm`	Use the system LLVM installation
`test`	Enable dependencies and/or preparations necessary to run tests (usually controlled by FEATURES=test but can be toggled independently)
`verify-sig`	Verify upstream signatures on distfiles
`wasm`	Build support for the wasm32-unknown-unknown target

Data provided by the Gentoo Package Database · Last update: 2024-04-10 17:56 More information about USE flags

USE flags for dev-lang/rust-bin Systems programming language from Mozilla

`big-endian`	Big-endian toolchain support
`clippy`	Install clippy, Rust code linter
`doc`	Add extra documentation (API, Javadoc, etc). It is recommended to enable per package instead of globally
`prefix`	Defines if a Gentoo Prefix offset installation is used
`profiler`	Build the profiler runtime and rust-demangler tool (needed for '-C profile-generate' or '-C instrument-coverage' codegen opts)
`rust-analyzer`	Install rust-analyzer, A Rust compiler front-end for IDEs (language server)
`rust-src`	Install rust-src, needed by developer tools and for build-std (cross)
`rustfmt`	Install rustfmt, Rust code formatter
`verify-sig`	Verify upstream signatures on distfiles

Data provided by the Gentoo Package Database · Last update: 2024-04-10 17:56 More information about USE flags

Switching between rust and rust-bin

root #eselect rust list

Available Rust versions:
  [1]   rust-1.40.0 *

Configuration for use with portage

RUSTFLAGS

CODE Setting RUSTFLAGS in /etc/portage/make.conf

RUSTFLAGS="-C target-cpu=native"

CODE Setting per target RUSTFLAGS in /etc/portage/make.conf

CARGO_TARGET_x86_64_UNKNOWN_LINUX_GNU_RUSTFLAGS="-C target-cpu=znver1"

rustc --print target-cpus

Cargo configuration

Cargo can also be configured through environment variables. For each configuration key of the form foo.bar the environment variable CARGO_FOO_BAR can also be used to define the value. For example the build.jobs key can also be defined by CARGO_BUILD_JOBS.

Environment variables will take precedent over TOML configuration, and currently only integer, boolean, and string keys are supported to be defined by environment variables.

CODE Setting CARGO_* in /etc/portage/make.conf

#quiet build
CARGO_TERM_VERBOSE=false
# override autodetection of MAKEOPTS=-j parameter
CARGO_BUILD_JOBS=2

https://doc.rust-lang.org/cargo/reference/config.html

Describe to the user when the issue described in the "Synopsis" above is indeed applicable in this context.

Be clear in this matter, and use verifiable methods, such as checking output with grep or so...

Known problems

cargo-clippy not available after enabling USEflag and re-installing rust.

Resolution

root #eselect rust set 1

External resources

(This is an optional part.)

If there are additional resources that can be view outside this wiki, list them each with a bullet point here under an "External resources" section:

Visit the Gentoo Forums to acquire even more knowledge!