Skip to content

Move backtrace option to the target-specific configuration #54187

Open
@humenda

Description

@humenda

When building a compiler for a target triple which differs from the host triple, it is impossible to express that the host supports libbacktrace, but the target doesn't.
Moving the option from [rust] to [target.xyz] would make this more flexible, allowing the host compiler to be built with backtrace support, while the target isn't.

cc @alexcrichton

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-backtraceArea: BacktracesC-enhancementCategory: An issue proposing an enhancement or a PR with one.T-bootstrapRelevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions