[if this is not the right topic please move it to its proper place]
Using [1] I installed arch on an SD-card for an RPI3.
No apparent errors during install.
Booting works, I can log in with both default users ‘alarm’ and ‘root’.
I can run commands or apps like top, dir.
When I try to run pacman I get the message that glibc 2.38 can not be found.
I searched the arch forum but found only old or apparently none related topics.
Then I searched this forum, where I found [2]. So I tried some of the suggestions there. But whatever I try (like pacman -Sy glibc curl), pacman throws the glibc-error.
pacman-static is suggested as a possible solution (also suggested over at arch), but so far I have not found the arm version of pacman-static.
Am I missing something obvious?
Any pointers or suggestions which might help me to get this solved?
Would repeating the installation as per [1] possibly solve this?
When using [1] did you use armv7h or aarch64? The difference being armv7h is 32 bit and aarch64 is 64 bit. The RPi 3b will run on either 32 bit or 64 bit but the armv7h (32 bit) repositories are not as up to date as the 64 bit repositories. Plus 64 bit is a little faster.
Here is what Archlinux ARM has in the repos for glibc
aarch64 core glibc 2.39+r52+gf8e4623421-1 GNU C Library
armv7h core glibc 2.39+r52+gf8e4623421-1 GNU C Library
I do not have a RPi 3b so I can’t try or test anything.
To install 64 bit, in step 5 change the name of the rootfs file to the 64 bit roots listed at the bottom of the wiki page.
The rootfs files have not been updated since Mar-2023. This probably led to something needing the glibc as a dependency of 2.38 and the rootfs may have supplied < 2.38 version.
My recommendation is to use the aarch64 rootfs supplied by Archlinux ARM. Then on first boot, immediately do a sudo pacman -Syu and see if you get glibc-2.39 which the latest version of glibc on the mirrors.
If you have time, you could try the EnOS RPi 4b image.
They are using the same rootfs for both RPi 3b and RPi 4b.
So, if you have the time and desire, you could download the RPi 4b image from here https://github.com/endeavouros-arm/images/releases/tag/rpi-4b-image
burn it to a micro-SD card, plug it in and see what happens. Maybe it will work, maybe not.
sudo pacman -Syyu, to try and do a full update. I did not get the glibc error, but got the message that boot was not large enough. No update was possible.
Trying to repeat the same with a larger boot (1Gib) resulted in nothing - black screen at boot. No TTY or anything. Did not look into this any further.
And just to make sure I’d there’s not something else going on I downloaded an alpine Linux image to see if that would work. It did. Though installing plasma on it, did not result in a working plasma.
So, I’ll abandon alpine for now.
Next step: download the rpi4 Eos image and see what happens then.