!QCCCSJHEsTIfozrZxz:nixos.org

Nix + Go

239 Members
Go packaging for and with Nixpkgs. | Be excellent to each other.49 Servers

Load older messages


SenderMessageTime
26 Mar 2024
@diamondburned:matrix.orgDiamond (it/she)that was long ago too 22:11:22
@jrick:zettaport.comjricki "get" go.work but i don't get why people are adding it to their repos on their main/master branches (might make sense on a development branch)22:21:09
@jrick:zettaport.comjrickespecially don't get it if they are making release tags containing it22:21:50
27 Mar 2024
@diamondburned:matrix.orgDiamond (it/she) gotk4-examples has one just to keep all submodules in sync w/ the outer one 04:47:45
@diamondburned:matrix.orgDiamond (it/she)there's a github action to guarantee that04:47:49
28 Mar 2024
@verscheures:matrix.orgverscheures joined the room.10:23:21
29 Mar 2024
@sebtm:lodere.esSebTM joined the room.04:22:42
2 Apr 2024
@mkal:matrix.orgmkal joined the room.08:49:25
3 Apr 2024
@maka_77x:matrix.orgmaka_77x joined the room.14:10:25
@jrick:zettaport.comjrick i think tests are broken (possibly by proxyVendor) of any internal package, all the non-internal packages pass internal ones fail with fork/exec /build/go-build245361709/b286/primitives.test: no such file or directory (where primitives is the name of the package) 15:42:24
@jrick:zettaport.comjrickoh nvm, i see other internal packages are passing hmmmm15:43:02
@jrick:zettaport.comjricknot sure if the .test binary is missing, or something it is trying to spawn..15:47:02
@jrick:zettaport.comjrickhow can i observe what is happening inside of the test/build sandbox?16:00:32
@jrick:zettaport.comjrick hmm ok, got to same error in a nix develop shell, let's see.. 17:57:14
@jrick:zettaport.comjrick
[jrick@elsa:~/nixos/tmp/source]$ go test -c ./internal/staging/primitives

[jrick@elsa:~/nixos/tmp/source]$ ldd ./primitives.test 
	statically linked

[jrick@elsa:~/nixos/tmp/source]$ ./primitives.test 
Could not start dynamically linked executable: ./primitives.test
NixOS cannot run dynamically linked executables intended for generic
linux environments out of the box. For more information, see:
https://nix.dev/permalink/stub-ld
17:59:11
@jrick:zettaport.comjrickuhh17:59:13
@jrick:zettaport.comjrick qbit: halp :D 18:00:23
@jrick:zettaport.comjrickah it's a pie executable, hmmm18:01:34
@jrick:zettaport.comjricki think all the other passing tests link to net, and are using the external linker, let me confirm18:03:14
@jrick:zettaport.comjrickyeah it's just these test executables that get compiled to static pie that are broken. wacky18:07:48
@jrick:zettaport.comjrick
[jrick@elsa:~/nixos/tmp/source]$ go test -c -ldflags=-linkmode=external ./internal/staging/primitives/

[jrick@elsa:~/nixos/tmp/source]$ ./primitives.test 
PASS
18:15:48
@jrick:zettaport.comjrickso ldflags in the attrset is being ignored when building tests, only the regular commands in the build stage18:16:37
@jrick:zettaport.comjricki uh.. not sure how to fix that. i don't think you can pass along ldflags in GOFLAGS can you?18:17:33
@jrick:zettaport.comjrickguess you can18:18:28
@jrick:zettaport.comjrickyeah, there's nothing like https://github.com/NixOS/nixpkgs/blob/master/pkgs/build-support/go/module.nix#L218 for the checkPhase18:22:21
@jrick:zettaport.comjrickhmm what's a trivial go module to include for the repro writeup :)18:38:27
@jrick:zettaport.comjrickcan't use net or cgo18:38:43
@qbit:tapenet.org@qbit:tapenet.org Mmmm 18:43:00
@jrick:zettaport.comjrickhuh, ok false alarm. i saw this because i was writing my own checkPhase18:51:21
4 Apr 2024
@jrick:zettaport.comjrickit looks like some .info files are missing with proxyVendor for transitive module requirements that aren't actually imported at all18:03:28

Show newer messages


Back to Room ListRoom Version: 9