--- Log opened Mon Jul 08 00:00:04 2019 00:15 -!- Cruz87Anderson [~Cruz87And@ns334669.ip-5-196-64.eu] has joined #bitcoin-builds 05:23 < fanquake> dongcarl 🎉 05:24 < dongcarl> fanquake: thanks ❤️ 05:25 < dongcarl> Will take a sweep over the PRs today 05:25 < dongcarl> Also, will read nothingmuch’s messages 05:25 < fanquake> All good 07:20 -!- hebasto [~hebasto@95.164.65.194] has joined #bitcoin-builds 07:41 < dongcarl> sweeping... fanquake lmk if there are things that needs urgent attention 07:47 < fanquake> dongcarl nothing too urgent. I reached out to Cory, think he'll be having a look at some build stuff, as well as the avx pr soonish as well. 07:47 < dongcarl> Sounds good, I acked the expat one, good to speed up builds 07:47 < dongcarl> Only `libXext` remaining, and that's the tricky one 07:48 < dongcarl> I'll take a look this week 07:48 < fanquake> Yea I was going to dive into that as well. Try and figure out how qt is using it, and then how we might be using it. 07:49 < dongcarl> Sounds good, I think I posted some logs here a while back about how it was affected. Lmk if you have more clues. 08:03 < dongcarl> nothingmuch: Oh I don't think you need to worry about `CROSS_` envvars if you're doing native Guix packages 08:03 < dongcarl> Literally `guix build --target=aarch64-linux-gnu my-zlib` should work 08:04 * dongcarl is excited about the progress 08:05 < dongcarl> TheCharlatan: wondering if you'll join the party soon? 08:49 -!- Cruz87Anderson [~Cruz87And@ns334669.ip-5-196-64.eu] has quit [Ping timeout: 248 seconds] 09:49 < nothingmuch> dongcarl: for zlib's custom configure script i did 09:50 < nothingmuch> otherwise it fails to find sys/types.h, or stdio.h, and tries to link with native glib 09:50 < nothingmuch> c 09:51 < dongcarl> nothingmuch: Even with `--target`? 09:52 -!- MarcoFalke [~none@198.12.116.246] has joined #bitcoin-builds 09:56 < nothingmuch> dongcarl: i tried that on friday and i don't remember what problem i ran into, IIRC i was having trouble making sure to use your cross toolchains 09:57 < nothingmuch> i'll try it again now that i got it working according to how build.sh works 09:57 < dongcarl> nothingmuch: Don't use my cross-toolchain if you're using native guix packages 09:57 < dongcarl> when you're using native guix packages, don't use any of my hacks 09:57 < dongcarl> no CROSS_ env vars 09:57 < dongcarl> none of my cross toolchains 09:57 < dongcarl> Guix knows how to do them automatically 09:58 < nothingmuch> i'll have another go in a few hrs 09:59 < dongcarl> nothingmuch: No worries, we can also pair-program sometime soon if you want 10:00 < nothingmuch> sure, i'd be happy to, i need to go afk for now but i'll let you know when i'm back 10:00 < dongcarl> nothingmuch: kk 10:00 < nothingmuch> and if not today then i'm always up for it, i work much better in that setting 10:00 < dongcarl> nothingmuch: Yeah I'll hit you up 10:57 -!- hebasto [~hebasto@95.164.65.194] has quit [Remote host closed the connection] 11:57 < nothingmuch> dongcarl: can you explain a bit more about the motiviation & consideratoins for your xtoolchains work? e.g. the specific glibc version, etc? 11:57 < dongcarl> nothingmuch: Yeah sure 11:57 < dongcarl> the specific glibc version is because we maintain glibc back compat 11:57 < dongcarl> and we maintain back compat for glibcs all the way up to 2.27 11:57 < dongcarl> because that is what Ubuntu bionic is on, and that's what Gitian is on 11:58 < dongcarl> But Guix's default glibc is 2.28 11:58 < dongcarl> So we pin it to 2.27 11:58 < dongcarl> does that make sense? 11:58 < nothingmuch> yes 11:59 < dongcarl> For the rest of the versions... We needed kernel headers 4.15 11:59 < dongcarl> For the rest of the versions... We needed kernel headers > 4.15 to support riscv 11:59 < dongcarl> but 4.15 isn't LTS 11:59 < dongcarl> 4.19 is LTS 11:59 < dongcarl> so we use that cuz it works 11:59 < nothingmuch> any way in which libc is relevant to the deps? if 2.28 is used for the native deps that's obviously not an issue, and everything else should only matter when linking the binaries from the bitcoin build itself, right? 12:00 < dongcarl> nothingmuch: Oh you mean for depends? 12:00 < nothingmuch> yeah, like in particular if the wrong headers get used in a std --target build 12:01 < dongcarl> Yeah, perhaps that's not relevant, but it doesn't hurt, right? What do you mean about the headers? 12:04 < nothingmuch> so suppose i have pkg x as a pretty vanilla guix package, and i build it with --target and produce a static .a for linking later in the bitcoin build, that would depend on libc symbols as set up by the std headers provided by guix, which should be 2.28 12:05 -!- hebasto [~hebasto@95.164.65.194] has joined #bitcoin-builds 12:06 < nothingmuch> i expect this isn't an issue in practice but i'm not sure what the actual differences betwen 2.2{7,8} are 12:08 < dongcarl> nothingmuch: Don't worry about that for now, I might PR a guix feature that allows a specification string for the toolchain, e.g. --target=aarch64-linux-gnu:2.27:4.19 12:09 < dongcarl> Only thing that'll break is `check-symbols`, which we can deal with later 12:12 < nothingmuch> ah, good point re check-symbols 12:26 < nothingmuch> afk again for a bit more but after that i should be back and have time for this 12:27 < dongcarl> nothingmuch: No worries at all 12:29 -!- hebasto [~hebasto@95.164.65.194] has quit [Remote host closed the connection] 14:07 < dongcarl> Any thoughts on using signify for Guix builds in the future? 14:07 < dongcarl> It's so easy to use... 14:07 < dongcarl> https://news.ycombinator.com/item?id=9709843 15:14 < jb55> looks great 18:29 -!- ryanofsky_ [~russ@jumpy.yanofsky.org] has joined #bitcoin-builds 18:30 -!- ryanofsky [~russ@jumpy.yanofsky.org] has quit [Remote host closed the connection] 20:34 -!- hebasto [~hebasto@95.164.65.194] has joined #bitcoin-builds --- Log closed Tue Jul 09 00:00:05 2019