Is it time to bring Arch Linux ARM into the fold of Arch Linux? The GNU toolchain of ALARM is now very behind, and the developers are dead silent about why. There little to no response on pull requests on the github page, and while it seems like there is activity on their PKGBUILDs repo, it almost seems to me that it is some kind of automatic jobs being run. Their forum is broken and has been broken for quite some time as well. -- chs
I would love to see this happen since there's a rise of aarch64 laptops. On Friday, December 8, 2023 10:24:42 AM UTC Christer Solskogen wrote:
Is it time to bring Arch Linux ARM into the fold of Arch Linux? The GNU toolchain of ALARM is now very behind, and the developers are dead silent about why. There little to no response on pull requests on the github page, and while it seems like there is activity on their PKGBUILDs repo, it almost seems to me that it is some kind of automatic jobs being run. Their forum is broken and has been broken for quite some time as well.
Hi,
I would love to see this happen since there's a rise of aarch64 laptops.
Another data point... The Pi 4 was used by the Raspberry Pi Foundation as their desktop machine and the Pi 5 is significantly more powerful still. An official NVMe extension board will join the others already available. The Foundation have made public noises about the Pi 5 becoming a useful server. -- Cheers, Ralph.
I would love to see this happen. I'm a user of both archlinux and archlinux arm, I have a few packages on AUR and I sometimes post issues on archlinux gitlab and got quick replies. I am quite disheartened seeing the state of archlinux arm. Their forum registration has been broken for months, attempts have been made to fix the forum with no reply. I am shocked to see that `extras/chromium` is broken for years in arch linux arm! There are many many PRs (and consolidated PR) to fix this issue, one of the maintainer sees the PR and tagged the other maintainers to no avail. I was eventually led to other user's maintained build, presumably out of frustration. I'd love to help, I'd post in their forum had it not been broken. I think there's a lot of archlinux arm users who would love for the project to be merged under arch linux, especially with arm servers and desktops becoming more relevant. We would like to hear more from arch linux leaderships. Evans some links: [forum reg down](https://archlinuxarm.org/forum/viewtopic.php?f=8&t=17386) [chromium PR](https://github.com/archlinuxarm/PKGBUILDs/pull/2183)
On 4/14/26 10:19 AM, evansjahja13@gmail.com wrote:
I would love to see this happen.
I'm a user of both archlinux and archlinux arm, I have a few packages on AUR and I sometimes post issues on archlinux gitlab and got quick replies.
I am quite disheartened seeing the state of archlinux arm. Their forum registration has been broken for months, attempts have been made to fix the forum with no reply.
I am shocked to see that `extras/chromium` is broken for years in arch linux arm! There are many many PRs (and consolidated PR) to fix this issue, one of the maintainer sees the PR and tagged the other maintainers to no avail. I was eventually led to other user's maintained build, presumably out of frustration.
I'd love to help, I'd post in their forum had it not been broken. I think there's a lot of archlinux arm users who would love for the project to be merged under arch linux, especially with arm servers and desktops becoming more relevant.
We would like to hear more from arch linux leaderships.
Evans
some links:
[forum reg down](https://archlinuxarm.org/forum/viewtopic.php?f=8&t=17386)
[chromium PR](https://github.com/archlinuxarm/PKGBUILDs/pull/2183)
I feel your pain. I got tired of the issues you describe as well. I am working on my own packages and I have everything working on Raspberrypi 4 and 5. CLI and lxqt desktop working, I am type this on a desktop system from my efforts. I wrote some scripts that process the "base" package and the build them. I may my PKGBUILD's available on codeberg but I am not at that point yet. I have a few packages about 40 out of 2000 that are not building and I am currently working on those. I too would welcome archlinux to modify their package to build on aarch64. There isn't many changes required. -- Hindi madali ang maging ako
On Tuesday, April 14th, 2026 at 10:09 AM, Pocket <pocket@columbus.rr.com> wrote:
On 4/14/26 10:19 AM, evansjahja13@gmail.com wrote:
I would love to see this happen.
I'm a user of both archlinux and archlinux arm, I have a few packages on AUR and I sometimes post issues on archlinux gitlab and got quick replies.
I am quite disheartened seeing the state of archlinux arm. Their forum registration has been broken for months, attempts have been made to fix the forum with no reply.
I am shocked to see that `extras/chromium` is broken for years in arch linux arm! There are many many PRs (and consolidated PR) to fix this issue, one of the maintainer sees the PR and tagged the other maintainers to no avail. I was eventually led to other user's maintained build, presumably out of frustration.
I'd love to help, I'd post in their forum had it not been broken. I think there's a lot of archlinux arm users who would love for the project to be merged under arch linux, especially with arm servers and desktops becoming more relevant.
We would like to hear more from arch linux leaderships.
Evans
some links:
[forum reg down](https://archlinuxarm.org/forum/viewtopic.php?f=8&t=17386)
[chromium PR](https://github.com/archlinuxarm/PKGBUILDs/pull/2183)
I feel your pain. I got tired of the issues you describe as well.
I am working on my own packages and I have everything working on Raspberrypi 4 and 5. CLI and lxqt desktop working, I am type this on a desktop system from my efforts.
I wrote some scripts that process the "base" package and the build them.
I may my PKGBUILD's available on codeberg but I am not at that point yet.
I have a few packages about 40 out of 2000 that are not building and I am currently working on those.
I too would welcome archlinux to modify their package to build on aarch64. There isn't many changes required.
-- Hindi madali ang maging ako
Yeah, unfortunately, I think you're going to get a recommendation to continue to seek help from Archlinux ARM. There are several places in the main Arch Linux documentation where they pretty clearly state that mainline Arch can't be and isn't responsible for the various forks for other architectures. Also, I would interpret this not as a lack of sympathy for your plight, but rather simply that support for other architectures like ARM isn't part of the mainline Arch project and Arch simply doesn't have the personnel or expertise to help you. [Wiki on supported archs] https://wiki.archlinux.org/title/Frequently_asked_questions#What_architectur... [terms of service] https://wiki.archlinux.org/title/Code_of_conduct#arch-linux-distribution-sup... Mike
On 4/14/26 11:28 AM, Michael Swanson wrote:
On Tuesday, April 14th, 2026 at 10:09 AM, Pocket <pocket@columbus.rr.com> wrote:
On 4/14/26 10:19 AM, evansjahja13@gmail.com wrote:
I would love to see this happen.
I'm a user of both archlinux and archlinux arm, I have a few packages on AUR and I sometimes post issues on archlinux gitlab and got quick replies.
I am quite disheartened seeing the state of archlinux arm. Their forum registration has been broken for months, attempts have been made to fix the forum with no reply.
I am shocked to see that `extras/chromium` is broken for years in arch linux arm! There are many many PRs (and consolidated PR) to fix this issue, one of the maintainer sees the PR and tagged the other maintainers to no avail. I was eventually led to other user's maintained build, presumably out of frustration.
I'd love to help, I'd post in their forum had it not been broken. I think there's a lot of archlinux arm users who would love for the project to be merged under arch linux, especially with arm servers and desktops becoming more relevant.
We would like to hear more from arch linux leaderships.
Evans
some links:
[forum reg down](https://archlinuxarm.org/forum/viewtopic.php?f=8&t=17386)
[chromium PR](https://github.com/archlinuxarm/PKGBUILDs/pull/2183)
I feel your pain. I got tired of the issues you describe as well.
I am working on my own packages and I have everything working on Raspberrypi 4 and 5. CLI and lxqt desktop working, I am type this on a desktop system from my efforts.
I wrote some scripts that process the "base" package and the build them.
I may my PKGBUILD's available on codeberg but I am not at that point yet.
I have a few packages about 40 out of 2000 that are not building and I am currently working on those.
I too would welcome archlinux to modify their package to build on aarch64. There isn't many changes required.
-- Hindi madali ang maging ako
Yeah, unfortunately, I think you're going to get a recommendation to continue to seek help from Archlinux ARM. There are several places in the main Arch Linux documentation where they pretty clearly state that mainline Arch can't be and isn't responsible for the various forks for other architectures. Also, I would interpret this not as a lack of sympathy for your plight, but rather simply that support for other architectures like ARM isn't part of the mainline Arch project and Arch simply doesn't have the personnel or expertise to help you.
[Wiki on supported archs] https://wiki.archlinux.org/title/Frequently_asked_questions#What_architectur...
[terms of service] https://wiki.archlinux.org/title/Code_of_conduct#arch-linux-distribution-sup...
Mike
There are several places in the main Arch Linux documentation where they pretty clearly state that mainline Arch I have seen that. ARM is becoming an architecture of the future. Look at all the ARM SBC's on the market. I look at x86_64 as a dying architecture as ipads/phones are taking over. I use a Raspberry pi as my daily desktop and I haven't had the need to turn on my Miniforum x86_64 system. -- Hindi madali ang maging ako
This is actually one of my main complaints about Arch: the refusal—so far—to support non-x86 architectures. I care more about RISC-V than ARM, but the latter is nonetheless very important and already has a significant installation base. Besides the support in the main package repos (which is far beyond 98% even on RISC-V), tooling like fex, Wine ARM etc. make compatibility with non-ARM software better than ever before. All to say that I am strongly in favor of ALARM going upstream. The main obstacle I see is with CI, as well as tooling for AUR packagers to test their packages on non-native platforms. (It’s possible with a combination of arch-chroot and qemu userspace emulation, as per wiki documentation, but I haven’t yet found a good cross compilation setup beyond Rust.) Regards, kleines Filmröllchen PS: Not written by an LLM, I just use em dashes :)
As previously mentioned, there is the ports RFC [1]. I'd argue that the only thing missing to get the ball really rolling is a bit of organization (and maybe breaking things down so users of all experience levels can help). I often find myself (like many others) going back to the ALARM repos mainly because they sort-of work; but contributing to those has been a pain and more often than not things break and everyone's on its own (mainly because there's no "central place" where to share things). I know there's been lots of efforts around this [2] but even then it feels like we are all waiting on the infra/tooling to magically appear and work for ports and the reality is that "talk is cheap, send patches". Some "talk" will be necessary as there's a lot of things that should be integrated into arch's tooling, but there's the need to get some momentum going. I think that the rest will come by itself; we're at a point where even building everything on an emulated VM would be kind-of feasible because there is the computing power. I'm going on a tangent here, of course there are better solutions, but what I'm trying to say is: what we need is involvement, interest, and people willing to organize and put in the work to move the project forward :) I'll open an issue there [2] mentioning this thread to see what the people actually working on the project think, and to ask how we can help! Fermín Olaiz. --- [1] https://rfc.archlinux.page/0032-arch-linux-ports/ [2] https://gitlab.archlinux.org/archlinux/ports/aarch64/project-management/
On 4/14/26 1:09 PM, Fermín Olaiz wrote:
As previously mentioned, there is the ports RFC [1]. I'd argue that the only thing missing to get the ball really rolling is a bit of organization (and maybe breaking things down so users of all experience levels can help).
I often find myself (like many others) going back to the ALARM repos mainly because they sort-of work; but contributing to those has been a pain and more often than not things break and everyone's on its own (mainly because there's no "central place" where to share things).
Which is why I bit the bullet and I am making my own "distro"
I know there's been lots of efforts around this [2] but even then it feels like we are all waiting on the infra/tooling to magically appear and work for ports and the reality is that "talk is cheap, send patches".
Where does one send patches?
Some "talk" will be necessary as there's a lot of things that should be integrated into arch's tooling, but there's the need to get some momentum going.
I concur
I think that the rest will come by itself; we're at a point where even building everything on an emulated VM would be kind-of feasible because there is the computing power. I'm going on a tangent here, of course there are better solutions, but what I'm trying to say is: what we need is involvement, interest, and people willing to organize and put in the work to move the project forward :)
I'll open an issue there [2] mentioning this thread to see what the people actually working on the project think, and to ask how we can help!
Fermín Olaiz.
---
[1] https://rfc.archlinux.page/0032-arch-linux-ports/
[2] https://gitlab.archlinux.org/archlinux/ports/aarch64/project-management/
-- Hindi madali ang maging ako
On 26/04/14 01:15PM, Pocket wrote:
On 4/14/26 1:09 PM, Fermín Olaiz wrote:
I know there's been lots of efforts around this [2] but even then it feels like we are all waiting on the infra/tooling to magically appear and work for ports and the reality is that "talk is cheap, send patches".
Where does one send patches?
Some "talk" will be necessary as there's a lot of things that should be integrated into arch's tooling, but there's the need to get some momentum going.
I concur
Most of the coordination around these efforts is happening on IRC/Matrix, so if you're interested please join #archlinux-ports.
On 4/14/26 1:38 PM, Christian Heusel wrote:
On 26/04/14 01:15PM, Pocket wrote:
On 4/14/26 1:09 PM, Fermín Olaiz wrote:
I know there's been lots of efforts around this [2] but even then it feels like we are all waiting on the infra/tooling to magically appear and work for ports and the reality is that "talk is cheap, send patches".
Where does one send patches?
Some "talk" will be necessary as there's a lot of things that should be integrated into arch's tooling, but there's the need to get some momentum going.
I concur Most of the coordination around these efforts is happening on IRC/Matrix, so if you're interested please join #archlinux-ports.
I will need to learn how to do that -- Hindi madali ang maging ako
On Tue, Apr 14, 2026 at 7:39 PM Christian Heusel <christian@heusel.eu> wrote:
Most of the coordination around these efforts is happening on IRC/Matrix, so if you're interested please join #archlinux-ports.
Not only that, but we have a working PROTOTYPE. And by that I mean it is not official WHAT-SO-EVER. Tarballs are here: https://arch-linux-repo.drzee.net/arch/tarballs/os/aarch64/ Package repos are: https://arch-linux-repo.drzee.net/arch/core/os/aarch64/, https://arch-linux-repo.drzee.net/arch/extra/os/aarch64/ and https://arch-linux-repo.drzee.net/arch/forge/os/aarch64/. The forge repo is for aarch64 specific packages . We're pretty much up to date with upstream x86_64. We haven't packaged everything (yet), but we are already far beyond ALARM. And yes, our chromium packages is not broken. That said, we need all the help we can get. Testing is the biggest thing. That and MRs for kernel config (we only support ARMv8.2-A and higher) for SBCs.
On 4/14/26 2:25 PM, Christer Solskogen wrote:
On Tue, Apr 14, 2026 at 7:39 PM Christian Heusel <christian@heusel.eu> wrote:
Most of the coordination around these efforts is happening on IRC/Matrix, so if you're interested please join #archlinux-ports. Not only that, but we have a working PROTOTYPE. And by that I mean it is not official WHAT-SO-EVER.
Tarballs are here: https://arch-linux-repo.drzee.net/arch/tarballs/os/aarch64/ Package repos are: https://arch-linux-repo.drzee.net/arch/core/os/aarch64/, https://arch-linux-repo.drzee.net/arch/extra/os/aarch64/ and https://arch-linux-repo.drzee.net/arch/forge/os/aarch64/.
The forge repo is for aarch64 specific packages .
We're pretty much up to date with upstream x86_64. We haven't packaged everything (yet), but we are already far beyond ALARM. And yes, our chromium packages is not broken.
That said, we need all the help we can get. Testing is the biggest thing. That and MRs for kernel config (we only support ARMv8.2-A and higher) for SBCs.
Do you have the PKGBUILD's available? I would like to have a look at the ones that you got to build but have failed to build for me. I have 19 so far that have failed to build and I haven't got to figuring them out. They are mostly older ones that fail with the newer gcc, binutils and glibc I have 1764 and counting that have built for me. -- Hindi madali ang maging ako
Hi,
We would like to hear more from arch linux leaderships. ... I too would welcome archlinux to modify their package to build on aarch64. There isn't many changes required.
A reminder in case some on the list are not aware... Arch Linux has accepted the possibility of supporting ports other than x86_64. Here's a jumping-off point: https://wiki.archlinux.org/title/Getting_involved#Help_porting_Arch_Linux_to... -- Cheers, Ralph.
participants (10)
-
Christer Solskogen
-
Christian Heusel
-
Danct12
-
evansjahja13＠gmail.com
-
Fermín Olaiz
-
kleines Filmröllchen
-
Michael Swanson
-
Pocket
-
Pocket
-
Ralph Corderoy