#archlinux-ports | Logs for 2026-01-23
Back
[04:38:27] -!- hcmb_ has joined #archlinux-ports
[04:38:27] hcmb is now known as Guest8551
[04:38:27] -!- Guest8551 has quit [Killed (tungsten.libera.chat (Nickname regained by services))]
[04:38:27] hcmb_ is now known as hcmb
[06:57:07] -!- SpieringsAE has joined #archlinux-ports
[07:24:21] <solskogen|M> <heftig> "arch decided on x86_64-pc-linux..." <- but that's probably rusts fault, isn't it? x86_64-pc-linux-gnu is what upstream config.guess comes up with IIRC.
[07:24:55] <heftig> Solskogen: there's no authority on triples
[07:25:10] <heftig> "upstream config.guess" is just gnu autoconf
[07:26:58] <heftig> the linux kernel sets clang's target to x86_64-linux-gnu
[07:28:26] <solskogen|M> what a mess...
[09:15:37] <integral|M> It seems that some packages should be blacklisted in the AArch64 port, such as `intel-ucode` and `amd-ucode`
[09:16:35] <solskogen|M> Because?
[09:17:27] <solskogen|M> I mean, I agree that it doesn't make much sense to install them.
[09:17:53] <solskogen|M> But since they are -any packages, they are just synced from x86_64.
[09:19:10] <solskogen|M> there are packages that either cannot be built on aarch64 and/or doesn't make any sense to have on aarc64 that we don't build like xf86-input-vmmouse
[11:59:43] -!- gehidore has quit [Ping timeout: 264 seconds]
[12:01:28] -!- gehidore has joined #archlinux-ports
[12:09:08] <linkmauve> Wouldn’t those be useful in emulation contexts?
[12:23:38] <solskogen|M> like what?
[12:25:28] <linkmauve> Running an AArch64 userland on amd64.
[12:39:45] <solskogen|M> good luck with that
[14:38:37] -!- SpieringsAE has quit [Quit: SpieringsAE]
[15:04:56] -!- drathir_tor has quit [Remote host closed the connection]
[15:05:16] -!- drathir_tor has joined #archlinux-ports
[16:14:26] -!- drathir_tor has quit [Remote host closed the connection]
[16:14:49] -!- drathir_tor has joined #archlinux-ports
[16:59:35] -!- marmis has quit [Read error: Connection reset by peer]
[16:59:37] -!- marmis has joined #archlinux-ports
[18:42:34] <yuvadm> is there any (even ad hoc) process for bootstrapping a new aarch64 port to a new board? I'd like to test the existing packages on odroid-c4 (which unfortunately never had proper ALARM support)
[18:43:32] <yuvadm> it runs Amlogic S905X3 fwiw
[19:17:45] <linkmauve> yuvadm, do you have a working u-boot and kernel for that board?
[19:18:09] <linkmauve> Or even better, is it supported in mainline in both of these projects?
[21:15:50] <yuvadm> linkmauve: u-boot has mainline support, kernel i believe i have a working config i can test
[21:17:24] <linkmauve> yuvadm, then you just have to install u-boot, extract the rootfs, then it should boot just fine. :)
[23:10:14] -!- titus_livius has joined #archlinux-ports