--- Log opened Fri Jun 25 00:00:48 2021
01:22 -!- belcher_ is now known as belcher
03:30 -!- robertspigler [~robertspi@2001:470:69fc:105::2d53] has joined #bitcoin-core-builds
08:07 -!- gribble [~gribble@bitcoin/bot/gribble] has quit [Read error: Connection reset by peer]
08:12 -!- gribble [~gribble@bitcoin/bot/gribble] has joined #bitcoin-core-builds
12:00 < dongcarl> Update: still working on the glibc stuff, we're likely going to do 2.24 for aarch64 + ppcle, 2.27 for riscv64, and 2.17 (with a few light backported patches) for everything else
12:02 < sipa> dongcarl: any reason not to do 2.24 for everything (except riscv64, perhaps?), if it doesn't result in runtime dependency on higher than 2.17?
12:03 < sipa> (or is it not the case that the runtime dependency stays at 2.17?)
13:33 < dongcarl> Hmmm, well looking at the objdump for 2.24, there are many symbols which are 2.18 or higher. My naive understanding is that although we might not use these functions now, we or our dependencies may start using them and it would cause problems... So I tend to think we should just use "the lowest one we can get away with without excessive patch
13:33 < dongcarl> backporting," but I'm definitely not set in that opinion
14:43 < sipa> i agree the risk is pretty low, given how little the glibc headers do functionally
14:43 < sipa> but 2.17 is very old (2012)
16:00 -!- belcher_ [~belcher@user/belcher] has joined #bitcoin-core-builds
16:02 -!- belcher [~belcher@user/belcher] has quit [Ping timeout: 256 seconds]
17:45 < fanquake> dongcarl: what is your definition of "excessive patch backporting"
17:45 < fanquake> Note that 2.17 was basically only picked because of CENTOS 7 support. However I can't imagine we are actually going to support that until 2024
17:49 < sipa> 2.24 is from 2016; even if accisentally we end up with a dependency on that, it's not a disaster...
17:51 < dongcarl> Right now, this works: https://github.com/dongcarl/bitcoin/commit/d576421706608d94302a321364e42fb0f627c3e9
17:52 < dongcarl> Basically only "glibc-2.17-_obstack_compat-initialize.patch" and "glibc-2.17-fix-libgcc_s_resume-issue.patch" are unique backported patches for 2.17
17:53 < dongcarl> I don't have strong opinions on what version to choose, and can adapt this to use 2.24 across all if that's what everyone prefers :-)
17:53 < dongcarl> I know that CentOS 7 is still on 2.17, but not sure that matters too much
17:55 < dongcarl> "glibc-ldd-x86_64.patch" "glibc-versioned-locpath.patch" and "glibc-2.17-supported-locales.patch" are Guix-specific patches for glibc that's applied to all Guix glibc packages
18:46 -!- copumpkin [~woohoo@user/copumpkin] has quit [Quit: Textual IRC Client: www.textualapp.com]
19:17 -!- copumpkin [~woohoo@user/copumpkin] has joined #bitcoin-core-builds
19:20 -!- reallll [~belcher@user/belcher] has joined #bitcoin-core-builds
19:22 -!- belcher_ [~belcher@user/belcher] has quit [Ping timeout: 272 seconds]
23:20 -!- belcher_ [~belcher@user/belcher] has joined #bitcoin-core-builds
23:23 -!- reallll [~belcher@user/belcher] has quit [Ping timeout: 258 seconds]
--- Log closed Sat Jun 26 00:00:49 2021