Active archive?

[summers]

Hi is any archive of the ARMv5 active?

On my NAS (kirkwood nsa-325) I'd like to update the kernel - to get the latest btrfs updates. Knew this would need respinning the package - not a problem. Problem is I never installed fakeroot on the NAS, and I need that. Easiest would be to install that from an archive, then at least i can respin arm v5 packages when needed ...

Anyway can't find a archive active for the old 2021 arch arm linux ...

[graysky]

Only active ALAA I know of it the one I am running for aarch64

https:// www. reddit.com/r/arch/comments/1rr323d/archlinux_arm_archive_alaa_for_aarch64/

[summers]

No love with the old armv5 files.

Am slowly going through the updates needed. Think I'm going to need updated glibc - which will be a bit hairy ...

Automake and autoconf were quite easy ...

[summers]

Managed to get an old (2021/2) fakeroot it build and install! I wasn't able to get the latest fakeroot to install - that depends on time64. Now on the glibc on my machine this doesn't seem compatible with fakeroot time64. A modern glibc depends on a modern gcc. And so on.

Anyway a fakeroot from 2021/2 built -and I installed by hand. So at least now seem to be able to run makepkg. I'll probably slowly add the needed updates - this is slow. I've gcc compiling at the moment (in a detached screen) my guess is this will take days/weeks ...

[graysky]

Time to update hardware

[summers]

I keep hardware going as long as possible - the desktop (E350) machine I got in 2011I only retired in 2024 or so.

The NAS is still one of my two backup solutions - its quiet can live under the stairs and has something like 5TB of btrfs compressed file space. Its not fast - but it doesn't need to be.

My Sharp PC-1403 I was still in use a few years ago - sine waves on the screen in machine code ...

The PC I built in late 1990's died in 2011 IIRC - it wouldn't power up and I never worked out why.

[summers]

Sigh this approaching is circling downward - just hit a known gcc bug!

[url]https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96394[/url]

In compiling python (that I need in the dependancy chain). Kinda glad I have gcc compiling in the background - I won't be surprised if it take a week of CPU time to compile ....

[summers]

Yes gcc took over a week to compile. binuitls was only a few hours. This means I now have a modern tool chain (in /usr/local - e.g. keeping it out of the main OS). This means I can start the build of glibc package (after disabling all patches).

Reason behind this, when I've got a modern set of headers files for the armv5, I can install on the desktop - and compile a cross compiler against them. Then hopefully can build the packages on the desktop.

I'll probably post the packages on my website - so if anyone else wants to update a armv5 device, at least the packages are available. It kind feels a bit silly to fork a minor line from arch arm linux, when arch arm linux is already very quiet, and not very active. Anyway keeps me busy ...

[graysky]

> Yes gcc took over a week to compile.

Yeah wow, it's like running some of the dense LLMs on my puny 5060 Ti.

[summers]

NVIDIA GeForce RTX 5060 is vastly more powerful than my desk top Intel Alder Lake-P GT1.

LLM aka AI I'm never sure I'm keen on - its one of the motivations behind huge data centres, and I'm not sure thats a great reason to generate so much heat and CO2 ...