--- Log opened Mon Jun 14 00:00:37 2021
01:29 -!- belcher_ is now known as belcher
02:05 -!- greypw [~greypw@grey.pw] has joined #bitcoin-core-builds
05:07 -!- ghost43_ [~ghost43@gateway/tor-sasl/ghost43] has joined #bitcoin-core-builds
05:07 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Remote host closed the connection]
06:21 < laanwj> dongcarl: fyi #21203 is mentioned as outstanding in #21145 but it is closed
07:28 < real_or_random> I'd be happy to get some review on https://github.com/bitcoin-core/secp256k1/pull/944 which is autotools stuff, and the people here are probably more knowledgeable than the usual secp crowd
11:40 < laanwj> ok this is pretty bad i guess: https://github.com/bitcoin/bitcoin/pull/22244  not sure how to handle these new glibc symbols
11:41 < laanwj> for guix, would it be possible to compile against the right glibc version for every platform and avoid the whole issue?
11:45 < dongcarl> laanwj: urgh I remember we used to do this but changed it at some point, not sure I remember the reason, will dig
11:53 < laanwj> i don't get why getrandom is there, we only use it through syscall(SYS_getrandom...) at most
11:54 < sipa> could c++ be compiling std::random_device into getrandom() calls
11:57 < dongcarl> laanwj: Okay found it, we were previously pinned to 2.27, but https://github.com/bitcoin/bitcoin/pull/21255/files required that we have at least glibc 2.28, so I bumped it to 2.31 in https://github.com/bitcoin/bitcoin/commit/c33b199456e57d83c21eacd36d3c56d0a123b0d0
11:57 < laanwj> getrandom used in one place, let me get symbols to see where
12:00 < laanwj> dongcarl: according to the symbol check, the glibc for x86_64 is 2.2.5, that sounds really ancient?
12:00 < laanwj> e.g. the ARCH_MIN_GLIBC_VER table, is this correct at all?
12:05 < laanwj> getrandom is used in   arc4_stir at evutil_rand.c:?    (so in libevent dependency)
12:06 < sipa> oh
12:11 < laanwj> i can't find where fcntl64 is used at all, no mentions of it in the objdump
12:12 < laanwj> possibly there is a data reference, let's check the relocations...
12:16 < laanwj> yes, that's it, it must be referenced as a pointer somewhere
12:25 < laanwj> it's referenced by sqlite
12:26 < laanwj> so except for log/pow/exp all the symbols come from dependencies
13:48 < laanwj> e.g. the ARCH_MIN_GLIBC_VER table, is this correct at all? <- no, it isn't; the values in there aren't used if they're smaller than what is in MAX_VERSIONS['GLIBC'], so 2.17
17:48 -!- l3kk0 [~l3kk0@c-73-22-213-40.hsd1.il.comcast.net] has joined #bitcoin-core-builds
21:34 -!- belcher_ [~belcher@user/belcher] has joined #bitcoin-core-builds
21:37 -!- belcher [~belcher@user/belcher] has quit [Ping timeout: 252 seconds]
22:48 -!- belcher_ [~belcher@user/belcher] has quit [Quit: Leaving]
--- Log closed Tue Jun 15 00:00:38 2021