← Back to issue list

Priming warning: "not a dynamic executable" with cross build

View original Launchpad issue

Metadata

Project
snapcraft (launchpad)
Number
#1911375
Type
issue
State
open
Author
~woodrow-shen
Labels
—
Created
Updated
Closed
—

Current evaluation

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.

Suggested action: close not a bug

Reason: The reporter is asking whether the warning is known behavior and how to handle it (a usage/support question), and the current docs (docs/how-to/integrations/craft-a-cross-compiled-app.rst) explicitly document this exact 'not a dynamic executable' warning for cross-compiled apps and show how to suppress it via a lint section, so the behavior is expected and now documented. No maintainer ever triaged it and it has been inactive for over 5 years.

Impact: 25 Quick Win: 17.5 Staleness: 90 Complexity: 30 Confidence: 70 Support Request: 75

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
qwen/qwen3.8-27b
Impact: 25
Quick Win: 17.5
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.
qwen3.6-35b-a3b-mtp-q6
Staleness: 95
Complexity: 30
Confidence: 85
Support Request: 80
close stale Cross-building snaps triggers a "not a dynamic executable" priming warning. The reporter questions if this is expected and requests arm64 linker guidance. Open, zero comments, awaiting triage.

Update history

No update history recorded yet.

Related work

  • Related To: snapcraft#1838098 (confidence 40%)

    Related priming/ELF-handling issue (invalid ELF file during prime), closed without fix; tangential to this warning.

Related issues

No related issues found above the similarity threshold.