From 17e0f6930c7b9c301bfe76522ca587dd78a06e13 Mon Sep 17 00:00:00 2001 From: Mark Schaller Date: Fri, 16 Oct 2026 02:11:26 -0400 Subject: [PATCH] Say what to do when the toolchain refuses to disable linker param files SKILL.md says to always call aquery with --features=-linker_param_file. The toolchain that rules_cc 0.2.22 autodetects on Linux implies that feature unconditionally, so analysis fails. In any2bazel-lab's migration runs, 8 of 10 agents hit the error and retried without the flag, one to three calls each, and none of the aquery outputs then held a param file reference (four runs checked). The text now names the error, says to drop the flag, and gives the check that keeps the instruction's purpose: no @....params entry in any action's arguments. Written after the runs, so no run has used it yet. Lab-Proposal: P29 Co-Authored-By: Claude Opus 5.5 --- SKILL.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/SKILL.md b/SKILL.md index effe05d..6a1a30d 100644 --- a/SKILL.md +++ b/SKILL.md @@ -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", //...)' \