| 28 Nov 2025 |
 Puna | i guess we have more nixos users on wii & wii u than i was anticipating 🥴.
fine. closed for now, since i don't think that a now-properly-marked-unsupported go prevents anything important from being built anymore (was previously blocking libcap)
| 00:23:06 |
| Puna | * i guess we have more nixos users on wii & wii u than i was anticipating 🥴.
fine. closed for now, since i don't think that a now-properly-marked-unsupported-on-ppc64 go prevents anything important from being built anymore (was previously blocking libcap)
| 00:30:38 |
 jrick | um, neither of those are ppc64, they're 32-bit | 00:30:45 |
| Puna | yes, but i'm mainly doing this for ppc64 rn | 00:31:11 |
| Puna | issue there: see above | 00:31:29 |
| Puna | non-ppc64le POWER then, I guess | 00:32:00 |
| Puna | * yes, but i'm mainly doing this for ppc64 rn, ppc32 was brought up by k900 | 00:37:26 |
| Puna | * issue with ppc64: see above | 00:37:35 |
| Puna | * yes, but i'm mainly doing this for ppc64 rn. ppc32 was brought up by k900 | 00:37:54 |
| 29 Nov 2025 |
|  amadaluzia changed their profile picture. | 11:40:54 |
| 2 Dec 2025 |
|  @fuckill:matrix.org joined the room. | 11:51:57 |
| @fuckill:matrix.org removed their display name Fuckill. | 12:46:13 |
| @fuckill:matrix.org left the room. | 12:46:25 |
|  @curid:matrix.org left the room. | 18:02:18 |
| 4 Dec 2025 |
|  @s_r:matrix.org left the room. | 05:08:29 |
|  isabel changed their profile picture. | 16:41:37 |
| 6 Dec 2025 |
|  P J joined the room. | 07:44:44 |
| 10 Dec 2025 |
|  Saturn changed their profile picture. | 17:23:07 |
| 11 Dec 2025 |
|  suua joined the room. | 16:11:03 |
| 15 Dec 2025 |
|  Tomodachi94 (they/them) joined the room. | 02:37:09 |
| Tomodachi94 (they/them) | Hi all! I just repackaged coc-go to use modern Node tooling. Is anyone interested in being listed as a maintainer for the package? (I don't think I would be a good maintainer for the package, since I am not familiar with Go and haven't really worked with it.)
The PR in question: https://github.com/NixOS/nixpkgs/issues/470903
| 02:39:32 |
| Tomodachi94 (they/them) | * Hi all! I just repackaged coc-go to use modern Node tooling. Is anyone interested in being listed as a maintainer for the package? (I don't think I would be a good maintainer for the package, since I am not familiar with Go and haven't really worked with it.)
The PR in question: https://github.com/NixOS/nixpkgs/pull/470903
| 02:39:44 |
|  ghishadow joined the room. | 08:13:41 |
| 16 Dec 2025 |
|  @azahi:azahi.cc joined the room. | 22:03:26 |
| 19 Dec 2025 |
|  Frédéric Christ changed their display name from Frédéric Christ to Frédéric Christ (back on 02.01.). | 15:15:21 |
| 23 Dec 2025 |
|  sudoforge joined the room. | 22:42:06 |
| sudoforge | there seems to be a significant lack of documentation for cross-compiling for platform targets that are not the builder host using buildGoModule. i know that pkgsCross is probably the recommended approach, but there isn't a 1:1 mapping of supported cross-compilation targets in nixpkgs to golang's supported targets. assuming i want to build for every target that golang supports, does anybody have examples for how to cross-compile using buildGoModule, without assuming that pkgsCross can be used? | 23:48:52 |
| 24 Dec 2025 |
| sudoforge | * there seems to be a significant lack of documentation for cross-compiling for platform targets that are not the builder host using buildGoModule. i know that pkgsCross is probably the recommended approach, but there isn't a 1:1 mapping of supported cross-compilation targets in nixpkgs to golang's supported targets. assuming i want to build for every target that golang supports, does anybody have examples for how to cross-compile using buildGoModule, without assuming that pkgsCross can be used?
i should note that setting env.{GOOS, GOARCH} isn't sufficient, and this is the only other approach i've seen talked about on the forums.
| 00:10:38 |
| sudoforge | * there seems to be a significant lack of documentation for cross-compiling for platform targets that are not the builder host using buildGoModule. i know that pkgsCross is probably the recommended approach, but there isn't a 1:1 mapping of supported cross-compilation targets in nixpkgs to golang's supported targets. assuming i want to build for every target that golang supports, does anybody have examples for how to cross-compile using buildGoModule, without assuming that pkgsCross can be used?
i should note that setting env.{GOOS, GOARCH} isn't sufficient, and this is the only other approach i've seen talked about on the forums (from posts that are 3+ years old).
| 00:10:53 |
 genadij.udarov | Why isnt setting these env vars sufficient? I was going to suggest that. 🫣CGO_ENABLED=0 might be missing? I don't recall if go supports cross-compiling cgo. | 08:05:49 |
