|Description||The ARM64 project is devoted to getting and keeping Gentoo in good shape on the ARM AArch64 architecture.|
|IRC channel||#gentoo-arm (webchat)|
Last elected: 2020-08-24
(and inherited member(s))
|Parent Project||ARM Development|
The ARM64 project works on getting the AArch64 architecture in 64-bit mode into a stable state (stable profiles, stable keywords coverage) and maintain its support long-term.
TODO: list our current hardware
- ARM64 is 64-bit.
- Some, but not all, ARM64 CPUs can run 32-bit ARM programs (e.g. chrooting into an armv7a stage3).
- ARM64 is primarily little-endian (we don't really talk about big-endian for arm -- nor does anybody else).
- ... but we do actually have an arm64 big-endian profile at least!
Users do not have to test themselves with FEATURES=test, although it's nice if they do. Please file a bug if a package works for you in stable and your system is stable. We want to mark it as such in Gentoo!
We want both stable
~arm64requests. File them! See Stable request.
If you are an ARM64 user and you use packages not keyworded yet, feel free to request such a keywording (see Knowledge_Base:Missing_keywords_and_keyword_requests#Fixing_it_for_everybody).
If possible, it'd be nice (but not required) if you can fully test request and covers all the dependencies - even those that you don't need yourself (from extra USE flags). To test for that, mark it locally and run repoman as such (dev-libs/foo-1.2-r3 is what we try to keyword as an example):
cd $(portageq get_repo_path / gentoo)
ekeyword ~arm64 foo-1.2-r3.ebuild
ebuild foo-1.2-r3.ebuild manifest
repoman -d full --include-arches arm64
If you notice any arm64 dependency issues, then you should test and keyword those as well. If this ends up with too much, or that isn't too applicable to arm64, then at least state the USE flags that didn't get tested due to extra dependencies, for the purpose of at least knowing to package.use.mask'ing them for now to avoid introducing new keyword issues. Once done, don't forget to clean up your local changes - if this was in a rsync tree, then that will happen automatically on next sync.
If you have a set of packages tested for keywording, we would prefer a list of packages tested together, not separate Bugzilla entries.
Feel free to add yourself with your IRC handle to our ARM hardware list here on the wiki. It contains both 32-bit and AArch64 hardware. It is always nice to know what gadgets are out there!