2025/11/25

Newest at the top

2025-11-25 21:42:12 +0100vanishingideal(~vanishing@user/vanishingideal) vanishingideal
2025-11-25 21:40:35 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 240 seconds)
2025-11-25 21:40:09 +0100 <tomsmeding> but nice :)
2025-11-25 21:40:06 +0100 <tomsmeding> Wygulmage: protip: use tab-completion for nicks, mentioning doesn't work if there's a typo :)
2025-11-25 21:36:17 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-11-25 21:34:27 +0100Frostillicus(~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net)
2025-11-25 21:33:03 +0100 <Wygulmage> tomsmedding: Sorry for the belated answer. Thank you. `.&&.` is exactly what I wanted.
2025-11-25 21:32:41 +0100Wygulmage(~Wygulmage@user/Wygulmage) Wygulmage
2025-11-25 21:26:37 +0100kitadamian(~kitadamia@95.49.84.49.ipv4.supernova.orange.pl) (Quit: Client closed)
2025-11-25 21:26:15 +0100Frostillicus(~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net) (Ping timeout: 250 seconds)
2025-11-25 21:25:15 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 240 seconds)
2025-11-25 21:23:44 +0100ttybitnik(~ttybitnik@user/wolper) ttybitnik
2025-11-25 21:20:45 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-11-25 21:18:01 +0100jmcantrell(~weechat@user/jmcantrell) (Ping timeout: 250 seconds)
2025-11-25 21:16:59 +0100kritzefitz(~kritzefit@debian/kritzefitz) kritzefitz
2025-11-25 21:11:52 +0100jmcantrell(~weechat@user/jmcantrell) jmcantrell
2025-11-25 21:11:05 +0100peterbecich(~Thunderbi@172.222.148.214) (Ping timeout: 250 seconds)
2025-11-25 21:10:15 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 240 seconds)
2025-11-25 21:06:51 +0100hseg_(~hseg_@46.120.21.70) (Remote host closed the connection)
2025-11-25 21:06:23 +0100Wygulmage(~Wygulmage@user/Wygulmage) (Ping timeout: 250 seconds)
2025-11-25 21:05:55 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-11-25 21:04:04 +0100ft(~ft@p508db844.dip0.t-ipconnect.de) ft
2025-11-25 21:01:07 +0100Square3(~Square@user/square) (Ping timeout: 250 seconds)
2025-11-25 21:00:11 +0100peterbecich(~Thunderbi@172.222.148.214) peterbecich
2025-11-25 20:57:52 +0100Frostillicus(~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net)
2025-11-25 20:57:36 +0100Square2(~Square4@user/square) Square
2025-11-25 20:56:22 +0100Frostillicus(~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net) (Ping timeout: 244 seconds)
2025-11-25 20:55:31 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 264 seconds)
2025-11-25 20:54:30 +0100 <hseg> it wants to get its package dbs on the command line
2025-11-25 20:53:40 +0100 <hseg> ahhhh. the problem is that setup.hs does nothing with GHC_ENVIRONMENT
2025-11-25 20:50:54 +0100Googulator56(~Googulato@2a01-036d-0106-4ad8-11e2-562e-881b-eb37.pool6.digikabel.hu) (Quit: Client closed)
2025-11-25 20:50:50 +0100Googulator33(~Googulato@2a01-036d-0106-4ad8-11e2-562e-881b-eb37.pool6.digikabel.hu)
2025-11-25 20:50:35 +0100sindu(~sindu@2.148.32.207.tmi.telenormobil.no) (Ping timeout: 240 seconds)
2025-11-25 20:50:31 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-11-25 20:48:04 +0100 <hseg> it's just that the compiled Setup.hs configure call doesn't make use of GHC_ENVIRONMENT
2025-11-25 20:47:25 +0100 <hseg> cleaning the test environment, ghc clearly logs that it's loading the package environment
2025-11-25 20:47:07 +0100 <hseg> wait!
2025-11-25 20:46:35 +0100 <hseg> under cabal exec it does pick up GHC_ENVIRONMENT, but for some reason it isn't satisfied
2025-11-25 20:46:09 +0100 <geekosaur> I'd expect not; I was hoping that, since `cabal run` can build first, it'd just keep it exported
2025-11-25 20:44:33 +0100 <tomsmeding> (build it first with `cabal build`, then run with `cabal exec`)
2025-11-25 20:44:16 +0100 <tomsmeding> and under `cabal exec`?
2025-11-25 20:44:02 +0100 <hseg> nope -- dumping environment under cabal run shows no GHC_* envvars
2025-11-25 20:43:35 +0100pavonia(~user@user/siracusa) siracusa
2025-11-25 20:40:06 +0100Frostillicus(~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net)
2025-11-25 20:39:35 +0100Frostillicus(~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net) (Read error: Connection reset by peer)
2025-11-25 20:39:19 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 244 seconds)
2025-11-25 20:37:12 +0100 <geekosaur> hack, see if it's there with `cabal run`? (there are enough differences between the two that using `cabal run` to run test suites is relatively common)
2025-11-25 20:35:06 +0100merijn(~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn
2025-11-25 20:28:10 +0100ttybitnik(~ttybitnik@user/wolper) (Quit: Fading out...)
2025-11-25 20:25:54 +0100tomsmedingwonders how long ago it has been that this has worked properly in the first place