Skip to content

Tracking Issue for Reproducible Build bugs and challenges #129080

@jieyouxu

Description

@jieyouxu

This is a tracking issue for collecting and triaging bugs and challenges that hinder our ability to produce reproducible and deterministic builds.

This tracking issue is used as a hub for connecting to other relevant issues, e.g., bugs or open design questions. This tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature. Instead, open a dedicated issue for the specific matter and add the A-reproducibility Area: Reproducible / deterministic builds label, and tag with OS/architecture/target labels as suitable.

This tracking issue is unlikely to be exhaustive. Please add suitable entries and edit as new issues and PRs pop up or if old issues and PRs are rediscovered.

Copy pastas for the inline labels

A-debuginfo Area: Debugging information in compiled programs (DWARF, PDB, etc.)
A-diagnostics Area: Messages for errors, warnings, and lints
A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues.
A-reproducibility Area: Reproducible / deterministic builds
A-run-make Area: port run-make Makefiles to rmake.rs
A-testsuite Area: The testsuite used to check the correctness of rustc
C-tracking-issue Category: An issue tracking the progress of sth. like the implementation of an RFC
F-trim-paths Feature: trim-paths
T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)
T-cargo Relevant to the cargo team, which will review and decide on the PR/issue.
T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
T-lang Relevant to the language team, which will review and decide on the PR/issue.
T-libs Relevant to the library team, which will review and decide on the PR/issue.
T-libs-api Relevant to the library API team, which will review and decide on the PR/issue.
T-infra Relevant to the infrastructure team, which will review and decide on the PR/issue.
T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue.
O-wasm Target: WASM (WebAssembly), http://webassembly.org/
O-windows Operating system: Windows
O-windows-msvc Toolchain: MSVC, Operating system: Windows
O-windows-gnu Toolchain: GNU, Operating system: Windows
O-macos Operating system: macOS
O-apple Operating system: Apple (macOS, iOS, tvOS, visionOS, watchOS)
O-AArch64 Armv8-A or later processors in AArch64 mode
O-x86_64 Target: x86-64 processors (like x86_64-*) (also known as amd64 and x64)

Bugs and issues

Tracking/meta issues:

Resolved:

Related issues, RFCs, MCPs and discussions

Related PRs

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-debuginfoArea: Debugging information in compiled programs (DWARF, PDB, etc.)A-diagnosticsArea: Messages for errors, warnings, and lintsA-reproducibilityArea: Reproducible / deterministic buildsC-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCD-diagnostic-infraDiagnostics: Issues that affect all diagnostics, or relate to the diagnostic machinery itself.S-tracking-foreverStatus: Never to be closed.T-bootstrapRelevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.T-infraRelevant to the infrastructure team, which will review and decide on the PR/issue.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions