--- Log opened Thu Dec 02 00:00:49 2021
04:28 -!- b10c [uid500648@id-500648.ilkley.irccloud.com] has joined #bitcoin-core-builds
05:31 -!- Kaizen_Kintsugi [~Kaizen_Ki@node-1w7jr9yi65te5s4lfwjywtjgw.ipv6.telus.net] has quit [Remote host closed the connection]
05:31 -!- Kaizen_Kintsugi [~Kaizen_Ki@node-1w7jr9yi65te5s4lfwjywtjgw.ipv6.telus.net] has joined #bitcoin-core-builds
07:35 -!- Kaizen_Kintsugi [~Kaizen_Ki@node-1w7jr9yi65te5s4lfwjywtjgw.ipv6.telus.net] has quit [Remote host closed the connection]
07:35 -!- Kaizen_Kintsugi [~Kaizen_Ki@node-1w7jr9yi65te5s4lfwjywtjgw.ipv6.telus.net] has joined #bitcoin-core-builds
07:41 -!- Kaizen_Kintsugi [~Kaizen_Ki@node-1w7jr9yi65te5s4lfwjywtjgw.ipv6.telus.net] has quit [Ping timeout: 268 seconds]
07:50 -!- Kaizen_Kintsugi [~Kaizen_Ki@node-1w7jr9yi65te5s4lfwjywtjgw.ipv6.telus.net] has joined #bitcoin-core-builds
10:01 < real_or_random> Here's a (probably naive) question: Would guix (or something else) make it (easily) possible to pass a hash of the compile-time deps of secp256k1 (entire toolchain, etc) to the secp256k1 build, e.g.,  to ./configure?
10:48 < laanwj> maybe it's possible, but it's not a usual way of doing things, configure scripts tend to be oblivious of the guix build, guix handles the dependency tree stuff internally
11:01 < sipa> right, you run configure and make inside a guix env, not the other way around
11:57 < real_or_random> makes sense
12:16 -!- Kaizen_Kintsugi [~Kaizen_Ki@node-1w7jr9yi65te5s4lfwjywtjgw.ipv6.telus.net] has quit [Remote host closed the connection]
12:16 -!- Kaizen_Kintsugi [~Kaizen_Ki@node-1w7jr9yi65te4fcj8of78jxhi.ipv6.telus.net] has joined #bitcoin-core-builds
12:21 -!- Kaizen_Kintsugi [~Kaizen_Ki@node-1w7jr9yi65te4fcj8of78jxhi.ipv6.telus.net] has quit [Ping timeout: 268 seconds]
12:38 -!- Kaizen_Kintsugi [~Kaizen_Ki@node-1w7jr9yi65te4fcj8of78jxhi.ipv6.telus.net] has joined #bitcoin-core-builds
13:11 -!- Kaizen_Kintsugi [~Kaizen_Ki@node-1w7jr9yi65te4fcj8of78jxhi.ipv6.telus.net] has quit [Remote host closed the connection]
13:11 -!- Kaizen_Kintsugi [~Kaizen_Ki@node-1w7jr9yi65te4fcj8of78jxhi.ipv6.telus.net] has joined #bitcoin-core-builds
13:33 -!- Kaizen_Kintsugi [~Kaizen_Ki@node-1w7jr9yi65te4fcj8of78jxhi.ipv6.telus.net] has quit [Remote host closed the connection]
13:34 -!- Kaizen_Kintsugi [~Kaizen_Ki@node-1w7jr9yi65te4fcj8of78jxhi.ipv6.telus.net] has joined #bitcoin-core-builds
13:38 -!- Kaizen_Kintsugi [~Kaizen_Ki@node-1w7jr9yi65te4fcj8of78jxhi.ipv6.telus.net] has quit [Ping timeout: 268 seconds]
13:51 -!- Kaizen_Kintsugi [~Kaizen_Ki@node-1w7jr9yi65te4fcj8of78jxhi.ipv6.telus.net] has joined #bitcoin-core-builds
17:52 -!- b10c [uid500648@id-500648.ilkley.irccloud.com] has quit [Quit: Connection closed for inactivity]
18:34 -!- kallewoof [~quassel@user/kallewoof] has quit [Ping timeout: 268 seconds]
--- Log closed Fri Dec 03 00:00:50 2021