--- Log opened Wed Mar 23 00:00:34 2022
00:03 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Remote host closed the connection]
00:04 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #bitcoin-core-pr-reviews
00:04 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c3e:c153:e75f:59c3] has quit [Ping timeout: 252 seconds]
00:08 -!- franzo [~franzo@103.129.2.167] has joined #bitcoin-core-pr-reviews
00:18 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c3e:c153:e75f:59c3] has joined #bitcoin-core-pr-reviews
00:18 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Remote host closed the connection]
00:19 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #bitcoin-core-pr-reviews
00:26 -!- hashfunc569 [~user@2601:5c0:c280:7090:78e9:5f82:1899:8c96] has quit [Ping timeout: 240 seconds]
00:53 -!- franzo [~franzo@103.129.2.167] has quit [Quit: Client closed]
01:04 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Remote host closed the connection]
01:05 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #bitcoin-core-pr-reviews
01:16 -!- lucasdcf_ [~lucasdcf@2804:431:c7d8:eb7d:f0e4:e054:c2d:c68f] has quit [Read error: Connection reset by peer]
01:17 -!- lucasdcf_ [~lucasdcf@2804:431:c7d8:eb7d:f0e4:e054:c2d:c68f] has joined #bitcoin-core-pr-reviews
01:20 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c3e:c153:e75f:59c3] has quit [Ping timeout: 268 seconds]
01:22 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Remote host closed the connection]
01:23 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #bitcoin-core-pr-reviews
01:34 -!- brunoerg [~brunoerg@187.183.43.40] has joined #bitcoin-core-pr-reviews
02:00 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Remote host closed the connection]
02:01 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #bitcoin-core-pr-reviews
02:05 -!- lukedashjr [~luke-jr@user/luke-jr] has joined #bitcoin-core-pr-reviews
02:06 -!- lukedashjr [~luke-jr@user/luke-jr] has quit [Read error: Connection reset by peer]
02:08 -!- luke-jr [~luke-jr@user/luke-jr] has quit [Ping timeout: 256 seconds]
02:18 -!- luke-jr [~luke-jr@user/luke-jr] has joined #bitcoin-core-pr-reviews
02:21 -!- luke-jr [~luke-jr@user/luke-jr] has quit [Read error: Connection reset by peer]
02:24 -!- ghost43_ [~ghost43@gateway/tor-sasl/ghost43] has joined #bitcoin-core-pr-reviews
02:25 -!- luke-jr [~luke-jr@user/luke-jr] has joined #bitcoin-core-pr-reviews
02:27 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Ping timeout: 240 seconds]
02:36 -!- brunoerg [~brunoerg@187.183.43.40] has quit [Ping timeout: 240 seconds]
02:51 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c3e:c153:e75f:59c3] has joined #bitcoin-core-pr-reviews
02:53 -!- luke-jr [~luke-jr@user/luke-jr] has quit [Read error: Connection reset by peer]
02:54 -!- lucasdcf_ [~lucasdcf@2804:431:c7d8:eb7d:f0e4:e054:c2d:c68f] has quit [Read error: Connection reset by peer]
02:55 -!- lucasdcf_ [~lucasdcf@2804:431:c7d8:eb7d:f0e4:e054:c2d:c68f] has joined #bitcoin-core-pr-reviews
02:58 -!- luke-jr [~luke-jr@user/luke-jr] has joined #bitcoin-core-pr-reviews
03:01 -!- lukedashjr [~luke-jr@user/luke-jr] has joined #bitcoin-core-pr-reviews
03:03 -!- luke-jr- [~luke-jr@user/luke-jr] has joined #bitcoin-core-pr-reviews
03:03 -!- luke-jr [~luke-jr@user/luke-jr] has quit [Ping timeout: 256 seconds]
03:04 -!- lucasdcf_ [~lucasdcf@2804:431:c7d8:eb7d:f0e4:e054:c2d:c68f] has quit [Read error: Connection reset by peer]
03:05 -!- lucasdcf_ [~lucasdcf@2804:431:c7d8:eb7d:f0e4:e054:c2d:c68f] has joined #bitcoin-core-pr-reviews
03:05 -!- luke-jr- is now known as luke-jr
03:06 -!- lukedashjr [~luke-jr@user/luke-jr] has quit [Ping timeout: 260 seconds]
03:11 -!- franzo [~franzo@103.129.2.170] has joined #bitcoin-core-pr-reviews
03:13 -!- lukedashjr [~luke-jr@user/luke-jr] has joined #bitcoin-core-pr-reviews
03:14 -!- luke-jr [~luke-jr@user/luke-jr] has quit [Ping timeout: 260 seconds]
03:15 -!- lukedashjr [~luke-jr@user/luke-jr] has quit [Read error: Connection reset by peer]
03:17 -!- luke-jr [~luke-jr@user/luke-jr] has joined #bitcoin-core-pr-reviews
03:18 -!- luke-jr [~luke-jr@user/luke-jr] has quit [Read error: Connection reset by peer]
03:19 -!- lucasdcf_ [~lucasdcf@2804:431:c7d8:eb7d:f0e4:e054:c2d:c68f] has quit [Read error: Connection reset by peer]
03:20 -!- lucasdcf_ [~lucasdcf@2804:431:c7d8:eb7d:f0e4:e054:c2d:c68f] has joined #bitcoin-core-pr-reviews
03:20 -!- ghost43_ [~ghost43@gateway/tor-sasl/ghost43] has quit [Remote host closed the connection]
03:21 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #bitcoin-core-pr-reviews
03:21 -!- luke-jr [~luke-jr@user/luke-jr] has joined #bitcoin-core-pr-reviews
03:30 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Remote host closed the connection]
03:32 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #bitcoin-core-pr-reviews
03:36 -!- yashraj [~yashraj@171.50.232.194] has joined #bitcoin-core-pr-reviews
03:40 -!- franzo [~franzo@103.129.2.170] has quit [Quit: Client closed]
03:53 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c3e:c153:e75f:59c3] has quit [Ping timeout: 252 seconds]
03:58 -!- luke-jr [~luke-jr@user/luke-jr] has quit [Read error: Connection reset by peer]
04:01 -!- luke-jr [~luke-jr@user/luke-jr] has joined #bitcoin-core-pr-reviews
04:08 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Remote host closed the connection]
04:09 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #bitcoin-core-pr-reviews
04:09 -!- luke-jr [~luke-jr@user/luke-jr] has quit [Read error: Connection reset by peer]
04:09 -!- brunoerg [~brunoerg@187.183.43.40] has joined #bitcoin-core-pr-reviews
04:10 -!- ghost43_ [~ghost43@gateway/tor-sasl/ghost43] has joined #bitcoin-core-pr-reviews
04:10 -!- luke-jr [~luke-jr@user/luke-jr] has joined #bitcoin-core-pr-reviews
04:11 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Remote host closed the connection]
04:13 -!- luke-jr [~luke-jr@user/luke-jr] has quit [Read error: Connection reset by peer]
04:16 -!- luke-jr [~luke-jr@user/luke-jr] has joined #bitcoin-core-pr-reviews
04:16 -!- luke-jr [~luke-jr@user/luke-jr] has quit [Read error: Connection reset by peer]
04:18 -!- luke-jr [~luke-jr@user/luke-jr] has joined #bitcoin-core-pr-reviews
04:21 -!- luke-jr [~luke-jr@user/luke-jr] has quit [Client Quit]
04:22 -!- luke-jr [~luke-jr@user/luke-jr] has joined #bitcoin-core-pr-reviews
04:25 -!- lukedashjr [~luke-jr@user/luke-jr] has joined #bitcoin-core-pr-reviews
04:28 -!- luke-jr [~luke-jr@user/luke-jr] has quit [Ping timeout: 250 seconds]
04:28 -!- luke-jr- [~luke-jr@user/luke-jr] has joined #bitcoin-core-pr-reviews
04:30 -!- luke-jr- [~luke-jr@user/luke-jr] has quit [Read error: Connection reset by peer]
04:30 -!- lukedashjr [~luke-jr@user/luke-jr] has quit [Ping timeout: 260 seconds]
04:31 -!- luke-jr [~luke-jr@user/luke-jr] has joined #bitcoin-core-pr-reviews
05:05 -!- ayush933 [~ayush933@49.37.45.4] has joined #bitcoin-core-pr-reviews
05:08 -!- yashraj [~yashraj@171.50.232.194] has quit [Remote host closed the connection]
05:09 -!- ayush933 [~ayush933@49.37.45.4] has quit [Client Quit]
05:10 -!- ayush933 [~ayush933@49.37.45.4] has joined #bitcoin-core-pr-reviews
05:10 -!- ayush933 [~ayush933@49.37.45.4] has quit [Client Quit]
05:11 -!- brunoerg [~brunoerg@187.183.43.40] has quit [Ping timeout: 250 seconds]
05:15 -!- ghost43_ [~ghost43@gateway/tor-sasl/ghost43] has quit [Remote host closed the connection]
05:15 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #bitcoin-core-pr-reviews
05:21 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c3e:c153:e75f:59c3] has joined #bitcoin-core-pr-reviews
05:22 -!- shesek [~shesek@user/shesek] has joined #bitcoin-core-pr-reviews
05:22 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Remote host closed the connection]
05:23 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #bitcoin-core-pr-reviews
05:37 -!- yashraj [~yashraj@171.50.232.194] has joined #bitcoin-core-pr-reviews
05:37 -!- lucasdcf_ [~lucasdcf@2804:431:c7d8:eb7d:f0e4:e054:c2d:c68f] has quit [Read error: Connection reset by peer]
05:37 -!- lucasdcf_ [~lucasdcf@2804:431:c7d8:eb7d:f0e4:e054:c2d:c68f] has joined #bitcoin-core-pr-reviews
05:56 -!- shesek [~shesek@user/shesek] has quit [Remote host closed the connection]
05:57 -!- shesek [~shesek@user/shesek] has joined #bitcoin-core-pr-reviews
06:07 -!- lucasdcf_ [~lucasdcf@2804:431:c7d8:eb7d:f0e4:e054:c2d:c68f] has quit [Read error: Connection reset by peer]
06:07 -!- lucasdcf_ [~lucasdcf@2804:431:c7d8:eb7d:f0e4:e054:c2d:c68f] has joined #bitcoin-core-pr-reviews
06:10 -!- yashraj [~yashraj@171.50.232.194] has quit []
06:28 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Remote host closed the connection]
06:28 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #bitcoin-core-pr-reviews
06:35 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Remote host closed the connection]
06:38 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #bitcoin-core-pr-reviews
06:41 -!- lucasdcf_ [~lucasdcf@2804:431:c7d8:eb7d:f0e4:e054:c2d:c68f] has quit [Read error: Connection reset by peer]
06:42 -!- lucasdcf_ [~lucasdcf@2804:431:c7d8:eb7d:f0e4:e054:c2d:c68f] has joined #bitcoin-core-pr-reviews
06:49 -!- shesek [~shesek@user/shesek] has quit [Remote host closed the connection]
06:49 -!- shesek [~shesek@user/shesek] has joined #bitcoin-core-pr-reviews
06:51 -!- pinkfl0YD [~pinkfl0YD@2a02:26f7:d6cc:4000:512a:6de8:699e:e93d] has joined #bitcoin-core-pr-reviews
06:53 -!- pinkfl0YD55 [~pinkfl0YD@2a02:26f7:d6cc:4000:5765:f21e:2186:54b6] has joined #bitcoin-core-pr-reviews
06:53 -!- pinkfl0YD [~pinkfl0YD@2a02:26f7:d6cc:4000:512a:6de8:699e:e93d] has quit [Client Quit]
06:53 -!- pinkfl0YD55 [~pinkfl0YD@2a02:26f7:d6cc:4000:5765:f21e:2186:54b6] has quit [Client Quit]
07:00 -!- ghost43_ [~ghost43@gateway/tor-sasl/ghost43] has joined #bitcoin-core-pr-reviews
07:01 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Remote host closed the connection]
07:08 -!- ghost43_ [~ghost43@gateway/tor-sasl/ghost43] has quit [Remote host closed the connection]
07:09 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #bitcoin-core-pr-reviews
07:23 -!- shesek [~shesek@user/shesek] has quit [Remote host closed the connection]
07:23 -!- shesek [~shesek@user/shesek] has joined #bitcoin-core-pr-reviews
07:41 -!- shesek [~shesek@user/shesek] has quit [Remote host closed the connection]
07:41 -!- shesek [~shesek@user/shesek] has joined #bitcoin-core-pr-reviews
07:45 -!- lucasdcf_ [~lucasdcf@2804:431:c7d8:eb7d:f0e4:e054:c2d:c68f] has quit [Read error: Connection reset by peer]
07:45 -!- lucasdcf_ [~lucasdcf@2804:431:c7d8:eb7d:f0e4:e054:c2d:c68f] has joined #bitcoin-core-pr-reviews
07:58 -!- shesek [~shesek@user/shesek] has quit [Remote host closed the connection]
07:59 -!- shesek [~shesek@user/shesek] has joined #bitcoin-core-pr-reviews
07:59 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c3e:c153:e75f:59c3] has quit [Remote host closed the connection]
08:05 -!- lucasdcf_ [~lucasdcf@2804:431:c7d8:eb7d:f0e4:e054:c2d:c68f] has quit [Read error: Connection reset by peer]
08:06 -!- lucasdcf_ [~lucasdcf@2804:431:c7d8:eb7d:f0e4:e054:c2d:c68f] has joined #bitcoin-core-pr-reviews
08:07 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Remote host closed the connection]
08:07 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #bitcoin-core-pr-reviews
08:10 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Remote host closed the connection]
08:11 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #bitcoin-core-pr-reviews
08:15 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c3e:c153:e75f:59c3] has joined #bitcoin-core-pr-reviews
08:19 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c3e:c153:e75f:59c3] has quit [Ping timeout: 245 seconds]
08:20 -!- lucasdcf_ [~lucasdcf@2804:431:c7d8:eb7d:f0e4:e054:c2d:c68f] has quit [Read error: Connection reset by peer]
08:21 -!- lucasdcf_ [~lucasdcf@2804:431:c7d8:eb7d:f0e4:e054:c2d:c68f] has joined #bitcoin-core-pr-reviews
08:21  * michaelfolkson wondering whether it is easier to just a set up a MacOS VM on your Linux machine than cross-compiling....
08:24 < michaelfolkson> Obtaining Xcode.app eww :)
08:31 < sipa> that seems strictly easier than obtaining all of macos
08:33 < michaelfolkson> I guess. But wouldn't you want to run it before distributing it? In which case you need MacOS anyway?
08:36 < sipa> if you're talking about distributing release binaries: (a) you need to cross-compilr on linux anyway, because guix doesn't run on macos afaik and (b) all you care about when guix building is reproducibility of the binary; any mac user can test
08:36 < sipa> if you're talking about building for personal use... well if you don't use macos to begin with why do you care about building for it?
08:39 < sipa> I've never used macos on any of my own hardware, afaik.
08:40 < michaelfolkson> Right, in the personal case if you use MacOS then why not just compile on MacOS (ultimate destination) rather than compile on Linux first and then transfer the binary? Faster to compile?
08:41 < michaelfolkson> I assumed this was ultimately for distribution to other users
08:41 < sipa> sure
08:41 < sipa> what is "this" ?
08:41 < sipa> maybe i just have no clue what you're talking about
08:43 < michaelfolkson> Today's PR review club is on cross compiling https://github.com/bitcoin/bitcoin/pull/21778
08:43 < michaelfolkson> (for MacOS)
08:44 < sipa> our release binaries are produced using cross-compiling inside the guix environment
08:44 < sipa> that's the primary reason why you'd do that, i think
08:45 < sipa> if you use macos yourself, and are developing... sure just build natively on macos itself
08:45 < sipa> but that won't produce the release binaries
08:46 < michaelfolkson> Ah Guix is only on Linux, ok makes sense
08:47 < sipa> guix is a linux distribution/package system
08:47 < sipa> like ubuntu or debian, more or lrss
08:49 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c3e:c153:e75f:59c3] has joined #bitcoin-core-pr-reviews
08:51 < sipa> so it's not so much that guix is on linux, but the fact that guix produces a linux environment
08:51 < sipa> and inside the environment we invoke the depends build system
08:53 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c3e:c153:e75f:59c3] has quit [Ping timeout: 240 seconds]
08:54 < sipa> like arguably you can run guix inside a linux VM on windows too ... but the result is still a linux environment, and if we want to build windows binaries in there, we still need to cross-compilr
08:55 -!- lucasdcf_ [~lucasdcf@2804:431:c7d8:eb7d:f0e4:e054:c2d:c68f] has quit [Read error: Connection reset by peer]
08:55 -!- lucasdcf_ [~lucasdcf@2804:431:c7d8:eb7d:f0e4:e054:c2d:c68f] has joined #bitcoin-core-pr-reviews
08:57 < michaelfolkson> Ok Guix produces a Linux environment so if you want to use Guix to produce your MacOS executable you need to do it on Linux and then transfer it to the destination OS (MacOS)
08:57 < sipa> you can run guix in a linux VM on macos :p
08:58 < sipa> we must go deeper
09:04 < michaelfolkson> Ha I am beginning to appreciate more why some newer languages (e.g. Go, to lesser extent Rust) wanted to produce executables that can run on any OS
09:05 < hebasto> michaelfolkson: fwiw, a monterey macos virtualbox vm works on linux host stable only with _one_ virtual cpu :/
09:06 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Remote host closed the connection]
09:06 -!- monlovesmango [monlovesma@gateway/vpn/protonvpn/monlovesmango] has joined #bitcoin-core-pr-reviews
09:06 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #bitcoin-core-pr-reviews
09:07 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:f97b:bd76:25aa:a0d3] has joined #bitcoin-core-pr-reviews
09:08 -!- monlovesmango [monlovesma@gateway/vpn/protonvpn/monlovesmango] has quit [Client Quit]
09:08 < michaelfolkson> hebasto: Oh you can't assign more than one? 
09:09 < hebasto> I can, but vm becomes unstable
09:09 < hebasto> pre-monterey are fine though
09:10 < hebasto> virtualbox bug tracker has a related issue, if I recall correctly
09:10 < michaelfolkson> Ok hopefully it will be fixed
09:12 < hebasto> considering that running macos vm on non-macos hardware is a license violation...
09:14 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Remote host closed the connection]
09:15 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #bitcoin-core-pr-reviews
09:15 -!- observer91 [~observer@cpe-23-242-148-67.socal.res.rr.com] has joined #bitcoin-core-pr-reviews
09:15 < sipa> ah, right, so the answer to "isn't running a macos VM easier than cross-compiling" is "but that's illegal!!!111"
09:16 < michaelfolkson> Wot. So I break the license by setting up a MacOS VM on a Linux desktop... Ok for the record I did not do this lol
09:17 < sipa> Of course not.
09:17 < sipa> Duh.
09:17 < michaelfolkson> Ok enough of this rabbithole for me for today
09:26 < sipa> Ok, looked it up. It's not illegal to run MacOS in a VM, but it is against their license agreement to run it on non-Apple hardware (whether in a VM or not). So you can install Linux on a Mac, and then legally run MacOS in a VM inside that ;)
09:27 < emzy> The electrum reproducible build for macos uses a VM in apple hardware.
09:28 < emzy> But it was not easy to set up. Download the exact old macos version and the exact xcode version from apple.
09:28 < emzy> s/in/on/
09:32 < michaelfolkson> hebasto: " a monterey macos virtualbox vm works on linux host stable only with _one_ virtual cpu :/" <- Was this M1 or Intel?
09:32 < hebasto> michaelfolkson: intel
09:33 < michaelfolkson> Maybe they are directing resources to M1, making M1 more attractive
09:33  * michaelfolkson shrugs
09:34 -!- shesek [~shesek@user/shesek] has quit [Remote host closed the connection]
09:34 < michaelfolkson> sipa: Thanks, good to know :)
09:34 -!- shesek [~shesek@user/shesek] has joined #bitcoin-core-pr-reviews
09:37 < hebasto> talking about virtualization on M1 host, Docker removed Rosetta layer requirement
09:38 < hebasto> so I can make guix builds on my M1 within a linux docker container
09:39 < hebasto> pretty smooth, btw
09:42 < michaelfolkson> emzy: What OS on the VM?
09:43 < emzy> michaelfolkson: macOS 10.14.6
09:43 < michaelfolkson> Oh Linux and that's not against license right
09:44 < emzy> Host OS is also macOS (newest) and VM is vmware fusion.
09:44 < sipa> Electrum build is macOS VM on Mac hardware; no Linux involved, as far as I can tell.
09:45 < emzy> Documentation: https://github.com/spesmilo/electrum/tree/master/contrib/osx
09:45 < michaelfolkson> Why MacOS VM if MacOS already on the Mac? Must be different version...
09:45 < emzy> sipa: right.
09:46 < emzy> Hard to install an old version of macos on a new machine.
09:46 < sipa> michaelfolkson: To get a consistent version (the alternative would be to ask every builder to have Mac hardware around with that exact MacOS version).
09:48 < michaelfolkson> Or just distribute different releases for the different MacOS versions?
09:49 < larryruane> The PR review club notes ask, "Did you try performing a macOS cross compile?" -- is the intention to do this on the PR branch, or just on master? (I thought I'd give it a try)
09:51 < michaelfolkson> larryruane: I read it as on master as the PR is a WIP but I could be wrong
09:52 -!- rage-proof [~rage-proo@ip5f5bf27f.dynamic.kabel-deutschland.de] has joined #bitcoin-core-pr-reviews
09:56 -!- shesek [~shesek@user/shesek] has quit [Remote host closed the connection]
09:57 -!- shesek [~shesek@user/shesek] has joined #bitcoin-core-pr-reviews
09:57 -!- kouloumos_ [uid539228@id-539228.tinside.irccloud.com] has joined #bitcoin-core-pr-reviews
09:58 -!- ayush933 [~ayush933@49.37.45.44] has joined #bitcoin-core-pr-reviews
09:59 -!- svav [~svav@82-69-86-143.dsl.in-addr.zen.co.uk] has joined #bitcoin-core-pr-reviews
09:59 -!- B_1o1 [~B_1o1@187.202.169.16] has joined #bitcoin-core-pr-reviews
10:00 -!- sanya [~sanya@93-86-82-14.dynamic.isp.telekom.rs] has joined #bitcoin-core-pr-reviews
10:00 < fanquake> #startmeeting
10:00 < glozow> hi!
10:00 < fanquake> Welcome to PR review club. Today we're looking at #21778 LLVM 14 & LLD based macOS toolchain.
10:00 < emzy> hi
10:00 -!- danielabrozzoni [~danielabr@2001:bc8:1828:379::1] has joined #bitcoin-core-pr-reviews
10:00 < danielabrozzoni> hi 🙂 
10:00 < larryruane> hi
10:00 < sipa> hi
10:00 < michaelfolkson> hi
10:00 < B_1o1> hi
10:00 < svav> Hi
10:00 < hebasto> hi
10:00 < kouloumos_> hi
10:00 < fanquake> Did you review the PR? Concept ACK, approach ACK, tested ACK, or NACK?
10:00 < ayush933> hi
10:01 < fanquake> Also, a reminder: if you have any questions of comments, you don't need to ask to say anything, just go right ahead! :)
10:01 < hebasto> approach ACK
10:01 < danielabrozzoni> concept ACK 
10:01 < larryruane> concept ACK
10:01 < fanquake> This PR is a bit of special case, given it doesn't fully work yet, so we aren't expecting tested-ACKs.
10:02 < emzy> concept ACK
10:02 < fanquake> It'd be more interesting if someone was a concept/approach NACK. However we'll also cover that in a later question
10:02 < michaelfolkson> Haven't made my mind up. Presumably it is a Concept ACK as you are working on it but don't know enough to say it is a Concept ACK (yet)
10:02 < fanquake> Ok. Would someone like to give a one sentence summary of what the PR is trying to achieve?
10:02 < jamesob> hi
10:03 -!- pinkfl0YD [~pinkfl0YD@2401:4900:1909:43af:f0dd:fb51:fb8e:5a65] has joined #bitcoin-core-pr-reviews
10:03 < hebasto> replace very specific toolchain with well-known one
10:04 < fanquake> Exactly
10:04 < svav> The PR is trying to use a more standard toolchain to produce the MacOS binaries, as the current one is rather complicated
10:04 -!- dunxen [~dunxen@gateway/tor-sasl/dunxen] has joined #bitcoin-core-pr-reviews
10:04 < michaelfolkson> ^ and the more standard toolchain has only become possible recently
10:04 -!- pinkfl0YD [~pinkfl0YD@2401:4900:1909:43af:f0dd:fb51:fb8e:5a65] has quit [Client Quit]
10:04 < fanquake> Currently our macOS toolchain is pretty homebrew. It's constructed from pre-compiled binaries, 3rd-party sources, we compile our own llinker (ld64), and mush it all together todo macOS builds.
10:04 -!- pinkfl0YD [~pinkfl0YD@2401:4900:1909:43af:f0dd:fb51:fb8e:5a65] has joined #bitcoin-core-pr-reviews
10:04 < glozow> replace our current method of cross compiling for macOS  with... llvm and lld based toolchain
10:05 < lightlike> hi
10:05 < glozow> except i don't actually know what llvm and lld are
10:05 < glozow> a compiler and a linker, i guess
10:05 < fanquake> LLVM (https://llvm.org/) is " a collection of modular and reusable compiler and toolchain technologies."
10:06 < hebasto> a GCC killer?
10:06 < fanquake> It's the umbrella project for clangg (compiler) and lld (linker) as well as a number of other tools and libraries.
10:06 < fanquake> *clang
10:06 < fanquake> Including the *SAN libraries that we use in our sanitizer CIs etc
10:06 -!- lily51 [~lily@104.244.19.202] has joined #bitcoin-core-pr-reviews
10:06 < jamesob> llvm is sort of like what java byte code is to the jvm, but it's supposed to be a general purpose target for many different languages
10:07 < glozow> Mr. Quake, what specific requirements does Bitcoin Core have that not every compiler/linker might support?
10:07 < sipa> i think that's where the name comes from, but now it's more used for the name of the project built around it, than the internal language itself
10:07 < fanquake> The reason LLVM is most interesting for a macOS toolchain is that Apple has also upstream a lot of work (given Clang & LLVM) is the native Apple toolchain, meaning it is "better" in a number of ways, at producing macOS binaries than GCC + friends may be.
10:09 < fanquake> In regards to macOS, GNU ld does not support producing macOS binaries, or maybe in a limited fasion?, as far as I'm aware. So a specific requirement we have is a working linker.
10:09 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:f97b:bd76:25aa:a0d3] has quit [Ping timeout: 250 seconds]
10:09 < glozow> I see okay
10:10 < fanquake> Speaking more generally, off the top of my head, I don't think there is anything particularly fancy we require in regards to compiler / linker requirements. Other than say, things more general, like c++17 support etc.
10:10 < fanquake> I guess we can move onto:
10:10 < fanquake> 2. Can you think of a reason why we might want to continue using our current macOS toolchain, rather than switch?
10:10 < hebasto> it just works now
10:10 < glozow> our current toolchain works, presumably?
10:10 < fanquake> that is certainly a good reason not to switch
10:10 < larryruane> Ignore if off-topic, but are there plans to move default linux builds from gcc to clang?
10:11 < jamesob> The only thing I can think of (and this is slightly fuzzy) is that MarcoFalke has highlighted some concerning issues with the llvm/clang development process. IIRC, basically anyone can commit to the tree and they rely on some kind of revert process if something goes afoul. But this is slightly off-topic and unsubstantiated (at least by me)
10:11 < fanquake> larryruane: that is a bit of a can of worms, probably best discussed later. However I'd say we'd be much more likely to move to clang for windows before, before thinking about moving for Linux.
10:12 < fanquake> jamesob: that' a fair point. Obviously we care about who is maintaining the tools we are (sometimes blindly) using
10:12 < jamesob> This is to say nothing of course about the possibly dubious infrastructure maintaining the gcc toolchain... 
10:12 < fanquake> It's also the same reason I'd like to move away from our current setup. If anything, I think there are far more eyes over the LLVM repos, as opposed to: https://github.com/tpoechtrager/cctools-port
10:13 < jamesob> Yep
10:13 < fanquake> i.e has anyone ever review all the patches in that tree which are applied pre compiling ld64 and co
10:13 < jamesob> I certainly haven't lol
10:13 < fanquake> Cool. So two good reasons. Any others anyone can think of?
10:14 < glozow> Basic question, do we already use a llvm toolchian for something else?
10:14 < jamesob> glozow: afaik only in development
10:15 < fanquake> We do somewhat, given that we currently used a prebuilt clang (downloaded from LLVM) for the macOS builds, but don't use any of the other tools.
10:15 < lightlike> maybe if there was a slight difference in features, some non-essential but nice things the new toolchain wouldn't support?
10:15 < fanquake> lightlike: good point, and that is actually currently the case!
10:15 < fanquake> In the PR description I have a note about -bind_at_load, which is a linker flag we currently use.
10:16 < fanquake> It is not yet supported by lld. Although it's unclear if that will actually be an issue, as the reason for setting the flag may no-longer be relevant when building "modern" macOS binaries.
10:16 < fanquake> Needs following up on.
10:16 < hebasto> what does mean "modern"?
10:18 < fanquake> hebasto: as in targetting a more recent minimum version of macOS. As if you know that your binaries are only running on more recent versions, you can assumed certain behaviour out of the dynamic linker, which might obsolete the thing that passing the flag would achieve.
10:18 < emzy> iirc Macos switched to LLVM in xcode many years ago.
10:18 < hebasto> thanks
10:19 < fanquake> and we can enforce that the binaries are only run on recent versions at  compile time, by passing minimum version flags to the linker (and sanity check those versions in our symbol check scripts)
10:19 < fanquake> Ok. Let's move into 3
10:19 < fanquake> *onto
10:19 < fanquake> Did you try performing a macOS cross compile? Did it work? If not, what problems did you run into?
10:19 < hebasto> yeap, partially
10:19 < emzy> only the guix build.
10:20 < hebasto> doesn't guix use another clang?
10:20 < fanquake> Currently yes, Guix uses it's "own" clang, from the clang-toolchain package. We do that by setting FORCE_USE_SYSTEM_CLANG during the Guix depends build.
10:21 < fanquake> That would continue to be the case going forward, even after these changes, however as I allude to in the next Q, there is a Guix related change missing from this PR.
10:21 -!- Amanuel [~Amanuel@c-69-181-198-1.hsd1.ca.comcast.net] has joined #bitcoin-core-pr-reviews
10:22 < fanquake> If no-one was building, or didn't run into issue, we could move on to the next question.
10:22 < hebasto> facing with failure to configure qt on cross-compiling
10:22 < danielabrozzoni> I tried running the command in the pr (`make -C depends/ HOST=x86_64-apple-darwin -j9`), but it says `error adding symbols: DSO missing from command line`. I guess I'm doing something wrong ahah 
10:22 < fanquake> Although also happy to just answer generally macOS cross-compilation questions at this point as well.
10:22 < glozow> when you say guix's "own" clang = comes with the guix package?
10:22 -!- Amanuel83 [~Amanuel@2601:645:4300:6fe0:e900:1fe6:9241:88fd] has joined #bitcoin-core-pr-reviews
10:22 -!- Amanuel83 [~Amanuel@2601:645:4300:6fe0:e900:1fe6:9241:88fd] has quit [Client Quit]
10:23 < fanquake> glozow: yes, we install a clang-toolchain, and then use that clang for the build. See here: https://github.com/bitcoin/bitcoin/blob/bc562b9ef81d4e37c20c4fdbd73be44d6f12efa0/contrib/guix/manifest.scm#L616
10:23 < glozow> ok understood
10:23 < fanquake> danielabrozzoni: Interesting, where about's during the depends build did that happen?
10:23 < fanquake> Happy to follow up and debug
10:24 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c3e:c153:e75f:59c3] has joined #bitcoin-core-pr-reviews
10:24 < fanquake> Currently the most painful part of building is probably aquiring the macOS SDK. Did anyone have issues / attempt doing that?
10:24 < danielabrozzoni> I think it's something about qt, as it doesn't happen if I set NO_QT=1
10:24 < glozow> wgot the tarball
10:25 < emzy> fanquake: no issue, if you have an Apple account.
10:25 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Remote host closed the connection]
10:25 < michaelfolkson> [16:49:46]  <larryruane> The PR review club notes ask, "Did you try performing a macOS cross compile?" -- is the intention to do this on the PR branch, or just on master? (I thought I'd give it a try)
10:25 < fanquake> danielabrozzoni: If you've got logs / info, feel free to dump it on the PR. What OS / hardware are you building on?
10:25 < michaelfolkson> Was the intention master or the PR branch?
10:26 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #bitcoin-core-pr-reviews
10:26 < danielabrozzoni> Yeah, I'll look more into it and dump logs in the PR 🙂 I'm on NixOS 
10:26 < danielabrozzoni> On x86 
10:26 < fanquake> The PR branch. It's not fully working. However a depends build should work ok (including Qt), however building bitcoin-qt or libbitcoinconsensus will not at this stage.
10:26 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Remote host closed the connection]
10:27 < fanquake> So it's possible to run through building depends, pass a CONFIG_SITE to ./configure and build a working bitcoind, then run it on macOS
10:27 < fanquake> If there's no other build related questions, we could move onto #4
10:27 -!- pinkfl0YD [~pinkfl0YD@2401:4900:1909:43af:f0dd:fb51:fb8e:5a65] has quit [Quit: Client closed]
10:27 < fanquake> which is a 2-parter. I hope that is allowed
10:27 < fanquake> Do these changes effect our Guix (release) build process?  
10:28 < fanquake> -> If so, how? (hint: look for usage of FORCE_USE_SYSTEM_CLANG)
10:28 < fanquake> -> Is there a Guix build change you’d expect to see, which is missing from the PR?
10:28 -!- rage-proof [~rage-proo@ip5f5bf27f.dynamic.kabel-deutschland.de] has quit [Quit: Connection closed]
10:28 -!- pinkfl0YD [~pinkfl0YD@2a02:26f7:d6c4:4000:6d0:74a7:6f2b:477] has joined #bitcoin-core-pr-reviews
10:28 < fanquake> Feel free to answer/discuss either of the Qs
10:28 < hebasto> I didn't expect guix changes in this pr, rather in follow ups
10:30 < fanquake> hebasto: if we are migrating to LLVM/clang 14 in depends, would you expect a similar migration to clang 14 in guix to be a part of this PR?
10:30 < fanquake> i.e installing clang-toolchain-14 over clang-toolchain-10 as we currently do
10:30 < hebasto> as we have https://github.com/bitcoin/bitcoin/blob/master/contrib/guix/libexec/build.sh#L221 -- no behavior change in guix
10:30 < fanquake> for reference: https://github.com/bitcoin/bitcoin/blob/bc562b9ef81d4e37c20c4fdbd73be44d6f12efa0/contrib/guix/manifest.scm#L616
10:30 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has joined #bitcoin-core-pr-reviews
10:31 < michaelfolkson> Clang is no longer a dependency now we aren't using native_cctools
10:31 < fanquake> I would think we'd want to keep the clang versions in sync, so that guix builds would be using clang 14, similar to users cross-compilling on linux would be.
10:32 < sipa> with this, do we still need the macos SDK etc?
10:32 < fanquake> michaelfolkson: I would still consider clang a dependency, given for a macOS cross-compile, we are downloading and then compiling using clang
10:33 < fanquake> sipa: yea we will still need it to build
10:33 < hebasto> the intention is good, but I see no reasons to combine two parts into one pr. let's keep it focused
10:34 < fanquake> One way to make obtaining it slightly less painful could be for someone to write a tool to extract it from the macOS command line tools .pkg, which is a few hundred mb, and save having to download 12 GB of Xcode.xip.
10:35 < fanquake> hebasto: I'm not sure. I think I would like to see the version change happen together, otherwise in the interim, you'd be Guix building with Clang 10, and the CI, or developers doing cross-compiles would be using 14.
10:35 < fanquake> However we can discuss further in the PR
10:35 -!- effexzi [uid474242@id-474242.ilkley.irccloud.com] has joined #bitcoin-core-pr-reviews
10:36 < fanquake> Any other Guix related Qs? Or we could move along to #5
10:36 < michaelfolkson> What was the answer to #4?
10:37 < michaelfolkson> Sorry, struggling to follow... Do these changes effect our Guix (release) build process?
10:37 < fanquake> The discussion around whether we'd want to migrate to using Clang 14 for the Guix build, at the same time we swapped over to using Clang 14 in depends.
10:37 < michaelfolkson> Ok thanks
10:37 < fanquake> Yes, they do. Even though we use a Guix installed Clang for the Guix  build, we still use the rest of the macOS toolchain ld64, cctools etc from depends.
10:37 < jamesob> Seems reasonable... moving both in lockstep reduces variability in builds
10:38 < fanquake> So if we migrate to using the llvm binutils and lld in depends, that would also then be used by the Guix build, but it would remain using it's own installed Clang.
10:39 < fanquake> One other point
10:39 < fanquake> You might be wondering why we don't just install and use everything that Guix provides when performing the Guix build.
10:40 < jamesob> Does the Guix-provided llvm toolchain not support e.g. linking for macOS?
10:40 < fanquake> The reason is that we need to maintain a macOS toolchain, that works outside of Guix, as Guix does not run everywhere, and there shouldn't be an expectation that you would need to use it to cross-compile.
10:40 < jamesob> Oh interesting... so the only point is to avoid a total reliance on Guix for the cross-compilation process?
10:41 < fanquake> jamesob: I'd be surprised if it did currently, as the features making this possible are basically only emerging in LLVM 14, which was officially relased last night
10:41 -!- pinkfl0YD39 [~pinkfl0YD@2a02:26f7:d6cc:4000:15e8:4f6:baae:d1dc] has joined #bitcoin-core-pr-reviews
10:41 < jamesob> Ah okay, so it sounds like it's both
10:41 -!- pinkfl0YD [~pinkfl0YD@2a02:26f7:d6c4:4000:6d0:74a7:6f2b:477] has quit [Quit: Client closed]
10:41 < fanquake> jamesob: I think not relying solely on Guix to be able to compile bitcoind for certain OS's is a good thing
10:42 < jamesob> Yep, agreed
10:42 < fanquake> Especially given that Guix doesn't work "everywhere". either hardware, or OS wise 
10:42 < jamesob> Didn't know if that was unique to cross-compilation for macOS
10:42 < hebasto> also using guix in Ci is questionable
10:42 < jamesob> yeah guix is very resource intensive
10:42 < fanquake> Cool. Let's move onto #5
10:42 < michaelfolkson> Relying solely means only supporting Guix builds? 
10:43 < fanquake> In native_llvm’s preprocessing step we rm -rf lib/libc++abi.so*:
10:43 < fanquake> -> Why do/did we do this? (remember we target a macOS SDK when building)
10:43 < fanquake> -> Is it actually necessary? (double-check what is ultimately copied from the tarball).
10:43 < fanquake> michaelfolkson: yes. We cannot tell people that they need to install and use Guix if they want to compile Bitcoin Core.
10:44 < michaelfolkson> Gotcha, yeah agreed
10:44 < fanquake> Which means the depends system must remain generic, and useable as widely as possible.
10:44 < fanquake> and be able to compile all binaries, hosts etc that we produce in release builds.
10:44 < hebasto> if one makes build for `native_llvm_fetched` target, it becomes obvious that `rm` do nothing
10:45 < fanquake> hebasto: correct. The preprocessing block as it stands is a no-op.
10:45 < jamesob> > why `rm`: is it because we'd be linking against a linux binary interface for a macos build?
10:46 < michaelfolkson> The arguments for not forcing Guix use are it is new(ish), users might not understand it, it is not industry standard outside of Bitcoin?
10:46 < fanquake> jamesob: I'm going to lazily dump a few lines I prepared that may explain further
10:46 < michaelfolkson> Or maybe it is just it has only been added to Core recently(ish)
10:46 < fanquake> The rm was originally added in https://github.com/bitcoin/bitcoin/pull/8210, to remove any LLVM C++ ABI related objects, given at that point we were copying more files out of the lib dirs in the clang tarball. Possibly just a belt-and-suspenders thing.
10:47 -!- pinkfl0YD [~pinkfl0YD@2a02:26f7:d6cc:4000:1f9a:7b4c:6e64:26fe] has joined #bitcoin-core-pr-reviews
10:47 < fanquake> Likely irrelevant since https://github.com/bitcoin/bitcoin/pull/19240, fbcfcf695435c9587e9f9fd2809c4d5350b2558e, where we stopped copying any c++ libs from the clang tarball.
10:47 < fanquake> The code in its current state is pointless / broken for 2 reasons:
10:47 -!- pinkfl0YD39 [~pinkfl0YD@2a02:26f7:d6cc:4000:15e8:4f6:baae:d1dc] has quit [Quit: Client closed]
10:47 < fanquake> The only things we copy out of lib/ are `libLTO.so` and headers from lib/clang/clang-version/include, so deleting .so files from /lib in advance of that, doesn't achieve anything.
10:47 < fanquake> Besides that, the `libc++abi.so*` objects have actually changed location inside the lib/ dir, so even if we kept the current code, it wouldn't actually remove anything anyways.
10:48 < fanquake> michaelfolkson: there are a number of arguments for not forcing anyone that wants to compile your software to use a single package manager to do so. Happy to discuss further later.
10:48 < hebasto> I did not find `libc++abi.so*` anywhere
10:49 < hebasto> in fetched archive
10:49 < fanquake> hebasto: I no-longer have the tarball handy, but iirc, the .so* had moved down a directory or two. I'll double check.
10:50 < fanquake> We can probably move onto #6. I am hoping everyone hasn't quite fallen asleep yet.
10:50 < fanquake> In native_llvm.mk, we copy a number of tools (i.e llvm-*, not clang or lld) out of the tarball:
10:50 < fanquake> -> What is one of them used for?
10:50 < fanquake> -> bonus: If we rename that tool when copying it, why might we do that?
10:52 < hebasto> talking about tools, why we do not need llvm-as, i.e. assemble?
10:52 < jamesob> Do we rename to avoid PATH conflicts with system tooling? e.g. `which ld` vs. `$(host)-ld`?
10:53 -!- pinkfl0YD37 [~pinkfl0YD@2a02:26f7:d6cc:4000:7ec9:7442:ebcd:d19b] has joined #bitcoin-core-pr-reviews
10:53 < fanquake> hebasto: I'm going to say because whatever it would be doing, is being handled by something else, I'll have to get you an answer, sorry.
10:53 -!- pinkfl0YD [~pinkfl0YD@2a02:26f7:d6cc:4000:1f9a:7b4c:6e64:26fe] has quit [Quit: Client closed]
10:53 < michaelfolkson> You mean pick a particular tool and say what it does?
10:54 < michaelfolkson> (out of those tools copied)
10:54 < fanquake> jamesob: somewhat. The reason we rename lld to ld, is to make things "simpler" for the build system, as most build systems, especially those using autotools, look for, and expect to use a linker called ld.
10:54 < fanquake> Given we are in full control of our build system here, we can just rename lld, and have it "pretend" to be ld, for the sake of making everything work, and the build systems expecting GNU ld should mostly be none-the-wiser.
10:54 -!- ayush933 [~ayush933@49.37.45.44] has quit [Quit: Connection closed]
10:55 < jamesob> right - `ld` is sort of a generic name for a linker whereas `lld` is LLVM's specific ld-compatible linker
10:55 < fanquake> michaelfolkson: yes basically
10:55 < michaelfolkson> Search engine llvm-install-name-tool
10:55 < michaelfolkson> :)
10:55 < glozow> when you say copy stuff out of the tarball, u mean like, these? https://github.com/bitcoin/bitcoin/pull/21778/files#diff-374d342fe41e2c3754a305bb1db9ba2c56f519fcd09c24cb26abba3ca64690feR19-R32
10:55 < fanquake> The other reason we might rename tools to have the $(host)- is discussed here somewhat: https://www.gnu.org/software/automake/manual/html_node/Cross_002dCompilation.html
10:55 < michaelfolkson> "tool to manipulate dynamic shared library install names and rpaths listed in a Mach-O binary"
10:56 < fanquake> When cross-compiling, autotools generally looks for native (build) tools that have the target arch in the name.
10:56 < fanquake> i.e x86_64-apple-darwin-strip
10:56 < jamesob> ah okay, so this is sort of an autotools convention?
10:56 < fanquake> So renaming some of the tools is also a bit of a convenience for autotools, and can prevent warning output like: "configure: WARNING: using cross tools not prefixed with host triplet".
10:56 < michaelfolkson> What is Mach-O, gosh search engine again
10:57 < sipa> Mac's executable file format.
10:57 < fanquake> MACHO is the macOS exeutable file format
10:57 < hebasto> it's macos's ELF :)
10:57 < fanquake> to cover a couple other tools, and why we might rename them:
10:57 < jamesob> interesting that we don't do the host-prefixing with clang/clang++, but I guess those are not platform specific?
10:57  * michaelfolkson sweats
10:57 < fanquake> llvm-install-name-tool -> install_name_tool as that is its "usual" name, and what other tools / build systems will look for / expect.
10:57 < fanquake> Same for llvm-libtool-darwin -> libtool as build systems / autotools expect libtool, not libtool-darwin.
10:57 < sipa> Windows' executable format is called PE, IIRC.
10:58 < fanquake> correct
10:58 -!- pinkfl0YD37 [~pinkfl0YD@2a02:26f7:d6cc:4000:7ec9:7442:ebcd:d19b] has quit [Quit: Client closed]
10:58 < sipa> elves > machos > physical education
10:58 < fanquake> I think we are running out of time, but if anyone has any other related thoughts / questions, feel free to throw them out.
10:59 < fanquake> I realise this has been a bit of a whirlwind tour of macOS related things
10:59 < michaelfolkson> Ok slightly less uninformed Concept ACK from me
10:59 < jamesob> thanks fanquake
10:59 < glozow> thank you fanquake!
10:59 < emzy> thanks fanquake!
10:59 < danielabrozzoni> thank you! 
10:59 < hebasto> fanquake: thank you
11:00 < kouloumos_> thank you!
11:00 < michaelfolkson> Thanks fanquake, that was great
11:00 < sipa> thanks for hosting!
11:00 < sipa> (and working on all this crazy stuff...)
11:00 < fanquake> Cool, thanks everyone. I think that means we can
11:00 < fanquake> #endmeeting
11:00 < larryruane> thanks fanquake!
11:01 < fanquake> I'll keep tabs on the channel for a while and try follow up with any other questions
11:01 < B_1o1> thanks fanquake!
11:02 < michaelfolkson> This PR is for Intel Mac only right? Any additional considerations for M1 Mac?
11:03 < fanquake> No that PR would be for both
11:03 < hebasto> but I did not build it on M1
11:03 < hebasto> yet
11:03 < hebasto> or for M1
11:04 < fanquake> yes, you can do the matrix of, x86_64 on x86_64, arm64 (M1) on x86_64, x86_64 on arm64 and arm64 on arm64.
11:04 < svav> Thanks fanquake!
11:05 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c3e:c153:e75f:59c3] has quit [Remote host closed the connection]
11:06 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c3e:c153:e75f:59c3] has joined #bitcoin-core-pr-reviews
11:07 < michaelfolkson> If I'd had to guess I'd have guessed tools wouldn't work on both. Not much seems to work on both
11:08 < sipa> cross-compiling is exactly about building something on another environment than it'll run on :)
11:08 < michaelfolkson> Ha I guess
11:09 -!- yashraj [~yashraj@171.50.232.194] has joined #bitcoin-core-pr-reviews
11:10 < sipa> it's more commonly used for building for other hardware than for a different OS on the same hardware
11:14 -!- pinkfl0YD [~pinkfl0YD@2a02:26f7:d6c1:4000:8915:97b4:fec7:b20c] has joined #bitcoin-core-pr-reviews
11:17 -!- pinkfl0YD [~pinkfl0YD@2a02:26f7:d6c1:4000:8915:97b4:fec7:b20c] has quit [Client Quit]
11:17 -!- pinkfl0YD [~pinkfl0YD@2a02:26f7:d6cc:4000:c1c9:641:8239:4f61] has joined #bitcoin-core-pr-reviews
11:18 -!- yashraj [~yashraj@171.50.232.194] has quit []
11:19 -!- pinkfl0YD [~pinkfl0YD@2a02:26f7:d6cc:4000:c1c9:641:8239:4f61] has quit [Client Quit]
11:20 -!- lily51 [~lily@104.244.19.202] has quit [Quit: Connection closed]
11:29 -!- B_1o1 [~B_1o1@187.202.169.16] has quit [Quit: Connection closed]
11:38 -!- shesek [~shesek@user/shesek] has quit [Remote host closed the connection]
11:42 -!- Amanuel [~Amanuel@c-69-181-198-1.hsd1.ca.comcast.net] has quit [Quit: Connection closed]
11:45 -!- Talkless [~Talkless@mail.dargis.net] has joined #bitcoin-core-pr-reviews
11:45 -!- lucasdcf_ [~lucasdcf@2804:431:c7d8:eb7d:f0e4:e054:c2d:c68f] has quit [Read error: Connection reset by peer]
11:45 -!- lucasdcf_ [~lucasdcf@2804:431:c7d8:eb7d:f0e4:e054:c2d:c68f] has joined #bitcoin-core-pr-reviews
11:51 -!- shesek [~shesek@user/shesek] has joined #bitcoin-core-pr-reviews
12:52 -!- shesek [~shesek@user/shesek] has quit [Remote host closed the connection]
12:52 -!- shesek [~shesek@user/shesek] has joined #bitcoin-core-pr-reviews
12:59 -!- lucasdcf_ [~lucasdcf@2804:431:c7d8:eb7d:f0e4:e054:c2d:c68f] has quit [Read error: Connection reset by peer]
12:59 -!- lucasdcf_ [~lucasdcf@2804:431:c7d8:eb7d:f0e4:e054:c2d:c68f] has joined #bitcoin-core-pr-reviews
13:07 -!- shesek [~shesek@user/shesek] has quit [Remote host closed the connection]
13:12 -!- Talkless [~Talkless@mail.dargis.net] has quit [Quit: Konversation terminated!]
13:15 -!- effexzi [uid474242@id-474242.ilkley.irccloud.com] has quit [Quit: Connection closed for inactivity]
13:19 -!- hashfunc569 [~user@2601:5c0:c280:7090:78e9:5f82:1899:8c96] has joined #bitcoin-core-pr-reviews
13:23 -!- shesek [~shesek@user/shesek] has joined #bitcoin-core-pr-reviews
13:47 -!- shesek [~shesek@user/shesek] has quit [Remote host closed the connection]
13:47 -!- shesek [~shesek@user/shesek] has joined #bitcoin-core-pr-reviews
13:53 -!- Solomon [~Solomon@068-188-185-025.res.spectrum.com] has joined #bitcoin-core-pr-reviews
13:53 -!- Solomon [~Solomon@068-188-185-025.res.spectrum.com] has quit [Client Quit]
13:54 -!- GucciPoet [~GucciPoet@068-188-185-025.res.spectrum.com] has joined #bitcoin-core-pr-reviews
13:55 < GucciPoet> Hi guys I'm new. Here to do my part for Bitcoin. Here to watch and learn, absorb. Trying to be a better developer!
14:16 -!- kouloumos_ [uid539228@id-539228.tinside.irccloud.com] has quit [Quit: Connection closed for inactivity]
14:18 -!- shesek [~shesek@user/shesek] has quit [Remote host closed the connection]
14:18 -!- shesek [~shesek@user/shesek] has joined #bitcoin-core-pr-reviews
14:27 < GucciPoet> Is this the correct room for the meeting?
14:28 < sipa> the meeting ended 3.5 hours ago
14:28 < GucciPoet> sipa: i thought it was 17:00 i guess not
14:30 < sipa> 17:00 UTC
14:30 < GucciPoet> sipa: Ah, thank you!
14:41 -!- lucasdcf_ [~lucasdcf@2804:431:c7d8:eb7d:f0e4:e054:c2d:c68f] has quit [Read error: Connection reset by peer]
14:41 -!- lucasdcf_ [~lucasdcf@2804:431:c7d8:eb7d:f0e4:e054:c2d:c68f] has joined #bitcoin-core-pr-reviews
14:52 -!- GucciPoet [~GucciPoet@068-188-185-025.res.spectrum.com] has quit [Quit: Connection closed]
14:52 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c3e:c153:e75f:59c3] has quit [Remote host closed the connection]
14:56 -!- shesek [~shesek@user/shesek] has quit [Remote host closed the connection]
14:56 -!- shesek [~shesek@user/shesek] has joined #bitcoin-core-pr-reviews
15:09 -!- brunoerg [~brunoerg@187.183.43.40] has joined #bitcoin-core-pr-reviews
15:13 -!- brunoerg [~brunoerg@187.183.43.40] has quit [Ping timeout: 240 seconds]
15:19 -!- lucasdcf_ [~lucasdcf@2804:431:c7d8:eb7d:f0e4:e054:c2d:c68f] has quit [Read error: Connection reset by peer]
15:20 -!- lucasdcf_ [~lucasdcf@2804:431:c7d8:eb7d:f0e4:e054:c2d:c68f] has joined #bitcoin-core-pr-reviews
15:20 -!- sanya [~sanya@93-86-82-14.dynamic.isp.telekom.rs] has quit [Quit: Connection closed]
15:22 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c3e:c153:e75f:59c3] has joined #bitcoin-core-pr-reviews
15:27 -!- shesek [~shesek@user/shesek] has quit [Remote host closed the connection]
15:27 -!- shesek [~shesek@user/shesek] has joined #bitcoin-core-pr-reviews
15:34 -!- lucasdcf_ [~lucasdcf@2804:431:c7d8:eb7d:f0e4:e054:c2d:c68f] has quit [Read error: Connection reset by peer]
15:34 -!- lucasdcf_ [~lucasdcf@2804:431:c7d8:eb7d:f0e4:e054:c2d:c68f] has joined #bitcoin-core-pr-reviews
15:51 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c3e:c153:e75f:59c3] has quit [Remote host closed the connection]
15:52 -!- hashfunc569 [~user@2601:5c0:c280:7090:78e9:5f82:1899:8c96] has quit [Ping timeout: 240 seconds]
16:02 -!- shesek [~shesek@user/shesek] has quit [Remote host closed the connection]
16:02 -!- shesek [~shesek@user/shesek] has joined #bitcoin-core-pr-reviews
16:09 -!- brunoerg [~brunoerg@187.183.43.40] has joined #bitcoin-core-pr-reviews
16:13 -!- brunoerg [~brunoerg@187.183.43.40] has quit [Ping timeout: 252 seconds]
16:24 -!- shesek [~shesek@user/shesek] has quit [Remote host closed the connection]
16:24 -!- shesek [~shesek@user/shesek] has joined #bitcoin-core-pr-reviews
16:34 -!- shesek [~shesek@user/shesek] has quit [Remote host closed the connection]
16:34 -!- shesek [~shesek@user/shesek] has joined #bitcoin-core-pr-reviews
16:42 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c3e:c153:e75f:59c3] has joined #bitcoin-core-pr-reviews
16:46 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c3e:c153:e75f:59c3] has quit [Ping timeout: 240 seconds]
17:01 -!- shesek [~shesek@user/shesek] has quit [Remote host closed the connection]
17:01 -!- shesek [~shesek@user/shesek] has joined #bitcoin-core-pr-reviews
17:03 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c3e:c153:e75f:59c3] has joined #bitcoin-core-pr-reviews
17:15 -!- shesek [~shesek@user/shesek] has quit [Remote host closed the connection]
17:15 -!- shesek [~shesek@user/shesek] has joined #bitcoin-core-pr-reviews
17:32 -!- shesek [~shesek@user/shesek] has quit [Remote host closed the connection]
17:32 -!- shesek [~shesek@user/shesek] has joined #bitcoin-core-pr-reviews
17:43 -!- svav [~svav@82-69-86-143.dsl.in-addr.zen.co.uk] has quit [Quit: Connection closed]
17:45 -!- shesek [~shesek@user/shesek] has quit [Remote host closed the connection]
17:46 -!- shesek [~shesek@user/shesek] has joined #bitcoin-core-pr-reviews
17:47 -!- lucasdcf_ [~lucasdcf@2804:431:c7d8:eb7d:f0e4:e054:c2d:c68f] has quit [Read error: Connection reset by peer]
17:48 -!- lucasdcf_ [~lucasdcf@2804:431:c7d8:eb7d:f0e4:e054:c2d:c68f] has joined #bitcoin-core-pr-reviews
17:54 -!- shesek [~shesek@user/shesek] has quit [Remote host closed the connection]
17:54 -!- shesek [~shesek@user/shesek] has joined #bitcoin-core-pr-reviews
18:05 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c3e:c153:e75f:59c3] has quit [Ping timeout: 252 seconds]
18:22 -!- lucasdcf_ [~lucasdcf@2804:431:c7d8:eb7d:f0e4:e054:c2d:c68f] has quit [Read error: Connection reset by peer]
18:23 -!- lucasdcf_ [~lucasdcf@2804:431:c7d8:eb7d:f0e4:e054:c2d:c68f] has joined #bitcoin-core-pr-reviews
18:33 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c3e:c153:e75f:59c3] has joined #bitcoin-core-pr-reviews
18:34 -!- shesek [~shesek@user/shesek] has quit [Remote host closed the connection]
18:34 -!- shesek [~shesek@user/shesek] has joined #bitcoin-core-pr-reviews
18:49 -!- shesek [~shesek@user/shesek] has quit [Remote host closed the connection]
18:49 -!- shesek [~shesek@user/shesek] has joined #bitcoin-core-pr-reviews
18:51 -!- luke-jr [~luke-jr@user/luke-jr] has quit [Read error: Connection reset by peer]
18:53 -!- luke-jr [~luke-jr@user/luke-jr] has joined #bitcoin-core-pr-reviews
18:58 -!- luke-jr [~luke-jr@user/luke-jr] has quit [Read error: Connection reset by peer]
19:00 -!- luke-jr [~luke-jr@user/luke-jr] has joined #bitcoin-core-pr-reviews
19:22 -!- Lucas_dcf [~lucasdcf@2804:431:c7d8:eb7d:f0e4:e054:c2d:c68f] has joined #bitcoin-core-pr-reviews
19:26 -!- lucasdcf_ [~lucasdcf@2804:431:c7d8:eb7d:f0e4:e054:c2d:c68f] has quit [Ping timeout: 268 seconds]
19:31 -!- shesek [~shesek@user/shesek] has quit [Remote host closed the connection]
19:31 -!- shesek [~shesek@user/shesek] has joined #bitcoin-core-pr-reviews
19:37 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c3e:c153:e75f:59c3] has quit [Ping timeout: 268 seconds]
19:53 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c3e:c153:e75f:59c3] has joined #bitcoin-core-pr-reviews
20:02 -!- shesek_ [~shesek@user/shesek] has joined #bitcoin-core-pr-reviews
20:06 -!- shesek [~shesek@user/shesek] has quit [Ping timeout: 272 seconds]
20:16 -!- hashfunc569 [~user@2601:5c0:c280:7090:78e9:5f82:1899:8c96] has joined #bitcoin-core-pr-reviews
20:54 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c3e:c153:e75f:59c3] has quit [Ping timeout: 240 seconds]
21:01 -!- Lucas_dcf [~lucasdcf@2804:431:c7d8:eb7d:f0e4:e054:c2d:c68f] has quit [Read error: Connection reset by peer]
21:02 -!- Lucas_dcf [~lucasdcf@2804:431:c7d8:eb7d:f0e4:e054:c2d:c68f] has joined #bitcoin-core-pr-reviews
21:09 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c3e:c153:e75f:59c3] has joined #bitcoin-core-pr-reviews
21:11 -!- shesek_ [~shesek@user/shesek] has quit [Remote host closed the connection]
21:11 -!- shesek_ [~shesek@user/shesek] has joined #bitcoin-core-pr-reviews
21:26 -!- Lucas_dcf [~lucasdcf@2804:431:c7d8:eb7d:f0e4:e054:c2d:c68f] has quit [Read error: Connection reset by peer]
21:26 -!- Lucas_dcf [~lucasdcf@2804:431:c7d8:eb7d:f0e4:e054:c2d:c68f] has joined #bitcoin-core-pr-reviews
21:29 -!- hashfunc569 [~user@2601:5c0:c280:7090:78e9:5f82:1899:8c96] has quit [Ping timeout: 240 seconds]
21:31 -!- franzo [~franzo@103.129.2.170] has joined #bitcoin-core-pr-reviews
21:31 -!- franzo [~franzo@103.129.2.170] has quit [Client Quit]
21:36 -!- shesek_ [~shesek@user/shesek] has quit [Remote host closed the connection]
21:36 -!- Lucas_dcf [~lucasdcf@2804:431:c7d8:eb7d:f0e4:e054:c2d:c68f] has quit [Read error: Connection reset by peer]
21:36 -!- shesek_ [~shesek@user/shesek] has joined #bitcoin-core-pr-reviews
21:37 -!- Lucas_dcf [~lucasdcf@2804:431:c7d8:eb7d:f0e4:e054:c2d:c68f] has joined #bitcoin-core-pr-reviews
21:40 -!- luke-jr [~luke-jr@user/luke-jr] has quit [Read error: Connection reset by peer]
21:41 -!- luke-jr [~luke-jr@user/luke-jr] has joined #bitcoin-core-pr-reviews
21:41 -!- ghost43 [~ghost43@gateway/tor-sasl/ghost43] has quit [Remote host closed the connection]
21:47 -!- shesek_ [~shesek@user/shesek] has quit [Remote host closed the connection]
21:47 -!- shesek_ [~shesek@user/shesek] has joined #bitcoin-core-pr-reviews
22:02 -!- shesek_ [~shesek@user/shesek] has quit [Remote host closed the connection]
22:02 -!- shesek_ [~shesek@user/shesek] has joined #bitcoin-core-pr-reviews
22:04 -!- shesek_ [~shesek@user/shesek] has quit [Remote host closed the connection]
22:04 -!- shesek_ [~shesek@user/shesek] has joined #bitcoin-core-pr-reviews
22:12 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c3e:c153:e75f:59c3] has quit [Ping timeout: 252 seconds]
22:14 -!- shesek_ [~shesek@user/shesek] has quit [Remote host closed the connection]
22:14 -!- shesek_ [~shesek@user/shesek] has joined #bitcoin-core-pr-reviews
22:25 -!- shesek_ [~shesek@user/shesek] has quit [Remote host closed the connection]
22:25 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c3e:c153:e75f:59c3] has joined #bitcoin-core-pr-reviews
22:26 -!- shesek_ [~shesek@user/shesek] has joined #bitcoin-core-pr-reviews
22:44 -!- Lucas_dcf [~lucasdcf@2804:431:c7d8:eb7d:f0e4:e054:c2d:c68f] has quit [Read error: Connection reset by peer]
22:45 -!- Lucas_dcf [~lucasdcf@2804:431:c7d8:eb7d:f0e4:e054:c2d:c68f] has joined #bitcoin-core-pr-reviews
22:51 -!- observer91 [~observer@cpe-23-242-148-67.socal.res.rr.com] has quit [Quit: Connection closed]
22:58 -!- shesek_ [~shesek@user/shesek] has quit [Remote host closed the connection]
22:58 -!- shesek_ [~shesek@user/shesek] has joined #bitcoin-core-pr-reviews
23:12 -!- Guest34 [~textual@90.160.136.106] has joined #bitcoin-core-pr-reviews
23:15 -!- shesek_ [~shesek@user/shesek] has quit [Remote host closed the connection]
23:15 -!- shesek_ [~shesek@user/shesek] has joined #bitcoin-core-pr-reviews
23:25 -!- shesek_ [~shesek@user/shesek] has quit [Remote host closed the connection]
23:25 -!- shesek_ [~shesek@user/shesek] has joined #bitcoin-core-pr-reviews
23:27 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c3e:c153:e75f:59c3] has quit [Ping timeout: 240 seconds]
23:29 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c3e:c153:e75f:59c3] has joined #bitcoin-core-pr-reviews
23:32 -!- shesek_ [~shesek@user/shesek] has quit [Remote host closed the connection]
23:32 -!- shesek_ [~shesek@user/shesek] has joined #bitcoin-core-pr-reviews
23:34 -!- brunoerg [~brunoerg@2804:14d:5281:8ae2:1c3e:c153:e75f:59c3] has quit [Ping timeout: 252 seconds]
23:36 -!- brunoerg [~brunoerg@187.183.43.40] has joined #bitcoin-core-pr-reviews
23:38 -!- Lucas_dcf [~lucasdcf@2804:431:c7d8:eb7d:f0e4:e054:c2d:c68f] has quit [Read error: Connection reset by peer]
23:39 -!- Lucas_dcf [~lucasdcf@2804:431:c7d8:eb7d:f0e4:e054:c2d:c68f] has joined #bitcoin-core-pr-reviews
23:42 -!- Guest34 [~textual@90.160.136.106] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
23:43 -!- Lucas_dcf [~lucasdcf@2804:431:c7d8:eb7d:f0e4:e054:c2d:c68f] has quit [Read error: Connection reset by peer]
23:44 -!- Lucas_dcf [~lucasdcf@2804:431:c7d8:eb7d:f0e4:e054:c2d:c68f] has joined #bitcoin-core-pr-reviews
23:57 -!- shesek_ [~shesek@user/shesek] has quit [Remote host closed the connection]
23:57 -!- shesek_ [~shesek@user/shesek] has joined #bitcoin-core-pr-reviews
--- Log closed Thu Mar 24 00:00:35 2022