Fresh arch install on RPI3b: glibc not found when running pacman

ARM General system
1

[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?

[1] https://archlinuxarm.org/platforms/armv8/broadcom/raspberry-pi-3
[2] /usr/lib/libc.so.6: version `GLIBC_2.34' not found (required by /usr/lib/libcurl.so.4) - #5 by igoryan

2

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.

Pudge

3

Thanks, @Pudge, will try as you suggest and report back.

Edit: to answer your question: I used the 32 bit.

Will not be today, I’m afraid.

1 Like
4

No worries. Whenever you get time.

This is from the Florida US mirror which I use.
http://fl.us.mirror.archlinuxarm.org/os/

ArchLinuxARM-rpi-aarch64-latest.tar.gz             01-Mar-2023 01:59           562123464
ArchLinuxARM-rpi-aarch64-latest.tar.gz.md5         01-Mar-2023 01:59                  73
ArchLinuxARM-rpi-aarch64-latest.tar.gz.sig         01-Mar-2023 01:59                 566
ArchLinuxARM-rpi-armv7-latest.tar.gz               01-Mar-2023 02:57           445216553
ArchLinuxARM-rpi-armv7-latest.tar.gz.md5           01-Mar-2023 02:58                  71
ArchLinuxARM-rpi-armv7-latest.tar.gz.sig           01-Mar-2023 02:57                 566

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.

This is step 5 for the Archlinux ARM RPi 3b rootfs as per the wiki
wget http://os.archlinuxarm.org/os/ArchLinuxARM-rpi-aarch64-latest.tar.gz

This is step 5 for the Archlinux ARM RPi 4b rootfs as per the wiki
wget http://os.archlinuxarm.org/os/ArchLinuxARM-rpi-aarch64-latest.tar.gz

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.

Pudge

1 Like
5

Thank you so much.

Will report back later.

1 Like
6

So far I have tried:

Still the same glibc-error.

Will try with the enos-image next.

1 Like
7

I tried a couple of things:

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.

1 Like
8

Have not had time yet to try enos image. Sorry.
Will report as soon as I do.

9

@pudge I tried the enos image file, but my SD card is too small. I think I have a larger one somewhere. Will have to search.

Anyway: onwards and upwards.

1 Like
10

I ended up with following [1], using ArchLinuxARM-rpi-aarch64-latest.tar.gz.
And in stead of 200M I used 1G, to create enough space.

Immediately afterwards I ran:

pacman -Syyu

which worked.

The problem with pacman did and does not occur, even after rebooting - rerunning pacman now simply ends with “nothing to do”.

Now I have to figure out how I get sddm/plasma/kde installed.

I’ll mark this as solved.

Thanks @Pudge!

[1] https://archlinuxarm.org/platforms/armv8/broadcom/raspberry-pi-3

1 Like
11

You are very welcome.

Pudge

12

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.