Skip to content
This repository was archived by the owner on Nov 24, 2023. It is now read-only.

Conversation

matthiaskrgr
Copy link
Member

When RUSTFLAGS was set, we would previously use "§{RUSTFLAGS}-W rust-2018-compatibility" which can cause
errorous invocations like "cargo fix .... -C target-cpu=native-W rust-2018-compatibility ...." if --prepare-for 2018 is used.
We need an extra space to separate RUSTFLAGS and "-W rust-2018-compatibility" because we want
"-C target-cpu=native -W rust-2018-compatibility".

When RUSTFLAGS was set, we would previously use "§{RUSTFLAGS}-W rust-2018-compatibility" which can cause
errorous invocations like "cargo fix .... -C target-cpu=native-W rust-2018-compatibility ...." if --prepare-for 2018 is used.
We need an extra space to separate RUSTFLAGS and "-W rust-2018-compatibility" because we want
"-C target-cpu=native -W rust-2018-compatibility".
@alexcrichton
Copy link
Member

Thanks! Can you add a test for this as well?

@killercup killercup merged commit e3608da into rust-lang:master Jun 7, 2018
killercup added a commit that referenced this pull request Jun 7, 2018
cli: fix injection of --prepare-for flags
@killercup
Copy link
Contributor

Added a test and merged

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants