2025/09/07

Newest at the top

2025-09-07 02:54:18 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-09-07 02:51:40 +0200jespada(~jespada@2800:a4:22ff:7a00:f5ee:99f1:c7f5:1d5a) jespada
2025-09-07 02:49:54 +0200arandombit(~arandombi@user/arandombit) (Ping timeout: 256 seconds)
2025-09-07 02:49:05 +0200jespada(~jespada@2800:a4:2309:e000:7cc9:782d:9408:1f91) (Ping timeout: 244 seconds)
2025-09-07 02:48:49 +0200EvanR(~EvanR@user/evanr) EvanR
2025-09-07 02:48:29 +0200EvanR(~EvanR@user/evanr) (Remote host closed the connection)
2025-09-07 02:46:15 +0200tremon(~tremon@83.80.159.219) (Quit: getting boxed in)
2025-09-07 02:45:07 +0200arandombit(~arandombi@user/arandombit) arandombit
2025-09-07 02:45:07 +0200arandombit(~arandombi@2603:7000:4600:ffbe:2133:587c:64a5:1340) (Changing host)
2025-09-07 02:45:07 +0200arandombit(~arandombi@2603:7000:4600:ffbe:2133:587c:64a5:1340)
2025-09-07 02:43:24 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 258 seconds)
2025-09-07 02:38:54 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-09-07 02:37:34 +0200trickard_trickard
2025-09-07 02:35:29 +0200acidjnk(~acidjnk@p200300d6e7171913b85d875ab8253342.dip0.t-ipconnect.de) (Ping timeout: 250 seconds)
2025-09-07 02:34:36 +0200segfaultfizzbuzz(~segfaultf@23-93-74-222.fiber.dynamic.sonic.net) (Ping timeout: 256 seconds)
2025-09-07 02:32:59 +0200 <geekosaur> oh, looks like instead of the `LD_BIND_NOW=1` part you could use `ldd -r`
2025-09-07 02:32:17 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 258 seconds)
2025-09-07 02:31:33 +0200trickard_(~trickard@cpe-53-98-47-163.wireline.com.au)
2025-09-07 02:31:29 +0200 <geekosaur> ghcup's ghc "binary" is actually a shell script wrapper. you would need to extract the path to the actual ghc binary from it and run `LD_BIND_NOW=1 ldd` on it (at least, I think LD_BIND_NOW works there; not certain) and see if you get the same error. you will also get the path to the glibc (libc.so.6) it's trying to use, but it may be hidden among a bunch of Haskell shared objects. (but in my case it's actually right at the end of the list)
2025-09-07 02:31:08 +0200trickard_(~trickard@cpe-53-98-47-163.wireline.com.au) (Ping timeout: 258 seconds)
2025-09-07 02:30:50 +0200ttybitnik(~ttybitnik@user/wolper) (Quit: Fading out...)
2025-09-07 02:30:21 +0200segfaultfizzbuzz(~segfaultf@23-93-74-222.fiber.dynamic.sonic.net)
2025-09-07 02:28:18 +0200 <geekosaur> there is one more thing you can try but it's a bit involved
2025-09-07 02:27:39 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-09-07 02:27:02 +0200otto_s(~user@p5b044af8.dip0.t-ipconnect.de)
2025-09-07 02:25:31 +0200otto_s(~user@p5de2f1c5.dip0.t-ipconnect.de) (Ping timeout: 248 seconds)
2025-09-07 02:24:54 +0200arandombit(~arandombi@user/arandombit) (Ping timeout: 252 seconds)
2025-09-07 02:21:31 +0200trickard_(~trickard@cpe-53-98-47-163.wireline.com.au)
2025-09-07 02:17:47 +0200Guest62(~Guest62@c-73-217-79-154.hsd1.co.comcast.net) (Ping timeout: 250 seconds)
2025-09-07 02:17:02 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 256 seconds)
2025-09-07 02:14:30 +0200trickard_(~trickard@cpe-53-98-47-163.wireline.com.au) (Read error: Connection reset by peer)
2025-09-07 02:12:17 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-09-07 02:11:02 +0200trickard_(~trickard@cpe-53-98-47-163.wireline.com.au)
2025-09-07 02:10:48 +0200trickard(~trickard@cpe-53-98-47-163.wireline.com.au) (Read error: Connection reset by peer)
2025-09-07 02:10:09 +0200Guest62(~Guest62@c-73-217-79-154.hsd1.co.comcast.net)
2025-09-07 02:06:53 +0200potato44(uid421314@id-421314.lymington.irccloud.com) potato44
2025-09-07 02:01:44 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 256 seconds)
2025-09-07 02:00:48 +0200sprotte24(~sprotte24@p200300d16f1ae200cce55c66184a5d60.dip0.t-ipconnect.de) (Quit: Leaving)
2025-09-07 02:00:14 +0200 <slondr> yeah that's definitely not the case here. I'm in a blank directory with one .hs file
2025-09-07 02:00:06 +0200Tuplanolla(~Tuplanoll@91-159-69-59.elisa-laajakaista.fi) (Quit: Leaving.)
2025-09-07 01:59:54 +0200 <geekosaur> that said, nix wouldn't insert a ghc into your path unless you're in a directorry with a shell.nix and something knows enough about nix to see that file and load the derivations it specifies
2025-09-07 01:57:44 +0200 <geekosaur> shells cache paths, but something run in a subshell or by a program you run from that shell won;t see the cache and will find the nix one first in that case
2025-09-07 01:57:07 +0200 <slondr> though 'echo $PATH' sure does report that the /nix bin directories are above the ghcup bin directories, hmm
2025-09-07 01:56:44 +0200merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-09-07 01:56:16 +0200 <slondr> 'which ghc' reports: $HOME/.ghcup/bin/ghc
2025-09-07 01:55:56 +0200 <geekosaur> the ghc from ghcup won't know about nix
2025-09-07 01:55:42 +0200 <geekosaur> make sure nix isn't substituting its own ghc for the one you intended to use
2025-09-07 01:54:47 +0200 <slondr> I'm not sure why it does
2025-09-07 01:54:42 +0200 <slondr> I don't want ghc to reference anything nix-related at all
2025-09-07 01:53:43 +0200 <geekosaur> nix really wants to be hermetic, but that can break things pretty thoroughly when it comes to stuff like glibc