Newest at the top
| 2025-11-25 20:56:22 +0100 | Frostillicus | (~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net) (Ping timeout: 244 seconds) |
| 2025-11-25 20:55:31 +0100 | merijn | (~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 +0100 | Googulator56 | (~Googulato@2a01-036d-0106-4ad8-11e2-562e-881b-eb37.pool6.digikabel.hu) (Quit: Client closed) |
| 2025-11-25 20:50:50 +0100 | Googulator33 | (~Googulato@2a01-036d-0106-4ad8-11e2-562e-881b-eb37.pool6.digikabel.hu) |
| 2025-11-25 20:50:35 +0100 | sindu | (~sindu@2.148.32.207.tmi.telenormobil.no) (Ping timeout: 240 seconds) |
| 2025-11-25 20:50:31 +0100 | merijn | (~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 +0100 | pavonia | (~user@user/siracusa) siracusa |
| 2025-11-25 20:40:06 +0100 | Frostillicus | (~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net) |
| 2025-11-25 20:39:35 +0100 | Frostillicus | (~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net) (Read error: Connection reset by peer) |
| 2025-11-25 20:39:19 +0100 | merijn | (~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 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-11-25 20:28:10 +0100 | ttybitnik | (~ttybitnik@user/wolper) (Quit: Fading out...) |
| 2025-11-25 20:25:54 +0100 | tomsmeding | wonders how long ago it has been that this has worked properly in the first place |
| 2025-11-25 20:24:08 +0100 | <hseg> | Giving up, I'll use something else then |
| 2025-11-25 20:23:55 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 240 seconds) |
| 2025-11-25 20:19:44 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-11-25 20:19:39 +0100 | mulk | (~mulk@pd9514972.dip0.t-ipconnect.de) mulk |
| 2025-11-25 20:18:51 +0100 | <hseg> | urggh |
| 2025-11-25 20:18:46 +0100 | <hseg> | hrmph. it seems cabal _builds_ the test suite with GHC_ENVIRONMENT set, but doesn't _run_ it with it |
| 2025-11-25 20:18:01 +0100 | jmcantrell | (~weechat@user/jmcantrell) (Ping timeout: 264 seconds) |
| 2025-11-25 20:16:02 +0100 | tromp | (~textual@2001:1c00:3487:1b00:bd07:71f2:e20b:fdc) |
| 2025-11-25 20:14:04 +0100 | peterbecich | (~Thunderbi@172.222.148.214) (Ping timeout: 256 seconds) |
| 2025-11-25 20:13:02 +0100 | tomsmeding | wishing hseg luck from the sideline |
| 2025-11-25 20:11:34 +0100 | <hseg> | .... OK, we're gradually closing in on a culprit -- it seems GHC_ENVIRONMENT is getting unset somewhere along the line |
| 2025-11-25 20:11:31 +0100 | jmcantrell | (~weechat@user/jmcantrell) jmcantrell |
| 2025-11-25 20:10:55 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) (Ping timeout: 240 seconds) |
| 2025-11-25 20:06:41 +0100 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-11-25 20:06:13 +0100 | kitadamian | (~kitadamia@95.49.84.49.ipv4.supernova.orange.pl) |
| 2025-11-25 20:04:36 +0100 | Frostillicus | (~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net) |
| 2025-11-25 20:04:14 +0100 | <hseg> | after all, GHC reads it from its environment |
| 2025-11-25 20:04:01 +0100 | <hseg> | ... wait, shouldn't it Just Work? |
| 2025-11-25 20:03:59 +0100 | Everything | (~Everythin@172-232-54-192.ip.linodeusercontent.com) Everything |
| 2025-11-25 20:03:55 +0100 | Frostillicus | (~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net) (Ping timeout: 240 seconds) |
| 2025-11-25 20:02:54 +0100 | Everything | (~Everythin@172-232-54-192.ip.linodeusercontent.com) (Quit: leaving) |
| 2025-11-25 20:02:31 +0100 | <hseg> | hrm. any way of making Setup.hs read GHC_ENVIRONMENT? I'm only seeing support for --package-db |
| 2025-11-25 19:58:42 +0100 | <hseg> | unfortunately, it seems that setup.exe doesn't know to pick up on that file? |
| 2025-11-25 19:58:11 +0100 | <hseg> | nope, the opposite -- it seems to be how it's communicating the package db info to the program it runs |
| 2025-11-25 19:58:00 +0100 | <geekosaur> | (see `--package-env` in cabal) |
| 2025-11-25 19:57:39 +0100 | <geekosaur> | usually you want that disabled, which I think is what cabal is doing |