Newest at the top
| 2025-07-04 20:24:03 +0200 | j1n37 | (~j1n37@user/j1n37) (Read error: Connection reset by peer) |
| 2025-07-04 20:19:43 +0200 | Ikosit | (~Ikosit@user/ikosit) Ikosit |
| 2025-07-04 20:17:59 +0200 | tzh | (~tzh@c-76-115-131-146.hsd1.or.comcast.net) |
| 2025-07-04 20:15:36 +0200 | j1n37 | (~j1n37@user/j1n37) j1n37 |
| 2025-07-04 20:15:32 +0200 | <int-e> | (It's just `cabal build` for me because I'm testing this in after `cabal unpack HsOpenSSL` because that makes it easier to actually replicate the executed commands.) |
| 2025-07-04 20:13:51 +0200 | <int-e> | That said, you also wanted to inject -optc-w and the output of cabal build --ghc-options=-optc-w is indeed much more to the point. |
| 2025-07-04 20:12:52 +0200 | rat-with-hat | (~rat-with-@24-113-114-97.wavecable.com) (Remote host closed the connection) |
| 2025-07-04 20:12:20 +0200 | <ii8> | Oh I see, that makes more sense |
| 2025-07-04 20:12:13 +0200 | euphores | (~SASL_euph@user/euphores) euphores |
| 2025-07-04 20:11:39 +0200 | Ikosit | (~Ikosit@user/ikosit) (Client Quit) |
| 2025-07-04 20:11:35 +0200 | j1n37 | (~j1n37@user/j1n37) (Read error: Connection reset by peer) |
| 2025-07-04 20:09:58 +0200 | caubert | (~caubert@user/caubert) caubert |
| 2025-07-04 20:09:44 +0200 | j1n37 | (~j1n37@user/j1n37) j1n37 |
| 2025-07-04 20:09:29 +0200 | Ikosit | (~Ikosit@user/ikosit) Ikosit |
| 2025-07-04 20:09:09 +0200 | Ikosit | (~Ikosit@user/ikosit) (Quit: The Lounge - https://thelounge.chat) |
| 2025-07-04 20:08:41 +0200 | <int-e> | (both clang and gcc just say error: *instead of* warning: in this case) |
| 2025-07-04 20:08:03 +0200 | <int-e> | It's also worth noting that when using -Werror, the C compilers don't use the word "warning" at all. |
| 2025-07-04 20:07:46 +0200 | weary-traveler | (~user@user/user363627) (Remote host closed the connection) |
| 2025-07-04 20:06:56 +0200 | <int-e> | But... no, compilation isn't failing because the C compiler produced a warning. There's an error to find in there too. |
| 2025-07-04 20:06:31 +0200 | <int-e> | It's awful to read. |
| 2025-07-04 20:06:30 +0200 | j1n37- | (~j1n37@user/j1n37) (Read error: Connection reset by peer) |
| 2025-07-04 20:06:25 +0200 | <int-e> | ...added by GHC, which is redundant when the C compiler also has one... |
| 2025-07-04 20:06:19 +0200 | <int-e> | Obviously something terrible *is* going on here... GHC is, I think, parsing the compiler output to extract location information, and then builds its own *error* message with that location information, and the original compiler output. So you get GHC saying <file>:line:char: error:, then whatever the C compiler actually output minus the parsed location, and then a visual indicator of the location... |
| 2025-07-04 20:06:13 +0200 | j1n37 | (~j1n37@user/j1n37) (Ping timeout: 276 seconds) |
| 2025-07-04 20:06:09 +0200 | caubert | (~caubert@user/caubert) (Ping timeout: 244 seconds) |
| 2025-07-04 20:05:06 +0200 | j1n37- | (~j1n37@user/j1n37) j1n37 |
| 2025-07-04 20:05:03 +0200 | Frostillicus | (~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net) (Ping timeout: 252 seconds) |
| 2025-07-04 20:04:39 +0200 | jmcantrell | (~weechat@user/jmcantrell) (Ping timeout: 260 seconds) |
| 2025-07-04 20:01:46 +0200 | tmciver | (~tim@syn-198-255-177-240.res.spectrum.com) tmciver |
| 2025-07-04 19:59:43 +0200 | <int-e> | (for me) |
| 2025-07-04 19:59:24 +0200 | jmcantrell | (~weechat@user/jmcantrell) jmcantrell |
| 2025-07-04 19:59:03 +0200 | <int-e> | the first one is error: passing argument 2 of ‘RSA_get0_crt_params’ from incompatible pointer type [...] |
| 2025-07-04 19:58:24 +0200 | <geekosaur> | * a lot of |
| 2025-07-04 19:58:17 +0200 | <geekosaur> | fwiw I got of "deprecated in OpenSSL 3.0" warnings but didn't see any real errors |
| 2025-07-04 19:57:24 +0200 | euphores | (~SASL_euph@user/euphores) (Quit: Leaving.) |
| 2025-07-04 19:56:57 +0200 | <int-e> | ii8: Anyway. At least for me, there are quite a few actual errors, and I'm pretty sure you'll find at least one too if you keep looking . |
| 2025-07-04 19:55:42 +0200 | prdak | (~Thunderbi@user/prdak) (Ping timeout: 252 seconds) |
| 2025-07-04 19:54:32 +0200 | j1n37 | (~j1n37@user/j1n37) j1n37 |
| 2025-07-04 19:51:37 +0200 | <geekosaur> | dammit, looks like it's one of those flags not supported in project files. please file a Cabal bug |
| 2025-07-04 19:51:02 +0200 | prdak | (~Thunderbi@user/prdak) prdak |
| 2025-07-04 19:50:52 +0200 | <int-e> | and far less duplication |
| 2025-07-04 19:49:55 +0200 | sord937 | (~sord937@gateway/tor-sasl/sord937) (Quit: sord937) |
| 2025-07-04 19:48:50 +0200 | j1n37 | (~j1n37@user/j1n37) (Read error: Connection reset by peer) |
| 2025-07-04 19:48:49 +0200 | <int-e> | GHC does some weird rewriting of the C compiler output too. https://paste.tomsmeding.com/uMEVzvs4 ... note that the GCC output (at the bottom) has no weird error: [newline] warning: stuff |
| 2025-07-04 19:48:46 +0200 | Frostillicus | (~Frostilli@pool-71-174-119-69.bstnma.fios.verizon.net) |
| 2025-07-04 19:46:34 +0200 | merijn | (~merijn@host-vr.cgnat-g.v4.dfn.nl) merijn |
| 2025-07-04 19:46:14 +0200 | j1n37 | (~j1n37@user/j1n37) j1n37 |
| 2025-07-04 19:45:48 +0200 | j1n37 | (~j1n37@user/j1n37) (Read error: Connection reset by peer) |
| 2025-07-04 19:45:27 +0200 | j1n37 | (~j1n37@user/j1n37) j1n37 |
| 2025-07-04 19:44:54 +0200 | Leary | (~Leary@user/Leary/x-0910699) Leary |