--- Log opened Thu Jun 23 00:00:00 2022 00:14 -!- dongcarl [~dongcarl@pool-108-6-233-95.nycmny.fios.verizon.net] has quit [Quit: Ping timeout (120 seconds)] 00:14 -!- dongcarl [~dongcarl@pool-108-6-233-95.nycmny.fios.verizon.net] has joined #bitcoin-core-builds 00:19 < laanwj> luke-jr: no, not really, it's just that my way of coping with the world is often to imagine just how much worse things could be 00:19 < laanwj> fanquake: will try 00:26 -!- dongcarl [~dongcarl@pool-108-6-233-95.nycmny.fios.verizon.net] has quit [Read error: Connection reset by peer] 00:26 -!- dongcarl [~dongcarl@pool-108-6-233-95.nycmny.fios.verizon.net] has joined #bitcoin-core-builds 00:32 < laanwj> any idea why the warning gets turned into an error in the first place in #25436? 00:32 < gribble> https://github.com/bitcoin/bitcoin/issues/25436 | build: GCC-12 build improvements by fanquake · Pull Request #25436 · bitcoin/bitcoin · GitHub 00:32 < laanwj> we don't build depends with -Werror do we? 00:33 < fanquake> no we don’t 00:33 < laanwj> gcc 12 automatically promotes it to error? 00:35 < fanquake> yea, looks like they’ve expanded array-bounds 00:35 < fanquake> we have a similar workaround in our bdb package iirc 00:36 < fanquake> had to do the same -no-Werror for -fcommon in libdmghfsplus for GCC 10 as well 00:36 < fanquake> these things slowly creep up 00:37 < laanwj> you'd expect for something to become error that gcc devs have to be really sure that it's actually an issue and not a false positive 00:37 < laanwj> right! 00:49 -!- sipsorcery [~sipsorcer@2a02:8084:6180:500::12b] has joined #bitcoin-core-builds 01:09 -!- dongcarl [~dongcarl@pool-108-6-233-95.nycmny.fios.verizon.net] has quit [Quit: Ping timeout (120 seconds)] 01:18 -!- dongcarl [~dongcarl@pool-108-6-233-95.nycmny.fios.verizon.net] has joined #bitcoin-core-builds 01:30 -!- dongcarl [~dongcarl@pool-108-6-233-95.nycmny.fios.verizon.net] has quit [Ping timeout: 272 seconds] 01:36 -!- sipsorcery [~sipsorcer@2a02:8084:6180:500::12b] has quit [Remote host closed the connection] 01:36 -!- sipsorcery [~sipsorcer@2a02:8084:6180:500::12b] has joined #bitcoin-core-builds 02:50 -!- dongcarl [~dongcarl@pool-108-6-233-95.nycmny.fios.verizon.net] has joined #bitcoin-core-builds 03:22 -!- jonatack [~jonatack@user/jonatack] has joined #bitcoin-core-builds 05:45 -!- Guest63 [~Guest63@31.144.149.170] has joined #bitcoin-core-builds 05:45 -!- Guest63 [~Guest63@31.144.149.170] has quit [Client Quit] 05:51 -!- sipsorcery [~sipsorcer@2a02:8084:6180:500::12b] has quit [Ping timeout: 264 seconds] 06:04 -!- sipsorcery [~sipsorcer@2a02:8084:6180:500::12b] has joined #bitcoin-core-builds 06:19 -!- jonatack [~jonatack@user/jonatack] has quit [Quit: Ping timeout (120 seconds)] 09:55 -!- z9z0b3t1_ [~z9z0b3t1c@145.224.65.191] has joined #bitcoin-core-builds 09:58 -!- z9z0b3t1c [z9z0b3t1c@gateway/vpn/protonvpn/z9z0b3t1c] has quit [Ping timeout: 255 seconds] 10:14 -!- belcher [~belcher@user/belcher] has joined #bitcoin-core-builds 10:27 -!- sipsorcery [~sipsorcer@2a02:8084:6180:500::12b] has quit [Ping timeout: 272 seconds] 10:47 -!- sipsorcery [~sipsorcer@2a02:8084:6180:500::12b] has joined #bitcoin-core-builds 10:56 -!- jonatack [~jonatack@user/jonatack] has joined #bitcoin-core-builds 11:30 -!- sipsorcery [~sipsorcer@2a02:8084:6180:500::12b] has quit [Ping timeout: 264 seconds] 11:30 -!- sipsorcery [~sipsorcer@2a02:8084:6180:500::12b] has joined #bitcoin-core-builds 12:26 -!- belcher [~belcher@user/belcher] has quit [Quit: Leaving] 12:45 < hebasto> begging for reviewing of https://github.com/bitcoin-core/crc32c-subtree/pull/5 13:42 -!- jonatack [~jonatack@user/jonatack] has quit [Quit: Ping timeout (120 seconds)] 15:31 -!- sipsorcery [~sipsorcer@2a02:8084:6180:500::12b] has quit [Ping timeout: 272 seconds] 15:53 -!- sipsorcery [~sipsorcer@2a02:8084:6180:500::12b] has joined #bitcoin-core-builds 16:28 -!- sipsorcery [~sipsorcer@2a02:8084:6180:500::12b] has quit [Ping timeout: 244 seconds] 20:08 -!- z9z0b3t1c [~z9z0b3t1c@145.224.66.51] has joined #bitcoin-core-builds 20:10 -!- z9z0b3t1_ [~z9z0b3t1c@145.224.65.191] has quit [Ping timeout: 248 seconds] 20:13 -!- z9z0b3t1_ [~z9z0b3t1c@145.224.65.191] has joined #bitcoin-core-builds 20:15 -!- z9z0b3t1c [~z9z0b3t1c@145.224.66.51] has quit [Ping timeout: 256 seconds] 20:23 -!- z9z0b3t1c [~z9z0b3t1c@145.224.65.191] has joined #bitcoin-core-builds 20:25 -!- z9z0b3t1_ [~z9z0b3t1c@145.224.65.191] has quit [Ping timeout: 248 seconds] 20:26 -!- z9z0b3t1_ [~z9z0b3t1c@145.224.65.191] has joined #bitcoin-core-builds 20:28 -!- z9z0b3t1c [~z9z0b3t1c@145.224.65.191] has quit [Ping timeout: 244 seconds] 20:33 -!- z9z0b3t1c [~z9z0b3t1c@145.224.65.157] has joined #bitcoin-core-builds 20:35 -!- z9z0b3t1_ [~z9z0b3t1c@145.224.65.191] has quit [Ping timeout: 248 seconds] 21:53 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Remote host closed the connection] 21:53 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #bitcoin-core-builds 22:15 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Write error: Connection reset by peer] 22:16 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #bitcoin-core-builds 23:59 -!- sipsorcery [~sipsorcer@2a02:8084:6180:500::12b] has joined #bitcoin-core-builds --- Log closed Fri Jun 24 00:00:01 2022