Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Remove unused
-C link-arg=-fuse-ld=lld
(#15097)
That's a gcc flag. lld is a linker, not a C compiler, and doesn't accept a `use-ld` flag. `-C linker=rust-lld` (which is already present in the test) is enough. This fixes the following warning found in rust-lang/rust#119286: ``` ---- expected: tests\testsuite\freshness.rs:2822:27 ++++ actual: stderr 1 1 | [FRESH] foo v0.1.0 ([ROOT]/foo) 2 + [WARNING] linker stderr: rust-lld: ignoring unknown argument '-fuse-ld=lld'␍ 3 + | 4 + = [NOTE] `#[warn(linker_messages)]` on by default 5 + 6 + [WARNING] `foo` (lib) generated 1 warning 2 7 | [FINISHED] `dev` profile [unoptimized + debuginfo] target(s) in [ELAPSED]s ``` <!-- Thanks for submitting a pull request 🎉! Here are some tips for you: * If this is your first contribution, read "Cargo Contribution Guide" first: https://doc.crates.io/contrib/ * Run `cargo fmt --all` to format your code changes. * Small commits and pull requests are always preferable and easy to review. * If your idea is large and needs feedback from the community, read how: https://doc.crates.io/contrib/process/#working-on-large-features * Cargo takes care of compatibility. Read our design principles: https://doc.crates.io/contrib/design.html * When changing help text of cargo commands, follow the steps to generate docs: https://github.com/rust-lang/cargo/tree/master/src/doc#building-the-man-pages * If your PR is not finished, set it as "draft" PR or add "WIP" in its title. * It's ok to use the CI resources to test your PR, but please don't abuse them. ### What does this PR try to resolve? Explain the motivation behind this change. A clear overview along with an in-depth explanation are helpful. You can use `Fixes #<issue number>` to associate this PR to an existing issue. ### How should we test and review this PR? Demonstrate how you test this change and guide reviewers through your PR. With a smooth review process, a pull request usually gets reviewed quicker. If you don't know how to write and run your tests, please read the guide: https://doc.crates.io/contrib/tests ### Additional information Other information you want to mention in this PR, such as prior arts, future extensions, an unresolved problem, or a TODO list. -->
- Loading branch information