build-package "on amd64 to armhf" seems to be not working
Metadata
Current evaluation
Resolved as user error. The correct syntax for architecture-specific build packages is package:arch (e.g., gcc-arm-linux-gnueabihf:amd64), not on amd64 to armhf.
Resolution: closed not a bug
Reason: Closed by @mr-cal because @ogra correctly identified that the syntax for architecture-specific build packages should be package:arch (e.g., gcc-arm-linux-gnueabihf:amd64) rather than the on amd64 to armhf format.
Evaluated by: mr-cal-bot
No scores available.
Issue body
It looks like build-package for cross-building does not fully work when using "build-on" and "run-on".
When I specify: " on amd64 to armhf" in snapcraft.yaml snapcraft does not try to install the build package in question.
Here is a slightly simplified example (full code in https://github.com/snapcore/pi-gadget):
```
name: pi
version: 18-0.1
summary: something
description: else
type: gadget
architectures:
- build-on: amd64
run-on: armhf
parts:
uboot-pi2:
plugin: nil
override-build: |
echo "do stuff"
build-packages:
- on amd64 to armhf:
- gcc-arm-linux-gnueabihf
```
using this snapcraft.yaml does not trigger an install of gcc-arm-linux-gnueabihf.
I need to trigger this via an explicit "snapcraft build --target-arch armhf" which I cannot do in launchpad (AFAIK).
Evaluation history
| Date | Model | Scores | Action | Summary |
|---|---|---|---|---|
| qwen/qwen3.6-35b-a3b | — | closed not a bug | Resolved as user error. The correct syntax for architecture-specific build packages is package:arch (e.g., gcc-arm-linux-gnueabihf:amd64), not on amd64 to armhf. | |
| stealth/space-bunny-alpha |
Impact:
20
Quick Win:
16
Complexity:
5
Confidence:
93
Actionability:
85
|
close not a bug | Advanced grammar is supported, but cross-build package selection needs a host-qualified package name; the reporter's armhf configuration does not trigger the compiler installation. | |
| stealth/space-bunny-alpha |
Impact:
32
Quick Win:
25
Complexity:
12
Confidence:
90
Actionability:
90
|
close not a bug | Cross-build grammar did not install the requested toolchain on Launchpad; the reported correction is to declare the amd64-hosted compiler as gcc-arm-linux-gnueabihf:amd64. | |
| qwen/qwen3.6-35b-a3b |
Impact:
30
Quick Win:
14
Complexity:
20
Confidence:
70
Actionability:
60
|
close resolved | Cross-build build-packages 'on amd64 to armhf' not installing packages. Issue is 8 years old; grammar support has evolved significantly. Likely resolved if target_arch is now auto-derived or syntax is fully supported. | |
| qwen/qwen3.8-27b |
Impact:
30
Quick Win:
14
Staleness:
95
Complexity:
55
Confidence:
70
Support Request:
10
|
close stale | Cross-building with build-on/run-on architecture grammar does not install the specified build-packages (e.g. gcc-arm-linux-gnueabihf) unless an explicit --target-arch is passed. Reported in 2018, no maintainer interaction, zero comments. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
98
Complexity:
35
Confidence:
92
Support Request:
5
|
close stale | Cross-building in Snapcraft fails to install specified build-packages when using build-on/run-on architecture directives. Unaddressed for over 7 years with no maintainer interaction. | |
| qwen/qwen3.6-35b-a3b |
Staleness:
95
Complexity:
45
Confidence:
90
Support Request:
15
|
close stale | Cross-compilation build-package syntax fails to install specified packages in snapcraft. Unlabelled, zero comments, inactive for over 7 years, likely outdated for current versions. | |
| qwen3.6-35b-a3b-mtp-q6 |
Staleness:
98
Complexity:
40
Confidence:
85
Support Request:
10
|
close stale | Cross-compilation build-package syntax fails to install specified packages in snapcraft.yaml. Issue is over 7 years old with no maintainer response or activity. |
Update history
| Date | Change |
|---|---|
| closed | |
| created |
Related issues
No related issues found above the similarity threshold.