--- Log opened Tue Nov 16 00:00:34 2021
00:26 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Ping timeout: 276 seconds]
00:26 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #bitcoin-core-builds
01:47 < laanwj> strange error, libgcc_s.so.1 is definitely an allowed library
01:48 < laanwj> at least for the bitcoin binaries themselves; it may be that the guix build environment doesn't have it? this would be strange, everything built with gcc will need it unless -static-libgcc linker flag is used
02:51 -!- b10c [uid500648@ilkley.irccloud.com] has quit [Quit: Connection closed for inactivity]
03:39 -!- b10c [uid500648@ilkley.irccloud.com] has joined #bitcoin-core-builds
04:00 < hebasto> the error is for `wayland` package
04:10 -!- jtrag [~jtrag@user/jtrag] has joined #bitcoin-core-builds
04:24 -!- jtrag [~jtrag@user/jtrag] has quit [Read error: Connection reset by peer]
04:26 -!- z9z0b3t1c [z9z0b3t1c@gateway/vpn/protonvpn/z9z0b3t1c] has joined #bitcoin-core-builds
05:20 < laanwj> Running 441 test cases...
05:20 < laanwj> __cxa_thread_call_dtors: dtr 0x801f77850 from unloaded dso, skipping
05:20 < laanwj> fwiw: FreeBSD thread_local problem still exists
05:20 < hebasto> laanwj: thanks for testing
05:20 < hebasto> which FreeBSD version?
05:22 < laanwj> hebasto: 13.0
07:19 < laanwj> maybe to verify GUIX output it'd make sense to do something like "cat guix-build-$(git rev-parse --short=12 HEAD)/output/*/SHA256SUMS.part" instead, the current command hashes both the output files and the SHA256 parts which is kind of overkill :)
07:20 < laanwj> (just noticed after I spammed https://github.com/bitcoin/bitcoin/pull/23511#issuecomment-970372334 )
08:08 < hebasto> iirc, we had some non-determinism in `SHA256SUMS.part` files due to the sorting
08:09 < hebasto> in the past
09:09 < dongcarl> hebasto: Can you point me to the logs?
09:26 < hebasto> dongcarl: sure, give me a couple of minutes
09:32 < hebasto> dongcarl: https://github.com/hebasto/artefacts/blob/master/guix-wayland.log
09:37 < dongcarl> hebasto: Looks like there's a wayland-scanner part which needs to built as native, since it's run as part of the wayland build process?
09:38 < hebasto> as other natively built tools?
09:39 < dongcarl> Right, like how we split out b2 from boost
09:39 < dongcarl> I'm not entirely sure I have the situation right tho
09:39 < hebasto> thanks for a hint! will try it out
09:40 < dongcarl> Perhaps it'd be illuminating to look at other cross-compiles of wayland and see what they do
09:43 -!- tla2k21 [~tla2k21@gateway/tor-sasl/tla2k21] has quit [Ping timeout: 276 seconds]
09:44 -!- tla2k21 [~tla2k21@gateway/tor-sasl/tla2k21] has joined #bitcoin-core-builds
09:44 < hebasto> dongcarl: it seems it requires `--with-host-scanner` configure option
09:44 < hebasto> testing...
11:31 -!- b10c [uid500648@ilkley.irccloud.com] has quit [Quit: Connection closed for inactivity]
12:33 -!- jkczyz [sid419941@lymington.irccloud.com] has quit [Ping timeout: 256 seconds]
12:33 < hebasto> dongcarl: thank you very much! your advice helped to fix that error :)
12:36 -!- jkczyz [sid419941@lymington.irccloud.com] has joined #bitcoin-core-builds
12:39 -!- Eigengrau30 [~Eigengrau@181.160.42.253] has joined #bitcoin-core-builds
12:40 -!- Eigengrau61 [~Eigengrau@181.160.42.253] has joined #bitcoin-core-builds
12:40 -!- Eigengrau30 [~Eigengrau@181.160.42.253] has quit [Client Quit]
12:40 -!- Eigengrau61 [~Eigengrau@181.160.42.253] has quit [Client Quit]
14:03 -!- b10c [uid500648@ilkley.irccloud.com] has joined #bitcoin-core-builds
17:40 -!- b10c [uid500648@ilkley.irccloud.com] has quit [Quit: Connection closed for inactivity]
23:56 -!- z9z0b3t1c [z9z0b3t1c@gateway/vpn/protonvpn/z9z0b3t1c] has quit [Ping timeout: 250 seconds]
--- Log closed Wed Nov 17 00:00:35 2021