Skip to content

Say what to do when the toolchain refuses to disable linker param files #46

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.

Sign up for GitHub

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

Open
anakanemison wants to merge 1 commit into from
Open

Say what to do when the toolchain refuses to disable linker param files #46

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 4 additions & 0 deletions SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -279,6 +279,10 @@ instead of being a warning nobody reads.
> `--features=-linker_param_file` to disable use of param files. Param files
> are never generated during `aquery` calls, so when they're in use they'll
> always point to files that are either stale, or do not exist at all.
> Some toolchains refuse this: analysis fails with "unconditionally implies
> feature 'linker_param_file'" (the toolchain rules_cc autodetects on Linux
> does). Then drop that flag, and check that no action's `arguments` in the
> output hold an `@….params` entry: if none does, nothing is hidden.

```bash
bazel aquery 'mnemonic("CppCompile|ObjcCompile|CppLink|CppArchive", //...)' \
Expand Down
Loading