Smart doesn't detect 'armel' architecture correctly
Bug #351823 reported by
Sidnei da Silva
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Landscape Client |
Invalid
|
Undecided
|
Unassigned | ||
Smart Package Manager |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Apparently 'arm' is toast, long live to 'armel. Smart though assumes that anything that startswith('arm') should be 'arm'.
From the information on Debian's ArmEabiPort, seems like anything later than 'armv4te' should be 'armel':
"""
So Debian armel runs on a minimum CPU of ARMv4t and by default the Debian armel GCC generates code for armv4t (rather than the usual default ARM target of armv5t).
""" -- From: http://
Changed in smart: | |
milestone: | 1.4 → 1.4.1 |
Changed in smart: | |
status: | Confirmed → Fix Committed |
Changed in smart: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
FWIW, in smart/backends/ deb/base. py:getArchitect ure():
- sysconf. get("deb- arch") returns None ("arm") : return "arm"
- ... elif arch.startswith
- Should probably be 'armel' here by default, and 'arm' only for
'StrongARM' or earlier than 'ARMv4'