#archlinux-ports | Logs for 2026-01-14

Back
[00:52:38] -!- marmis has quit [Quit: Bye!]
[00:54:24] -!- marmis has joined #archlinux-ports
[04:48:47] -!- hcmb_ has joined #archlinux-ports
[04:48:47] hcmb is now known as Guest629
[04:48:47] -!- Guest629 has quit [Killed (platinum.libera.chat (Nickname regained by services))]
[04:48:47] hcmb_ is now known as hcmb
[06:17:45] -!- p71 has quit [Ping timeout: 252 seconds]
[07:12:40] -!- SpieringsAE has joined #archlinux-ports
[08:59:26] -!- linkmauve has joined #archlinux-ports
[08:59:56] -!- linkmauve has parted #archlinux-ports
[09:02:41] -!- linkmauve has joined #archlinux-ports
[09:03:19] <linkmauve> Hi, when I do `pacman-key --init` I end up with “/usr/bin/pacman-key: line 221: 65457 Illegal instruction (core dumped) "${GPG_PACMAN[@]}" --update-trustdb”
[09:03:39] <linkmauve> I just extracted the tarball on a Cortex-A55 board.
[09:04:05] <linkmauve> The host system is still ArchLinuxARM, I wanted to evaluate whether this port would run fine there.
[09:06:01] <linkmauve> The instruction it’s choking on is, according to gdb, this one:
[09:06:02] <linkmauve> │ >0xfffff7c9aea4 pmull2 v0.1q, v0.2d, v31.2d
[09:06:31] <Solskogen> That should work. You're running it in a chroot?
[09:06:42] <linkmauve> Yes I am.
[09:06:48] <linkmauve> No container whatsoever, just a basic chroot.
[09:07:14] <Solskogen> does other tools with? Like cp and ls?
[09:07:23] <Solskogen> *WORK* - not with
[09:07:27] <linkmauve> Both run yes.
[09:09:45] <Solskogen> but not this: gpg --version ?
[09:09:58] <linkmauve> # gpg --version
[09:09:58] <linkmauve> Illegal instruction (core dumped) gpg --version
[09:11:59] <linkmauve> https://linkmauve.fr
[09:13:04] <linkmauve> This happens in libgcrypt.so.20
[09:14:57] <Solskogen> give me a few secs, and I'll provide you with a package you can try
[09:17:11] <linkmauve> I absolutely don’t understand the succession of instructions this is failing on though:
[09:17:11] <linkmauve> 0xfffff7c9aea0 eor v31.16b, v31.16b, v31.16b
[09:17:12] <linkmauve> >0xfffff7c9aea4 pmull2 v0.1q, v0.2d, v31.2d
[09:17:12] <linkmauve> 0xfffff7c9aea8 aesimc v15.16b, v0.16b
[09:17:12] <linkmauve> 0xfffff7c9aeac sha1su1 v0.4s, v0.4s
[09:17:12] <linkmauve> 0xfffff7c9aeb0 sha256su1 v0.4s, v15.4s, v31.4s
[09:17:35] <linkmauve> Is that a test of support for the crypto extension?
[09:24:20] <Solskogen> I might have enabled a option that is not supported, and that is +rcpc. your board should support +crypto.
[09:26:39] <Solskogen> hm, no. that's not it. but the m1 doesn't seem to work with +crypto - which is strange.
[09:27:45] <linkmauve> Indeed, it doesn’t have this extension.
[09:28:38] <Solskogen> But https://www.hardkernel.com says it does
[09:28:40] <phrik> Title: ODROID-M1 with 8GByte RAM – ODROID (at www.hardkernel.com)
[09:30:27] <linkmauve> Uh, that’s weird! Could it be that my kernel or u-boot or TF-A don’t have something needed enabled?
[09:30:44] <linkmauve> I have build my own u-boot and TF-A.
[09:31:42] <Solskogen> I... I don't know.
[09:32:04] <linkmauve> I’ll try building everything anew, and report back.
[09:32:49] <Solskogen> how old is the dtb you used when building uboot?
[09:35:01] <linkmauve> It was from mainline circa December.
[09:37:37] <Solskogen> From what I've found: https://forum.odroid.com
[09:38:24] <Solskogen> it seems you're missing some of the flags others have (like aes and sha1)
[09:39:38] <Solskogen> but it's not clear to me if that is the m1 or m1s
[09:39:59] <linkmauve> It is the m1.
[09:43:35] <Solskogen> they're so alike, i don't think it matters. the question is why you're missing those flags, while others aren't.
[09:45:46] <Solskogen> I found this: https://linux-hardware.ru
[09:45:48] <phrik> Title: HW probe of Hardkernel ODROID-M1 #481e87aa23: cpuinfo (at linux-hardware.ru)
[09:46:00] <Solskogen> there is says that it has those extentions.
[10:05:07] <linkmauve> I just tested a newer u-boot, same report.
[10:05:18] <linkmauve> I’ll move that to #linux-rockchip, thanks for the help. :)
[10:15:44] <linkmauve> Solskogen, if I use ALARM’s uboot-odroid-m1 package, it does work!
[10:15:52] <linkmauve> I’ll check out how it’s built.
[10:16:24] <linkmauve> Ah, they use a proprietary bl31…
[10:16:55] <linkmauve> https://github.com
[10:16:56] <phrik> Title: PKGBUILDs/alarm/uboot-odroid-m1/PKGBUILD at master · archlinuxarm/PKGBUILDs · GitHub (at github.com)
[10:17:52] <linkmauve> # gpg --version
[10:17:52] <linkmauve> gpg (GnuPG) 2.4.8
[10:18:40] <linkmauve> I guess I’ll try to use their proprietary bootloader for the time being, but will try to figure out why the (almost-)free software one doesn’t enable the extension.
[10:28:35] <Solskogen> great news :-)
[10:30:23] <linkmauve> Solskogen, the crypto extension is apparently the last missing piece for mainline support in TF-A: https://lore.kernel.org
[10:30:25] <phrik> Title: [PATCH v2 05/12] rockchip: board: qnap-ts433: Add instructions for how to use upstream TF-A - Heiko Stuebner (at lore.kernel.org)
[11:03:57] <linkmauve> :: Import PGP key 0CF25682E6BA0751, "Unknown Packager"? [Y/n
[11:04:23] <linkmauve> I’ve correctly done the first two steps now, pacman-key --init and --populate archlinux, yet it doesn’t recognize the signatures.
[11:05:34] <linkmauve> Ah I’m stupid, I had to update archlinux-keyring first!
[11:08:13] <linkmauve> Hm no, even with archlinux-keyring 20260107-2 it still fails on this Unknown Packager.
[11:08:43] <SpieringsAE> yeah you need to download the key from the repo
[11:08:55] <SpieringsAE> and do pacman-key --add and then sign it or something
[11:09:31] <SpieringsAE> I dont have the link for the key on hand
[11:10:35] <linkmauve> Seems to be https://arch-linux-repo.drzee.net
[11:10:54] <SpieringsAE> yep
[11:57:28] <Solskogen> yeah, we're not /that/ offcial yet :-)
[11:59:41] <Solskogen> heftig: you might want to look into the IRC bridge with Matrix. It doesn't seem to quite work. Stuff I write in Matrix doesn't show up on IRC (it works the other way)
[12:56:28] -!- titus_livius has joined #archlinux-ports
[13:14:18] -!- heftig-weechat has joined #archlinux-ports
[13:14:28] <heftig-weechat> ping
[13:14:32] <heftig> pong
[13:14:42] <heftig-weechat> Solskogen: please test
[13:16:08] <gromit> Solskogen: are you registered with the bridge?
[13:16:16] <heftig> registered with nickserv
[13:17:10] <heftig> the very end of https://wiki.archlinux.org explains how to do that
[13:17:11] <phrik> Title: DeveloperWiki:Staff Services - ArchWiki (at wiki.archlinux.org)
[13:33:00] <cjc7373> Hi, I want to help with aarch64 ports. Where do I start?
[13:36:39] <linkmauve> Hmm, the wine package doesn’t seem to run properly here, it “wine: failed to start L"C:\\windows\\system32\\wineboot.exe": c0000135”
[13:37:04] <linkmauve> I see only i686 and x86_64 Windows rootfs in the package, alongside aarch64 unix libraries.
[13:37:41] <linkmauve> Would it make sense for me to start packaging FEX-Emu’s CPU emulation in a dll?
[13:37:48] <linkmauve> I believe that’s the missing piece.
[14:07:14] <Solskogen> I get this from the IRC-bridge: No clients connected to this network, not reconnecting
[14:07:43] <Solskogen> cjc7373: fix wine :-)
[14:08:10] <Solskogen> linkmauve: yeah, fixes are welcome!
[14:09:48] <Antiz> cjc7373: There are some info at https://ports.archlinux.page & https://ports.archlinux.page
[14:09:50] <phrik> Title: Arch Linux Ports (at ports.archlinux.page)
[14:10:35] <Solskogen> cjc7373: jokes aside - test stuff - and if something isn't working either report it here or create a PR to fix it (or both)
[14:12:37] <cjc7373> already testing. So far every package I need seems to be working :)
[14:13:24] <cjc7373> Does every package in the repo built with official PKGBUILD with no patch?
[14:13:41] <Solskogen> our kernel config is far from perfect. I know Ben would love some PRs about that (https://gitlab.archlinux.org/bschnei/linux - the aarch64 branch)
[14:13:42] <phrik> Title: Benjamin Schneider / linux · GitLab (at gitlab.archlinux.org)
[14:14:40] <Solskogen> cjc7373: almost. if not, I create PRs about if. There are *some* expections - those are in my gitlab.
[14:18:41] <heftig> Solskogen: right; i had deactivated your account on the bridge because of inactivity
[14:18:46] <heftig> should work again, now
[14:18:56] <heftig> just talk here once
[14:19:25] -!- solskogen|M has joined #archlinux-ports
[14:19:26] <solskogen|M> This is talk!
[14:19:31] <heftig-weechat> there we go
[14:19:37] <Solskogen> thank you!
[14:19:53] -!- heftig-weechat has quit [Quit: WeeChat 4.8.1]
[14:22:13] <solskogen|M> with regards to wine, I'm quite certain it has to do with that mingw-gcc isn't configured for aarch64. I think I'm able to do something about that.
[14:26:32] -!- SpieringsAE has quit [Remote host closed the connection]
[14:32:02] <linkmauve> solskogen|M, I think it’s much more useful to keep builds for i686 and x86_64 at least for now, because that’s what the vast majority of the Windows programs people will want to use.
[14:32:30] <linkmauve> Although with the ARM64EC ABI it might work too.
[14:32:47] <solskogen|M> yes, the aarch64 target is a addition. not to replace.
[14:34:10] <solskogen|M> adding aarch64 support for binutils and gcc (as in the cross compilers) can be useful anyways
[14:35:49] <solskogen|M> I wonder how many people are coding in ada and cross compiling it for windows...
[15:40:19] -!- cjc7373 has quit [Remote host closed the connection]
[15:40:44] -!- cjc7373 has joined #archlinux-ports
[15:43:26] -!- drathir_tor has quit [Remote host closed the connection]
[15:51:38] -!- drathir_tor has joined #archlinux-ports
[16:01:30] -!- cjc7373 has quit [Ping timeout: 256 seconds]
[16:36:33] -!- cjc7373 has joined #archlinux-ports
[21:33:14] <solskogen|M> binarycraft: Yes-ish. What packages are you missing? It's not a place for aur packages. I want that repo to be as small as possible (in fact, I don't what it to exist at all)
[21:34:16] <solskogen|M> kyeh: No, not really. We're looking into making small images that can be used to install the tarball. I made one for the Pi already (it's not published anywhere, it's just a PoC)
[21:35:43] <solskogen|M> Care to elaborate? :-)
[21:41:13] <solskogen|M> ah, will fix.
[21:48:51] <linkmauve> Are you talking to yourself? :D
[22:16:25] <solskogen|M> libpisp 1.2.1 is now in forge
[22:17:29] <solskogen|M> I've never gotten archiso to work on my aarch64 machines - and it's using ALARM. Not ours.
[23:00:42] <linkmauve> solskogen|M, so, from what I’ve gathered, mingw-gcc doesn’t support AArch64 whatsoever, so we need llvm-mingw instead. I’ve attempted to package it, but I’m nowhere close to getting it to work so far.
[23:01:32] <solskogen|M> winpthreads giving you a hard time?
[23:05:18] <linkmauve> Figuring out how to build LLVM and all its components mostly.
[23:10:12] -!- titus_livius has joined #archlinux-ports