Newest at the top
| 2025-11-03 16:35:27 +0100 | <dminuoso> | Or I guess "Nix modules" rather? Not sure. |
| 2025-11-03 16:35:16 +0100 | <dminuoso> | But at least I can communicate this via NixOS modules to haskell.nix |
| 2025-11-03 16:34:56 +0100 | ttybitnik | (~ttybitnik@user/wolper) (Quit: Fading out...) |
| 2025-11-03 16:33:56 +0100 | <dminuoso> | https://github.com/input-output-hk/haskell.nix/issues/887#issuecomment-1489632156 has some details about this. |
| 2025-11-03 16:33:19 +0100 | <dminuoso> | davean: Ah turns out that does not work. Seems to be an extension of https://github.com/haskell/cabal/issues/6343 |
| 2025-11-03 16:31:07 +0100 | humasect | (~humasect@dyn-192-249-132-90.nexicom.net) |
| 2025-11-03 16:30:35 +0100 | deptype | (~deptype@2406:b400:3a:73c2:6c77:97e3:113e:dea6) |
| 2025-11-03 16:30:22 +0100 | deptype | (~deptype@2406:b400:3a:73c2:a4a3:fb37:661e:a962) (Remote host closed the connection) |
| 2025-11-03 16:28:09 +0100 | Nachtgespenst | (~user@user/siracusa) (Quit: Bye!) |
| 2025-11-03 16:25:36 +0100 | Square | (~Square4@user/square) Square |
| 2025-11-03 16:24:57 +0100 | Square | (~Square4@user/square) (Remote host closed the connection) |
| 2025-11-03 16:10:49 +0100 | prdak1 | prdak |
| 2025-11-03 16:10:49 +0100 | prdak | (~Thunderbi@user/prdak) (Ping timeout: 264 seconds) |
| 2025-11-03 16:10:39 +0100 | deptype | (~deptype@2406:b400:3a:73c2:a4a3:fb37:661e:a962) |
| 2025-11-03 16:10:22 +0100 | Zemyla | (~Zemyla@72.178.108.235) Zemyla |
| 2025-11-03 16:10:20 +0100 | deptype | (~deptype@2406:b400:3a:73c2:422:9c14:cc52:da31) (Remote host closed the connection) |
| 2025-11-03 16:08:13 +0100 | prdak1 | (~Thunderbi@user/prdak) prdak |
| 2025-11-03 16:07:59 +0100 | trickard_ | (~trickard@cpe-52-98-47-163.wireline.com.au) |
| 2025-11-03 16:07:45 +0100 | trickard | (~trickard@cpe-52-98-47-163.wireline.com.au) (Read error: Connection reset by peer) |
| 2025-11-03 16:02:27 +0100 | <davean> | dminuoso: I would specificly recomend setting profiling: true in your cabal.project before entering the flake |
| 2025-11-03 16:02:23 +0100 | ezzieyguywuf | (~Unknown@user/ezzieyguywuf) ezzieyguywuf |
| 2025-11-03 15:58:36 +0100 | <davean> | I think dminuoso can fix this either by setting profiling in cabal.project or in the flake with configureArgs |
| 2025-11-03 15:58:35 +0100 | Zemyla | (~Zemyla@72.178.108.235) (Ping timeout: 250 seconds) |
| 2025-11-03 15:57:52 +0100 | <davean> | right, it builds a build way one time usually. I'm addressing why I think haskell.nix is breaking it |
| 2025-11-03 15:57:17 +0100 | <tomsmeding> | makes sense; I was just arguing against "cabal usually won't rebuild something for profiling" |
| 2025-11-03 15:56:48 +0100 | <davean> | yes because its a different build config |
| 2025-11-03 15:56:26 +0100 | <tomsmeding> | if I use `cabal build --enable-profiling` on a project where I have not done so before, cabal definitely starts rebuidling the world with profiling. |
| 2025-11-03 15:55:41 +0100 | <davean> | dminuoso: no, profiling is a build option for GHC, cabal usually won't rebuild something for profiling, it builts it the first time for it. |
| 2025-11-03 15:53:32 +0100 | Zemyla | (~Zemyla@72.178.108.235) Zemyla |
| 2025-11-03 15:44:39 +0100 | trickard_ | trickard |
| 2025-11-03 15:40:50 +0100 | trickard_ | (~trickard@cpe-52-98-47-163.wireline.com.au) |
| 2025-11-03 15:40:37 +0100 | trickard_ | (~trickard@cpe-52-98-47-163.wireline.com.au) (Read error: Connection reset by peer) |
| 2025-11-03 15:39:26 +0100 | DetourNetworkUK | (~DetourNet@user/DetourNetworkUK) DetourNetworkUK |
| 2025-11-03 15:37:59 +0100 | DetourNetworkUK | (DetourNetw@user/DetourNetworkUK) (Read error: Connection reset by peer) |
| 2025-11-03 15:31:08 +0100 | prdak | (~Thunderbi@user/prdak) prdak |
| 2025-11-03 15:30:48 +0100 | Square | (~Square4@user/square) Square |
| 2025-11-03 15:28:24 +0100 | prdak | (~Thunderbi@user/prdak) (Ping timeout: 252 seconds) |
| 2025-11-03 15:27:34 +0100 | prdak2 | (~Thunderbi@user/prdak) prdak |
| 2025-11-03 15:25:51 +0100 | trickard_ | (~trickard@cpe-52-98-47-163.wireline.com.au) |
| 2025-11-03 15:25:37 +0100 | trickard_ | (~trickard@cpe-52-98-47-163.wireline.com.au) (Read error: Connection reset by peer) |
| 2025-11-03 15:24:43 +0100 | Frostillicus | (~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net) |
| 2025-11-03 15:24:36 +0100 | <dminuoso> | So is profiling similar to cabal flags in that respect? |
| 2025-11-03 15:22:09 +0100 | Frostillicus | (~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net) (Ping timeout: 244 seconds) |
| 2025-11-03 15:19:54 +0100 | <Leary> | My guess: It means that the ghc cabal is using has non-profiling versions of the libraries registered in its global package database, which get in the way of it building its own. |
| 2025-11-03 15:19:49 +0100 | <tomsmeding> | normally cabal would realise that a particular dependency has not been built for profiling yet, and start doing so |
| 2025-11-03 15:19:23 +0100 | <dminuoso> | Since it is just plain cabal-install |
| 2025-11-03 15:19:19 +0100 | <dminuoso> | This is why my question was rather about what cabal is barking about rather. |
| 2025-11-03 15:18:51 +0100 | <tomsmeding> | probably, and where I sign off because I have no clue |
| 2025-11-03 15:18:41 +0100 | <dminuoso> | Would this be the time where I admit that I may be using haskell.nix? |
| 2025-11-03 15:18:38 +0100 | <tomsmeding> | if nuking the store doesn't help, that rules this out |