-
Notifications
You must be signed in to change notification settings - Fork 12.9k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
In 1.64 split-debuginfo = "unpacked" was ignored on Windows while in 1.65 it fails to build #103976
Labels
C-bug
Category: This is a bug.
regression-from-stable-to-stable
Performance or correctness regression from one stable version to another.
Comments
Yatekii
added
C-bug
Category: This is a bug.
regression-untriaged
Untriaged performance or correctness regression.
labels
Nov 4, 2022
rustbot
added
the
I-prioritize
Issue: Indicates that prioritization has been requested for this issue.
label
Nov 4, 2022
GuillaumeGomez
added a commit
to GuillaumeGomez/rust
that referenced
this issue
Nov 8, 2022
Add split-debuginfo print option This option prints all supported values for `-Csplit-debuginfo=..`, i.e. only stable ones on stable/beta and all of them on nightly/dev. Motivated by 1.65.0 regression causing builds with the following entry in `Cargo.toml` to fail on Windows: ```toml [profile.dev] split-debuginfo = "unpacked" ``` See rust-lang/cargo#11347 for details. This will lead to closing rust-lang#103976.
GuillaumeGomez
added a commit
to GuillaumeGomez/rust
that referenced
this issue
Nov 8, 2022
Add split-debuginfo print option This option prints all supported values for `-Csplit-debuginfo=..`, i.e. only stable ones on stable/beta and all of them on nightly/dev. Motivated by 1.65.0 regression causing builds with the following entry in `Cargo.toml` to fail on Windows: ```toml [profile.dev] split-debuginfo = "unpacked" ``` See rust-lang/cargo#11347 for details. This will lead to closing rust-lang#103976.
GuillaumeGomez
added a commit
to GuillaumeGomez/rust
that referenced
this issue
Nov 8, 2022
Add split-debuginfo print option This option prints all supported values for `-Csplit-debuginfo=..`, i.e. only stable ones on stable/beta and all of them on nightly/dev. Motivated by 1.65.0 regression causing builds with the following entry in `Cargo.toml` to fail on Windows: ```toml [profile.dev] split-debuginfo = "unpacked" ``` See rust-lang/cargo#11347 for details. This will lead to closing rust-lang#103976.
Manishearth
added a commit
to Manishearth/rust
that referenced
this issue
Nov 8, 2022
Add split-debuginfo print option This option prints all supported values for `-Csplit-debuginfo=..`, i.e. only stable ones on stable/beta and all of them on nightly/dev. Motivated by 1.65.0 regression causing builds with the following entry in `Cargo.toml` to fail on Windows: ```toml [profile.dev] split-debuginfo = "unpacked" ``` See rust-lang/cargo#11347 for details. This will lead to closing rust-lang#103976.
GuillaumeGomez
added a commit
to GuillaumeGomez/rust
that referenced
this issue
Nov 8, 2022
Add split-debuginfo print option This option prints all supported values for `-Csplit-debuginfo=..`, i.e. only stable ones on stable/beta and all of them on nightly/dev. Motivated by 1.65.0 regression causing builds with the following entry in `Cargo.toml` to fail on Windows: ```toml [profile.dev] split-debuginfo = "unpacked" ``` See rust-lang/cargo#11347 for details. This will lead to closing rust-lang#103976.
apiraino
removed
the
I-prioritize
Issue: Indicates that prioritization has been requested for this issue.
label
Nov 9, 2022
dubrowgn
added a commit
to dubrowgn/shooter
that referenced
this issue
Feb 2, 2023
Windows does not support split-debuginfo, and as of rust 1.65, results in build failure. Simple remove the directive, since it was an experiment anyway. See: rust-lang/rust#103976
@rustbot label -regression-untriaged +regression-from-stable-to-stable |
rustbot
added
regression-from-stable-to-stable
Performance or correctness regression from one stable version to another.
I-prioritize
Issue: Indicates that prioritization has been requested for this issue.
and removed
regression-untriaged
Untriaged performance or correctness regression.
labels
Jun 10, 2023
@Jules-Bertholet I think #104104 was meant to close this. But this issue still reproduces, right? |
I wouldn't know, I just updated the label based on the issue description. |
I'm going to close as I believe this is fixed in 1.68 via rust-lang/cargo#11347. Feel free to comment if that doesn't seem to be the case. |
apiraino
removed
the
I-prioritize
Issue: Indicates that prioritization has been requested for this issue.
label
Jun 15, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
C-bug
Category: This is a bug.
regression-from-stable-to-stable
Performance or correctness regression from one stable version to another.
Code
I tried this code:
I expected to see this happen: The compilation on windows succeds but does not actually use the feature.
Instead, this happened: The compilation on windows lets me know this feature is unavailable.
Version it worked on
It most recently worked on: Rust 1.64
Version with regression
rustc --version --verbose
:This is the
Cargo.toml
in question: https://github.com/probe-rs/probe-rs/blob/master/Cargo.toml#L21.This is the CI pipeline that started to fail with th 1.65 release: https://github.com/probe-rs/probe-rs/actions/runs/3390410063/jobs/5634519715
I am not sure if this would be a cargo or rustc issue. Pardon my ignorance.
Best,
Noah
The text was updated successfully, but these errors were encountered: