snapcraft does not properly detect the architecture when kernel is 64 bits but userspace is 32
Bug #1641123 reported by
Alfonso Sanchez-Beato
This bug affects 3 people
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Snapcraft |
Fix Released
|
High
|
Marco Trevisan (Treviño) | ||
Bug Description
Building a snap in a chroot in a phone that has 64 bits kernel but 32 bits user space produces a snap that is supposed to be 64 bits, with name *_arm64.snap and snap.yaml containing:
<<
architectures:
- arm64
>>
However, the compiled files are 32 bits, because:
$ gcc -v |& grep Target
Target: arm-linux-gnueabihf
Revision history for this message
| Sergio Schvezov (sergiusens) wrote | #1 |
| Changed in snapcraft: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| assignee: | nobody → Sergio Schvezov (sergiusens) |
| milestone: | none → 2.23 |
| Changed in snapcraft: | |
| milestone: | 2.23 → none |
| Changed in snapcraft: | |
| assignee: | Sergio Schvezov (sergiusens) → Marco Trevisan (Treviño) (3v1n0) |
| status: | Triaged → In Progress |
| milestone: | none → 2.26 |
| Changed in snapcraft: | |
| status: | In Progress → Fix Committed |
Revision history for this message
| Sergio Schvezov (sergiusens) wrote | #2 |
| Changed in snapcraft: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
Taking infinity's input...
So, if a compiler is always there, and you trust it's sane, gcc -dumpmachine is pretty much what you're after for guessing "native" compilation.