#archlinux-ports | Logs for 2026-01-22
Back
[00:59:15] -!- Daanct12 has joined #archlinux-ports
[04:39:39] -!- hcmb_ has joined #archlinux-ports
[04:39:39] hcmb is now known as Guest8705
[04:39:39] -!- Guest8705 has quit [Killed (platinum.libera.chat (Nickname regained by services))]
[04:39:39] hcmb_ is now known as hcmb
[07:21:44] -!- SpieringsAE has joined #archlinux-ports
[08:28:03] <C0rn3j|M> Yep, did so initially
[08:42:15] <C0rn3j|M> I did a small writeup on how I did it here if it's useful to anyone - https://t.me
[08:42:15] <phrik> Title: Telegram: Contact @ArchLinuxARMgroup (at t.me)
[09:36:12] -!- Daanct12 has quit [Quit: WeeChat 4.8.1]
[10:14:52] -!- gromit has quit [Quit: ZNC 1.10.1+docker-git--rc11.10.x-znc-1.10.0-12-gee54fb12 - https://znc.in]
[10:16:52] -!- gromit has joined #archlinux-ports
[10:58:18] <solskogen|M> Very nice
[10:59:56] <solskogen|M> I'm just waiting for the email @freswa and anthraxx talked about in https://gitlab.archlinux.org
[10:59:57] <phrik> Title: aarch64 support (!7) · Merge requests · Arch Linux / Packaging / Packages / glibc · GitLab (at gitlab.archlinux.org)
[11:16:44] -!- titus_livius has joined #archlinux-ports
[12:09:52] <anthraxx|M> mkurz: yes it is, that said there are 2 special cases for very specific packages that we'd propose to allow. the glibc one, and the obsidian one also looks similar i'd need to run a check on aarch64 machine.
[12:27:26] <gromit> anthraxx|M: do you still have access to the hetzner vserver I'm hosting?
[12:27:58] <gromit> I was thinking about having something like this as an official arch thing, but I feel like we might not be advanced enough with the ports effort to do so
[12:28:30] <gromit> See https://gitlab.archlinux.org for a more detailed proposal
[12:28:32] <phrik> Title: Draft: tf-stage1: Add ARM sandbox server (!1060) · Merge requests · Arch Linux / infrastructure · GitLab (at gitlab.archlinux.org)
[12:37:54] <solskogen|M> <anthraxx|M> "yes it is, that said there are 2..." <- next in line is vlc and qemu
[13:09:19] <linkmauve> Is there already a PXE-compatible image?
[13:27:48] <solskogen|M> linkmauve: No - We don't even have images (yet)
[13:28:57] <solskogen|M> I did manage to make a script that creates images that can be either used as is, or used to install it on the medium you want
[14:36:46] -!- NoaHimesaka18731 has quit [Quit: The Lounge - https://thelounge.chat]
[16:01:23] -!- SpieringsAE has quit [Quit: SpieringsAE]
[19:42:39] -!- marmis has quit [Quit: Bye!]
[19:48:37] -!- h|weechat has quit [Ping timeout: 264 seconds]
[20:09:14] -!- marmis has joined #archlinux-ports
[20:13:02] -!- h|weechat has joined #archlinux-ports
[21:09:24] <heftig> Solskogen: can you add `aarch64-linux-gnu-*` symlinks to the aarch64 gcc?
[21:09:34] <heftig> similar to what our gcc does with x86_64-linux-gnu-*
[21:10:00] <solskogen|M> I cannot add something that is already there :-)
[21:10:35] <solskogen|M> We've got both aarch64-unknown-linux-gnu-gcc AND aarch64-linux-gnu-gcc.
[21:10:37] <heftig> hm? gcc-15.2.1+r447+g6a64f6c3ebb8-1-aarch64 doesn't contain any
[21:11:24] <solskogen|M> And from where did you get that?
[21:12:18] <heftig> https://archlinuxarm.org
[21:12:20] <phrik> Title: gcc (aarch64) | Packages | Arch Linux ARM (at archlinuxarm.org)
[21:12:26] <solskogen|M> I've had those symlinks for quite some time.
[21:12:38] <solskogen|M> That is not our packages. Those are ALARMs.
[21:12:47] <heftig> which project are you working on?
[21:13:18] <solskogen|M> I'm the one creating the packages that DrZee hosts
[21:13:30] <solskogen|M> https://ports.archlinux.page
[21:13:31] <phrik> Title: Aarch64 | Arch Linux Ports (at ports.archlinux.page)
[21:14:02] * heftig uploaded an image: (226KiB) < https://matrix.archlinux.org >
[21:14:32] <solskogen|M> DrZee: explain yourself!
[21:15:43] <heftig> anyway, thanks
[21:16:22] <heftig> i wanted to configure the full triple-based names for all the tools in rust
[21:16:36] <solskogen|M> We're not affiliated with ALARM in that regard. We just used ALARM as a base to bootstrap. We've now got hell of a lot more packages than ALARM :-)
[21:16:37] <heftig> (and remove the /usr/bin/ prefix where possible)
[21:17:18] <solskogen|M> the aarch64 cross compiler in Arch x86_64 is using the "wrong" triple.
[21:18:04] <heftig> well, once that gets corrected i guess i can move the names over
[21:18:08] <solskogen|M> the -any packages are pulled from x86_64, yes. First we tried that as a test, to see if that worked - and it did. Haven't had any problems so far (6 months)
[21:18:23] <solskogen|M> the correct triple is aarch64-unknown-linux-gnu
[21:18:43] <solskogen|M> while the aarch64 cross compiler is using aarch64-linux-gnu-gcc.
[21:19:26] <solskogen|M> That said, I think aarch64-linux-gnu-gcc looks better than aarch64-unknown-linux-gnu. But config.guess disagrees.
[21:22:29] <solskogen|M> that's the reason why I also have aarch64-linux-gnu-* symlinks as well. I should probably do the same with binutils, but I haven't seen the need yet
[21:29:02] <heftig> Solskogen: that mess extends across distributions
[21:30:24] <heftig> x86_64-pc-linux-gnu vs x86_64-unknown-linux-gnu vs x86_64-linux-gnu vs x86_64-redhat-linux and more
[21:31:18] <heftig> arch decided on x86_64-pc-linux-gnu and also configured clang that way but rust disagrees that it exists