--- Log opened Sun Oct 03 00:00:25 2021
04:03 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Remote host closed the connection]
04:03 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #bitcoin-core-builds
06:48 < laanwj> dynamically linked risc-v 64 bit binaries go from 47M in total to 36M ... bitcoin-wallet is the largest relative change it goes from 3.3M to 1.3M, less than half
06:48 < laanwj> (stripped sizes)
12:54 < laanwj> curiously, the size reduction of bitcoin-qt is least, although it is the largest binary it only goes from 13M to 12M, maybe because large part of it is resources instead of code? (mind, this is a dynamic build so doesn't include qt itself)
16:09 -!- gribble [~gribble@bitcoin/bot/gribble] has joined #bitcoin-core-builds
16:17 -!- belcher_ [~belcher@user/belcher] has quit [Read error: Connection reset by peer]
16:35 -!- belcher_ [~belcher@user/belcher] has joined #bitcoin-core-builds
21:51 -!- luke-jr [~luke-jr@user/luke-jr] has quit [Read error: Connection reset by peer]
21:55 -!- luke-jr [~luke-jr@user/luke-jr] has joined #bitcoin-core-builds
22:22 < luke-jr> got the actual builds compolete, but the signing step is failing
22:22 < luke-jr> Failed to open file: codesignatures/win/bitcoin-22.0rc1-win64-setup-unsigned.exe.pem
22:46 < luke-jr> the full path appears to be /home/ubuntu/build/signature/win/bitcoin-22.0-win64-setup-unsigned.exe.pem
22:46 < luke-jr> not sure why it's looking for it in the wrong place?
23:20 < fanquake> wumpus: discussed with Carl, and turns out using LTO in Guix could be as simple as using the gcc-* wrappers for ar, ranlib. As that will add the necessary --plugin arguments.
23:20 < fanquake> Just finished a GUIX build, with LTO, for x86_64-linux-gnu, and it appears to work.
23:48 < achow101> luke-jr: sounds like you're building the wrong tag?
--- Log closed Mon Oct 04 00:00:26 2021