Newest at the top
| 2024-11-01 14:36:28 +0100 | <merijn> | C-sources get included, `includes` does not (since it might contain generated/system/whatever stuff) |
| 2024-11-01 14:36:05 +0100 | <merijn> | mauke: https://github.com/merijn/Belewitte/blob/ed95965077ee0a55c9a206b75445ddf93723916b/benchmark-analys… |
| 2024-11-01 14:35:21 +0100 | <merijn> | mauke: My C shipping projects explicitly list headers under `extra-source-files` |
| 2024-11-01 14:35:06 +0100 | <merijn> | mauke: Yeah, I think the problem is that `includes` doesn't include your headers in the sdist |
| 2024-11-01 14:34:29 +0100 | <mauke> | I wish it would stop building an sdist. all I want is an executable |
| 2024-11-01 14:34:05 +0100 | <merijn> | mauke: So most likely your sdist is fucked and not including the header |
| 2024-11-01 14:33:53 +0100 | <merijn> | mauke: First clue is: "build works, install fails". install *always* builds an sdist *first* and THEN installs from that. To protect against broken sdists |
| 2024-11-01 14:33:48 +0100 | <mauke> | merijn: https://paste.tomsmeding.com/uNvsLOb0 |
| 2024-11-01 14:33:24 +0100 | k_hachig_ | (~k_hachig@2607:fea8:351d:ef0:901a:fefb:e87f:78b3) k_hachig |
| 2024-11-01 14:33:05 +0100 | <merijn> | But lemme check the cabal file first |
| 2024-11-01 14:32:57 +0100 | <merijn> | I think I know :D |
| 2024-11-01 14:32:52 +0100 | <merijn> | ooh |
| 2024-11-01 14:32:44 +0100 | <mauke> | but I can't get it to tell me wtf it's doing, so my plan is to configure a fake compiler that just dumps what's going on |
| 2024-11-01 14:32:33 +0100 | <merijn> | mauke: Is the cabal file public? |
| 2024-11-01 14:32:20 +0100 | <mauke> | oh, the compiler is fine |
| 2024-11-01 14:32:09 +0100 | <merijn> | mauke: Ah, that sounds more like wrong include dirs than wrong compiler, no? |
| 2024-11-01 14:32:01 +0100 | <mauke> | the fun part is that it only happens on 'cabal install'. 'cabal build' is fine with it |
| 2024-11-01 14:31:46 +0100 | <mauke> | Missing (or bad) header file: wcalc.h |
| 2024-11-01 14:31:35 +0100 | <merijn> | mauke: Error? And I assume you mean actual C and not secretly C++? |
| 2024-11-01 14:31:13 +0100 | <yushyin> | 4345 is the missing deps on foreign libs error, no? this is one of the more murky errors |
| 2024-11-01 14:31:05 +0100 | <mauke> | and I can't figure out what |
| 2024-11-01 14:31:01 +0100 | <mauke> | no, cabal is doing something stupid |
| 2024-11-01 14:30:58 +0100 | <merijn> | I think there was either a config file or GHC flag to tell it to use something else |
| 2024-11-01 14:30:47 +0100 | <merijn> | mauke: Cabal just invokes GHC on C files, which determines what C compiler to call |
| 2024-11-01 14:30:33 +0100 | <merijn> | mauke: You can't tell cabal, you need to tell GHC |
| 2024-11-01 14:30:08 +0100 | <mauke> | how do I tell cabal what C compiler to use? |
| 2024-11-01 14:27:32 +0100 | <merijn> | Step one is *having* unique codes, step two is documenting them ;) |
| 2024-11-01 14:27:20 +0100 | <merijn> | mauke: Work in progress ;) |
| 2024-11-01 14:26:48 +0100 | <merijn> | nice :) |
| 2024-11-01 14:26:48 +0100 | <mauke> | 1 whole errors |
| 2024-11-01 14:26:43 +0100 | <mauke> | hah: "So far, 1 Cabal errors and warnings are documented here." |
| 2024-11-01 14:26:27 +0100 | <merijn> | I see some CABAL-xxx codes there |
| 2024-11-01 14:26:11 +0100 | <mauke> | nothing there either |
| 2024-11-01 14:25:12 +0100 | <yushyin> | https://errors.haskell.org/cabal/ |
| 2024-11-01 14:25:04 +0100 | <merijn> | mauke: https://discourse.haskell.org/t/announcing-the-haskell-error-index/5195 |
| 2024-11-01 14:25:01 +0100 | <yushyin> | the error message index website? yes, but it is incomplete |
| 2024-11-01 14:24:47 +0100 | <merijn> | I'm assuming cabal codes are extension of that |
| 2024-11-01 14:24:29 +0100 | <merijn> | mauke: Hecate was leading something on error codes in GHC |
| 2024-11-01 14:24:17 +0100 | <mauke> | nothing in the manual, nothing on the website, nothing in a google search |
| 2024-11-01 14:24:02 +0100 | <mauke> | merijn: I'll take that as a "no" |
| 2024-11-01 14:23:57 +0100 | Square2 | (~Square4@user/square) Square |
| 2024-11-01 14:23:30 +0100 | <merijn> | but if you run hackage you get the benefits of hyperlinked browsable docs for internal libs for free |
| 2024-11-01 14:23:10 +0100 | <merijn> | Square: I think it can use "dumb" disk repos too so you could have a shared network filesystem or something and use that |
| 2024-11-01 14:22:03 +0100 | slack1256 | (~slack1256@2803:c600:5111:8696:d97c:cbc8:139:bdb3) (Ping timeout: 244 seconds) |
| 2024-11-01 14:21:41 +0100 | <Square> | is available* |
| 2024-11-01 14:21:40 +0100 | Xe | (~cadey@perl/impostor/xe) Xe |
| 2024-11-01 14:21:30 +0100 | <Square> | merijn, yeah. Seems to be it. I was thinking there were different options. But excellent if hackage availble. |
| 2024-11-01 14:21:15 +0100 | mulk | (~mulk@pd95146e9.dip0.t-ipconnect.de) mulk |
| 2024-11-01 14:20:10 +0100 | slac68956 | (~slack1256@179.60.70.224) slack1256 |
| 2024-11-01 14:19:46 +0100 | <merijn> | Square: You can set up your own internal Hackage and Hoogle and have cabal fallback to the regular public one (if desired) |