#archlinux-ports | Logs for 2026-03-27
Back
[00:02:36] -!- maxjrh has joined #archlinux-ports
[00:42:05] -!- marmis has quit [Quit: Bye!]
[00:43:49] -!- marmis has joined #archlinux-ports
[02:15:57] -!- drathir_tor has quit [Remote host closed the connection]
[02:16:16] -!- drathir_tor has joined #archlinux-ports
[04:13:30] -!- hcmb has quit [Ping timeout: 245 seconds]
[04:13:46] -!- hcmb has joined #archlinux-ports
[04:49:36] -!- maxjrh has quit [Quit: maxjrh]
[04:49:43] -!- maxjrh has joined #archlinux-ports
[05:42:13] -!- maxjrh has quit [Quit: maxjrh]
[06:59:58] <solskogen|M> gromit: Did you do anything special to build freecad? I can't build it on either aarch64 nor x86_64.
[07:01:52] <solskogen|M> oh, I think I know. you built it against boost 1.90.0, which is in staging.
[11:30:29] -!- maxjrh has joined #archlinux-ports
[15:55:26] <yuvadm> bschnei: it's probably not the main blocker but would more cores help here?
[17:09:40] <bschnei> yuvadm: correct, it'd only help on the margin. ok so chromium takes 6 hours instead of 24 to build. less annoying? sure. not really an obstacle though. AWS has very beefy ARM VMs we already use. where we are at now though is that environment is supporting/maintaining the v8.2 packages. we've been fortunate that drzee has some credits as an AWS employee that have kept costs low for us. setting up that same environment to
[17:09:40] <bschnei> build/maintain v8 packages in parallel (even if only temporary) is likely to exceed his credits (if we aren't already doing so). so a bigger discussion would need to happen. if you are serious about wanting to tackle the v8 problem, I'd probably start by connecting directly with solskogen since he built and runs the current infrastucture and can speak to how much of his time it takes just to keep up. if still intereste
[17:09:40] <bschnei> d then we could then check in with drzee
[17:13:27] <bschnei> in the interim, I will try to naively build as many packages as I can for v8 (though I may not be able to support them on an on-going basis) but just to get a sense....are we talking...hundreds? thousands? we're not really sure....
[17:14:32] <solskogen|M> It's a bit of a hassle to do, since we didn't do things properly to begin with - some of the packages we have are newer than x86_64 - and they are quite important (a dependency to pacman)
[17:15:03] <solskogen|M> It's possible, but personally I don't see the need to support 12 year old CPUs.
[17:15:36] <solskogen|M> So it's not as easy as just to recompile the packages.
[17:18:47] -!- binarycraft has joined #archlinux-ports
[17:19:20] <binarycraft> https://build.opensuse.org has free arm build server but only support x86_64 arch, we could request it to support our unofficial arm port though
[17:19:22] <phrik> Title: Open Build Service API (at build.opensuse.org)
[17:21:08] <binarycraft> https://imgur.com
[17:22:21] <solskogen|M> Feel free to do that :-)
[19:33:49] <yuvadm> bschnei: i was asking just out of curiosity :) v8 is very low priority for me personally, and also in terms of the entire effort i'm not sure we should prioritize that right now either
[19:34:27] <bschnei> ya that's kinda of where it lands for everyone at the moment :)
[19:35:40] <bschnei> another reason is that the cloud infrastructure is all v8.2 and that is honestly where we do most of our work. my v8 router just sits there and routes. I don't interact with it much
[19:36:18] <bschnei> even the pi5 I bought to help package a kernel collects dust these days
[19:40:52] <yuvadm> same, v8 router runs openwrt and then i just forget about it
[19:48:49] -!- binarycraft has quit [Quit: WeeChat 4.8.2]