Skip to content

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

Open
anakanemison wants to merge 1 commit into
mschaller/u10-link-only-external-depsfrom
mschaller/u11-linker-param-file-refusal
Open

anakanemison wants to merge 1 commit into
mschaller/u10-link-only-external-depsfrom
mschaller/u11-linker-param-file-refusal

Conversation

@anakanemison

@anakanemison anakanemison commented Oct 20, 2026 •

Copy link
Copy Markdown
Contributor

SKILL.md says to call aquery with --features=-linker_param_file, but the toolchain rules_cc 0.2.22 autodetects on Linux implies that feature, so analysis fails. The text now names the error, says to drop the flag, and gives the check that keeps its purpose: no @….params entry in any action's arguments.

In any2bazel-lab, 8 of 10 agents hit the error and retried; none of the four outputs checked then held a param file reference. Written after those runs, so no run has used it yet.

Stacked on #45 (tracking issue: #35). pytest tests/: 186 passed (132 on main). Lab proposal: P29.

🤖 Generated with Claude Code

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 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant