2026/02/11

Newest at the top

2026-02-11 18:59:21 +0100 <haskellbridge> <sm> stack version doesn't matter much, no
2026-02-11 18:58:21 +0100 <perryprog> my stack version /shouldn't/ matter if it's just a cabal project, right??
2026-02-11 18:57:43 +0100 <perryprog> failed on cabal 3.14.2.0
2026-02-11 18:56:50 +0100haskellbridgesm tries 9.12.2 on mac
2026-02-11 18:56:30 +0100 <geekosaur> in case a GC bug crept into .2
2026-02-11 18:56:27 +0100sord937_(~sord937@gateway/tor-sasl/sord937) (Quit: sord937_)
2026-02-11 18:56:15 +0100 <geekosaur> might still be worth trying 9.12.1
2026-02-11 18:55:40 +0100rncwnd(~quassel@2a01:4f8:221:27c6::1)
2026-02-11 18:55:28 +0100rncwnd(~quassel@2a01:4f8:221:27c6::1) (Server closed connection)
2026-02-11 18:54:13 +0100 <perryprog> (/s)
2026-02-11 18:54:11 +0100 <perryprog> the project needs 9.12.1 or higher, so I kinda doubt it needs 9.12.1 and not 9.12.2 unless it relied on inaccurate division somehow
2026-02-11 18:52:59 +0100 <perryprog> I tried with a git clean -fxd which should be same thing
2026-02-11 18:52:47 +0100Guest2(~Guest2@client-8-178.eduroam.oxuni.org.uk) (Quit: Client closed)
2026-02-11 18:52:37 +0100 <haskellbridge> <sm> I might even try building in a fresh clone, to rule out ghc environment files
2026-02-11 18:52:05 +0100 <haskellbridge> <sm> you could also try building with a different ghc version, cabal-install version, and/or stack
2026-02-11 18:51:48 +0100 <geekosaur> (because in that ticket it's `Setup` that segfaults, so it wouldn't reach running ghc)
2026-02-11 18:51:25 +0100 <geekosaur> alternatively it might be https://github.com/haskell/cabal/issues/11465, but as it's not custom `Setup` and it reached running ghc that seems pretty unlikely
2026-02-11 18:51:09 +0100 <haskellbridge> <sm> I was going to say ask #hackage:matrix.org (https://matrix.to/#/#hackage:matrix.org) . It looks like a very straightforward package, clearly there's a tool bug
2026-02-11 18:50:31 +0100 <perryprog> but I don't want to file an issue, I want my build to work ;-; /hj
2026-02-11 18:50:30 +0100 <lambdabot> [1,11,2,12,3,13]
2026-02-11 18:50:29 +0100 <probie> > foldr (\x k ys -> case ys of { [] -> []; (y:ys') -> x:y:k ys' }) (const []) [1, 2, 3] [11, 12, 13] -- to clarify, this is a joke
2026-02-11 18:50:08 +0100 <geekosaur> perryprog: if I read that log correctly, it's ghc that segfaulted so you may want to file an issue on gitlab
2026-02-11 18:49:13 +0100 <probie> Or use `foldr`. `foldr` solves everything
2026-02-11 18:49:04 +0100 <Guest2> Thanks
2026-02-11 18:48:59 +0100 <Guest2> Oh that's clever
2026-02-11 18:48:32 +0100 <lambdabot> [1,11,2,12,3,13]
2026-02-11 18:48:31 +0100 <probie> > concat $ zipWith (\x y -> [x,y]) [1,2,3] [11,12,13]
2026-02-11 18:48:20 +0100 <Guest2> Wouldn't that give me a list of pairs? I waned to combine two lists into one of the same type
2026-02-11 18:47:25 +0100 <haskellbridge> <sm> Guest2 you're thinking of zip maybe. It would be a start
2026-02-11 18:47:04 +0100 <perryprog> nw
2026-02-11 18:47:02 +0100 <haskellbridge> <sm> perryprog good, just making sure
2026-02-11 18:46:35 +0100 <haskellbridge> <sm> \o/
2026-02-11 18:46:34 +0100 <perryprog> sm, I'm sure—I just checked with htop -d 1. 10 GB free the whole time.
2026-02-11 18:46:24 +0100bliminse(~bliminse@user/bliminse) bliminse
2026-02-11 18:46:21 +0100 <__monty__> sm: Maybe I was adding my dependencies wrong. I refactored a bit and now I'm getting the expected behavior.
2026-02-11 18:46:08 +0100bliminse_(~bliminse@user/bliminse) (Server closed connection)
2026-02-11 18:45:51 +0100 <haskellbridge> <sm> are you sure it's not eating up your loads of memory due to a compiler bug ? I would make sure
2026-02-11 18:45:04 +0100 <haskellbridge> <sm> I see Cabal-7125, but as usual it's not in the haskell error index
2026-02-11 18:44:49 +0100 <Guest2> Hey, sorry for the stupid question, but is there a built-in function to "interleave" two lists? Like f [1,2,3] [11,12,13] = [1,11,2,12,3,13]. I for some reason thought there was one, but I can't find it now, did I dream it up or something?
2026-02-11 18:44:11 +0100 <perryprog> nope, I got loads
2026-02-11 18:43:46 +0100 <haskellbridge> <sm> are you running out of memory perryprog ? watch with a fast-updating top , eg
2026-02-11 18:41:18 +0100tzh(~tzh@c-76-115-131-146.hsd1.or.comcast.net)
2026-02-11 18:40:17 +0100karenw(~karenw@user/karenw) (Ping timeout: 250 seconds)
2026-02-11 18:39:47 +0100 <perryprog> I'm having some trouble troubleshooting a build failure—I'm getting "The build process segfaulted" from cabal and I'm not seeing much help from cabal build -v (https://paste.tomsmeding.com/aGOsdU5i). The project is https://github.com/pdobsan/oama. There's reports of this sort of build failure from a few years ago also on macOS, but that was from an older macOS version and also seems to have been fixed...
2026-02-11 18:37:52 +0100 <haskellbridge> <sm> if by <file> you mean a shake target
2026-02-11 18:37:25 +0100 <haskellbridge> <sm> __monty__ I think that's implied, isn't it ? Shake's dependency engine will do that by default
2026-02-11 18:36:38 +0100perryprog(~perryprog@wikipedia/perryprog) perryprog
2026-02-11 18:35:33 +0100tromp(~textual@2001:1c00:3487:1b00:5913:697:5f95:d198)
2026-02-11 18:35:23 +0100Guest2(~Guest2@client-8-178.eduroam.oxuni.org.uk)
2026-02-11 18:31:51 +0100tromp(~textual@2001:1c00:3487:1b00:5913:697:5f95:d198) (Quit: My iMac has gone to sleep. ZZZzzz…)