← Back to issue list

cli: disable --target-arch support on core20

View original Github issue

Metadata

Project
snapcraft
Number
#3151
Type
pull request
State
merged
Author
cjp256
Labels
Created
Updated
Closed

Current evaluation

Merged changes disable the --target-arch CLI flag for core20 bases due to cross-compilation limitations. The flag is temporarily removed while future development expands --build-on support for multi-architecture targeting.

Suggested action:

No scores available.

Issue body

Rather than cross-compiling, which has numerous limitations, this commit disables --target-arch. We need to work on expanding support for --build-on to create an environment to target the correct architecture. Signed-off-by: Chris Patterson <chris.patterson@canonical.com> - [ ] Have you followed the [guidelines for contributing](https://github.com/snapcore/snapcraft/blob/master/CONTRIBUTING.md)? - [ ] Have you signed the [CLA](http://www.ubuntu.com/legal/contributors/)? - [ ] Have you successfully run `./runtests.sh static`? - [ ] Have you successfully run `./runtests.sh tests/unit`? -----

Evaluation history

Date Model Scores Action Summary
qwen/qwen3.6-35b-a3b Merged changes disable the --target-arch CLI flag for core20 bases due to cross-compilation limitations. The flag is temporarily removed while future development expands --build-on support for multi-architecture targeting.
qwen3.6-35b-a3b-mtp-q6 Merged into master. Disables --target-arch support on core20 to bypass cross-compilation limitations. Future work will expand --build-on to handle architecture targeting.
qwen3.6-35b-a3b-mtp-q6 Merged into master. Disables --target-arch CLI support on core20 to avoid cross-compilation limitations, deferring architecture targeting to future --build-on improvements.

Update history

No update history recorded yet.

Related issues

Issue Project State Summary Similarity
#3410 project: enable experimental target-arch support for core20 snapcraft merged Merged PR enabling experimental target-arch support for core20 with an explicit warning. Approved by a maintainer, the change adds the flag to two files without affecting code coverage, and was integrated despite a noted test failure.
75%