#archlinux-ports | Logs for 2025-08-06
Back
[02:14:25] -!- marmis has quit [Quit: Bye!]
[02:15:28] -!- marmis has joined #archlinux-ports
[05:01:30] -!- marmis has quit [Quit: Bye!]
[05:13:49] -!- marmis has joined #archlinux-ports
[06:12:03] <Solskogen> gromit: and now say hello to DrZee!
[07:53:57] -!- drathir_tor has quit [Ping timeout: 240 seconds]
[08:01:10] -!- drathir_tor has joined #archlinux-ports
[08:16:24] <gromit> DrZee: Heyhey 👋
[08:41:31] <Antiz> Hi all 👋
[09:01:49] <Solskogen> I have a question. The aarch64 cross compiler (https://gitlab.archlinux.org/archlinux/packaging/packages/aarch64-linux-gnu-gcc and friends) have the "wrong" target name aarch64-linux-gnu, and not aarch64-unknown-linux-gnu which is used on Arch on aarch64. Should I or how should I proceed in order to fix that?
[09:01:50] <phrik> Title: Arch Linux / Packaging / Packages / aarch64-linux-gnu-gcc · GitLab (at gitlab.archlinux.org)
[09:04:02] <DrZee> Hi Gromit and everyone else!
[09:12:42] <gromit> Solskogen: This is totally not something where I'm knowledgable, so take my answer with that in mind ... What defines right and wrong in this case? I just ran "gcc -dump-machine" and got "x86_64-pc-linux-gnu" on my x86 machine
[09:12:52] <gromit> Also what goes wrong with the currently set target?
[09:16:20] <Solskogen> config.guess sets that on x86_64, but on aarch64 it is aarch64-unknown-linux-gnu. why the "unknown" part comes in play, I don't know. Personally, I like config.guess on aarch64 to say aarch64-linux-gnu.
[09:17:10] <Solskogen> consistency is my motivation behind wanting to change the cross compiler's name.
[18:21:21] -!- marmis8 has joined #archlinux-ports
[18:23:14] -!- marmis has quit [Ping timeout: 248 seconds]
[18:23:14] marmis8 is now known as marmis
[21:30:58] -!- marmis has quit [Quit: Bye!]
[21:31:56] -!- marmis has joined #archlinux-ports