2025/11/03

Newest at the top

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 +0100Zemyla(~Zemyla@72.178.108.235) Zemyla
2025-11-03 15:44:39 +0100trickard_trickard
2025-11-03 15:40:50 +0100trickard_(~trickard@cpe-52-98-47-163.wireline.com.au)
2025-11-03 15:40:37 +0100trickard_(~trickard@cpe-52-98-47-163.wireline.com.au) (Read error: Connection reset by peer)
2025-11-03 15:39:26 +0100DetourNetworkUK(~DetourNet@user/DetourNetworkUK) DetourNetworkUK
2025-11-03 15:37:59 +0100DetourNetworkUK(DetourNetw@user/DetourNetworkUK) (Read error: Connection reset by peer)
2025-11-03 15:31:08 +0100prdak(~Thunderbi@user/prdak) prdak
2025-11-03 15:30:48 +0100Square(~Square4@user/square) Square
2025-11-03 15:28:24 +0100prdak(~Thunderbi@user/prdak) (Ping timeout: 252 seconds)
2025-11-03 15:27:34 +0100prdak2(~Thunderbi@user/prdak) prdak
2025-11-03 15:25:51 +0100trickard_(~trickard@cpe-52-98-47-163.wireline.com.au)
2025-11-03 15:25:37 +0100trickard_(~trickard@cpe-52-98-47-163.wireline.com.au) (Read error: Connection reset by peer)
2025-11-03 15:24:43 +0100Frostillicus(~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 +0100Frostillicus(~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
2025-11-03 15:18:15 +0100 <tomsmeding> because this looks like a borked install of parser-combinators and attoparsec in the store
2025-11-03 15:18:02 +0100 <dminuoso> why would I have to nuke stuff from cabal store?
2025-11-03 15:17:36 +0100 <tomsmeding> dminuoso: have you tried rm -r ~/.cabal/store/ghc-9.6.6*? :p
2025-11-03 15:15:12 +0100prdak(~Thunderbi@user/prdak) prdak
2025-11-03 15:14:44 +0100 <dminuoso> Is GHC looking for .p_hi files or soemthing along the lines?
2025-11-03 15:14:13 +0100 <dminuoso> What does "installed the profiling libraries" even mean, here?
2025-11-03 15:12:10 +0100 <dminuoso> I just wanted to debug a performance regression, so I tried `--enable-profiling` and cabal is failing to find modules for an internal dependencies: https://paste.tomsmeding.com/23kpMrLR
2025-11-03 15:08:52 +0100prdak(~Thunderbi@user/prdak) (Read error: Connection reset by peer)
2025-11-03 15:05:01 +0100deptype(~deptype@2406:b400:3a:73c2:422:9c14:cc52:da31)
2025-11-03 15:04:48 +0100deptype(~deptype@2406:b400:3a:73c2:c5bd:c4ff:b106:a7ad) (Remote host closed the connection)
2025-11-03 15:03:03 +0100trickard_(~trickard@cpe-52-98-47-163.wireline.com.au)
2025-11-03 15:02:50 +0100trickard_(~trickard@cpe-52-98-47-163.wireline.com.au) (Read error: Connection reset by peer)
2025-11-03 15:01:58 +0100prdak(~Thunderbi@user/prdak) prdak
2025-11-03 15:00:47 +0100 <sshine> Morj: https://www.icann.org/en/contracted-parties/registry-operators/services/reserved-names/two-charact…
2025-11-03 15:00:37 +0100 <sshine> Mroj: it seems that ICANN changed their policy and generally allow two-letter gTLDs that are not ccTLDs.
2025-11-03 14:59:49 +0100 <dminuoso> First domain shall be category.hask.
2025-11-03 14:59:33 +0100 <dminuoso> .hask is available.
2025-11-03 14:59:30 +0100 <haskellbridge> <Morj> I propose a reunification of serbo-croatia, the tld would be an abbreviation of hrvatsko-serbsko
2025-11-03 14:58:56 +0100 <dminuoso> But yeah.
2025-11-03 14:58:28 +0100 <dminuoso> Morj: Well, one of the imperial bags of cash is just bribing someone at ICANN.
2025-11-03 14:57:40 +0100 <haskellbridge> <Morj> But a gtld can't be two letters, right?
2025-11-03 14:57:40 +0100 <dminuoso> Oh and you need to pay an annual fee of 3 lumps of gold.
2025-11-03 14:57:17 +0100 <dminuoso> Morj: gTLDs are a thing! No need for a full country anymore, you just need about 2 imperial bags of cash.