--- Log opened Thu Apr 16 00:00:53 2020
02:07 -!- jonatack [~jon@213.152.162.69] has quit [Ping timeout: 258 seconds]
02:09 -!- jonatack [~jon@37.166.74.11] has joined #bitcoin-builds
02:54 -!- jonatack [~jon@37.166.74.11] has quit [Ping timeout: 264 seconds]
02:55 -!- jonatack [~jon@213.152.161.85] has joined #bitcoin-builds
02:55 -!- jonatack [~jon@213.152.161.85] has quit [Client Quit]
02:55 -!- jonatack [~jon@213.152.161.85] has joined #bitcoin-builds
03:06 -!- Lelia24Schmeler [~Lelia24Sc@ns334669.ip-5-196-64.eu] has joined #bitcoin-builds
04:02 < elichai2> Hi, Am I missing something or is this not a valid C++ program? https://github.com/bitcoin/bitcoin/blob/master/configure.ac#L316
04:02 < elichai2> the last line `__attribute__((weak)) // allow for libFuzzer linking`
04:02 < elichai2> https://godbolt.org/z/jEYcCb cc MarcoFalke
04:10 < elichai2> ohh that's because `AC_LANG_PROGRAM` plugs in `int main` right after that, so  the weak attribute is for the main
04:43 -!- jonatack [~jon@213.152.161.85] has quit [Quit: jonatack]
04:51 -!- mol_ [~molly@unaffiliated/molly] has quit [Ping timeout: 260 seconds]
04:56 -!- jonatack [~jon@2a01:e0a:53c:a200:bb54:3be5:c3d0:9ce5] has joined #bitcoin-builds
04:56 < fanquake> hebasto: heh that was a typo, not a question in 18652
04:58 -!- mol [~molly@unaffiliated/molly] has joined #bitcoin-builds
05:03 < hebasto> fanquake: :)
05:05 < hebasto> fanquake: is it safe to drop --enable-glibc-back-compat for gitian builds when minimum glibc version is 2.17 now?
05:06 -!- Lelia24Schmeler [~Lelia24Sc@ns334669.ip-5-196-64.eu] has quit [Ping timeout: 264 seconds]
05:08 < fanquake> hebasto: off the top of my head, I'd say no. Would need to go back and look at everything we're going. I was going to follow up the the memmove memcpy stuff but haven't gotten around to it
05:08 < fanquake> *s/going/doing/
05:10 < hebasto> maybe force --enable-threadlocal is safe?
05:11 < fanquake> There's a lot more going on in glibc compat than what's determined by the minimum required glibc version
05:11 < fanquake> I'd have to go back and re-read the thread for the rationale behind explicitly disabling it with glibc-back-compat before I could comment
09:29 -!- mol_ [~molly@unaffiliated/molly] has joined #bitcoin-builds
09:33 -!- mol [~molly@unaffiliated/molly] has quit [Ping timeout: 256 seconds]
09:36 -!- alko89 [~alko@cpe-85-10-28-138.static.amis.net] has joined #bitcoin-builds
10:09 -!- molz_ [~molly@unaffiliated/molly] has joined #bitcoin-builds
10:12 -!- mol_ [~molly@unaffiliated/molly] has quit [Ping timeout: 256 seconds]
10:13 -!- mol [~molly@unaffiliated/molly] has joined #bitcoin-builds
10:16 -!- molz_ [~molly@unaffiliated/molly] has quit [Ping timeout: 256 seconds]
10:48 -!- luke-jr [~luke-jr@unaffiliated/luke-jr] has joined #bitcoin-builds
11:30 -!- mol [~molly@unaffiliated/molly] has quit [Ping timeout: 256 seconds]
11:37 -!- mol [~molly@unaffiliated/molly] has joined #bitcoin-builds
12:03 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has quit [Quit: jb55]
12:04 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined #bitcoin-builds
13:42 -!- BlueMatt [~BlueMatt@unaffiliated/bluematt] has quit [Quit: Quit]
13:44 -!- BlueMatt [~BlueMatt@unaffiliated/bluematt] has joined #bitcoin-builds
17:24 -!- mol [~molly@unaffiliated/molly] has quit [Ping timeout: 256 seconds]
18:27 -!- mol [~molly@unaffiliated/molly] has joined #bitcoin-builds
20:16 < fanquake> dongcarl: I'm surprised  you didn't announce the release of Guix 1.1.0 in here
20:16 < fanquake> https://guix.gnu.org/blog/2020/gnu-guix-1.1.0-released/
20:16 < fanquake> Will be updating my containers / core-review guides
21:41 -!- mol [~molly@unaffiliated/molly] has quit [Ping timeout: 256 seconds]
23:57 -!- mol [~molly@unaffiliated/molly] has joined #bitcoin-builds
--- Log closed Fri Apr 17 00:00:54 2020