Skip to content

error: unknown debugging option: dual-proc-macros when running cross tests #59110

Closed
@mati865

Description

@mati865

I'm working on tests for dynamic musl (#58575) and since #58013 I'm hitting:

Building stage0 compiler artifacts (x86_64-unknown-linux-gnu -> x86_64-unknown-linux-musl)
error: failed to run `rustc` to learn about target-specific information

Caused by:
  process didn't exit successfully: `/checkout/obj/build/bootstrap/debug/rustc - --crate-name ___ --print=file-names -C target-feature=-crt-static --target x86_64-unknown-linux-musl --crate-type bin --crate-type rlib --crate-type dylib --crate-type cdylib --crate-type staticlib --crate-type proc-macro` (exit code: 1)
--- stderr
error: unknown debugging option: `dual-proc-macros`

[RUSTC-TIMING] ___ test:false 0.011

command did not execute successfully: "/checkout/obj/build/x86_64-unknown-linux-gnu/stage0/bin/cargo" "build" "--target" "x86_64-unknown-linux-musl" "-Zdual-proc-macros" "-j" "16" "--release" "--locked" "--features" "" "--manifest-path" "/checkout/src/rustc/Cargo.toml" "--message-format" "json"
expected success, got: exit code: 101
failed to run: /checkout/obj/build/bootstrap/debug/bootstrap test --host x86_64-unknown-linux-musl --target x86_64-unknown-linux-musl

Error comes from:

cmd.arg("-Zdual-proc-macros");

The configuration is very unusual because the builder is x86_64-unknown-linux-gnu and both the host and the target are set to x86_64-unknown-linux-musl.

Full log from rebuild: https://gist.github.com/mati865/147c64df0f093117f730c78b66299d86

cc @Zoxc

Metadata

Metadata

Labels

T-bootstrapRelevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap)T-infraRelevant to the infrastructure team, which will review and decide on the PR/issue.regression-from-stable-to-stablePerformance or correctness regression from one stable version to another.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions