Priming warning: "not a dynamic executable" with cross build
Metadata
Current evaluation
Cross-build priming emits misleading ELF/library-linter warnings; the maintainer identified disabling library checks as the needed fix, while current docs provide only a lint-disable workaround.
Suggested action: keep open
Reason: Maintainer @sergiusens explicitly stated that library checking must be disabled for cross-builds. The current cross-compilation documentation reproduces the warning, explains that target dependencies cannot be resolved by the library linter, and prescribes a lint override, but no resolving commit or PR was found.
Evaluated by: mr-cal-bot
Impact:
38
Quick Win:
11
Complexity:
60
Confidence:
92
Actionability:
72
Issue body
The customer reported as follows:
The attached snapcraft.yaml properly pulls, builds and stages .deb packages searched out from https://pkgs.org/, but during priming the following warnings appear:
(visible during the build of other snaps, too, altough some libraries are directly placed in a file_tree folder to be archived as .tar.
Is this a known behavior?
Is there an arm64-specific script needed to call the system linker/loader? (like in the example below?)
https://forum.snapcraft.io/t/how-to-fix-library-dependency-checking-for-cross-builds/9660
https://pastebin.com/LDgZaE7K
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| stealth/space-bunny-alpha |
Impact:
38
Quick Win:
11
Complexity:
60
Confidence:
92
Actionability:
72
|
keep open | Cross-build priming emits misleading ELF/library-linter warnings; the maintainer identified disabling library checks as the needed fix, while current docs provide only a lint-disable workaround. | |
| stealth/space-bunny-alpha |
Impact:
38
Quick Win:
12
Complexity:
55
Confidence:
92
Actionability:
70
|
keep open | Cross-build priming emits false library warnings because dependency checking uses host architecture details; maintainers acknowledged x-builds should skip this check, while current docs offer only a lint override. | |
| qwen/qwen3.6-35b-a3b |
Impact:
15
Quick Win:
11
Complexity:
10
Confidence:
90
Actionability:
80
|
close not a bug | Cross-build priming warning about 'not a dynamic executable' — documented as expected behavior with a lint: section workaround | |
| qwen/qwen3.8-27b |
Impact:
25
Quick Win:
18
Staleness:
90
Complexity:
30
Confidence:
70
Support Request:
75
|
close not a bug | Cross-build priming emits 'not a dynamic executable' warnings; reporter asks if known and whether an arm64 linker/loader script is needed. No maintainer response, no labels, inactive ~5.6 years. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
30
Confidence:
80
Support Request:
85
|
needs triage | Warning "not a dynamic executable" during snapcraft priming for cross builds. Unlabeled, zero comments, inactive for over 5 years, awaiting maintainer triage. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
40
Confidence:
85
Support Request:
75
|
close stale | User reports a not a dynamic executable warning during snapcraft priming for cross-compiled snaps. No maintainer response, no labels, and inactive for over 5 years. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
95
Complexity:
40
Confidence:
60
Support Request:
75
|
needs triage | Cross-build warning "not a dynamic executable" during snapcraft priming. No reproduction steps, no maintainer response, and inactive for over five years. |
Update history
| Date | Change |
|---|---|
| created |
Related issues
No related issues found above the similarity threshold.