--- Log opened Sat Jun 04 00:00:43 2022 00:08 -!- z9z0b3t1_ [z9z0b3t1c@gateway/vpn/protonvpn/z9z0b3t1c] has joined #bitcoin-core-builds 00:11 -!- z9z0b3t1c [z9z0b3t1c@gateway/vpn/protonvpn/z9z0b3t1c] has quit [Ping timeout: 244 seconds] 00:19 -!- sipsorcery [~sipsorcer@2a02:8084:6180:500::12b] has joined #bitcoin-core-builds 01:42 -!- sipsorcery [~sipsorcer@2a02:8084:6180:500::12b] has quit [Ping timeout: 272 seconds] 01:57 -!- sipsorcery [~sipsorcer@2a02:8084:6180:500::12b] has joined #bitcoin-core-builds 04:15 -!- z9z0b3t1c [z9z0b3t1c@gateway/vpn/protonvpn/z9z0b3t1c] has joined #bitcoin-core-builds 04:18 -!- z9z0b3t1_ [z9z0b3t1c@gateway/vpn/protonvpn/z9z0b3t1c] has quit [Ping timeout: 246 seconds] 07:22 -!- sipsorcery [~sipsorcer@2a02:8084:6180:500::12b] has quit [Ping timeout: 240 seconds] 08:37 -!- z9z0b3t1_ [z9z0b3t1c@gateway/vpn/protonvpn/z9z0b3t1c] has joined #bitcoin-core-builds 08:40 -!- z9z0b3t1c [z9z0b3t1c@gateway/vpn/protonvpn/z9z0b3t1c] has quit [Ping timeout: 246 seconds] 08:47 -!- sipsorcery [~sipsorcer@37.228.225.67] has joined #bitcoin-core-builds 09:33 -!- sipsorcery [~sipsorcer@37.228.225.67] has quit [Ping timeout: 256 seconds] 12:37 -!- sipsorcery [~sipsorcer@37.228.225.67] has joined #bitcoin-core-builds 12:51 -!- z9z0b3t1c [z9z0b3t1c@gateway/vpn/protonvpn/z9z0b3t1c] has joined #bitcoin-core-builds 12:54 -!- z9z0b3t1_ [z9z0b3t1c@gateway/vpn/protonvpn/z9z0b3t1c] has quit [Ping timeout: 244 seconds] 12:55 < hebasto> when building `secp256k1` as a subtree in bitcoin repo, the `SECP256K1_API` macro is always defined to an empty string, which effectively disables `__attribute__ ((visibility ("default")))`. That is not the case when building `secp256k1` in its own repo. My Q is how does it work in the former case because I cannot see how bitcoin Autotools build system modifies `secp256k1` build system? 12:55 < hebasto> ^ real_or_random fanquake 15:40 -!- sipsorcery [~sipsorcer@37.228.225.67] has quit [Ping timeout: 246 seconds] 15:44 -!- sipsorcery [~sipsorcer@37.228.225.67] has joined #bitcoin-core-builds 16:00 -!- sipsorcery [~sipsorcer@37.228.225.67] has quit [Remote host closed the connection] 16:01 -!- Guest53 [~Guest53@2405:8d40:cf0:6b15:b64a:81a2:31c2:9fae] has joined #bitcoin-core-builds 16:02 -!- Guest53 [~Guest53@2405:8d40:cf0:6b15:b64a:81a2:31c2:9fae] has quit [Client Quit] 17:05 -!- z9z0b3t1_ [z9z0b3t1c@gateway/vpn/protonvpn/z9z0b3t1c] has joined #bitcoin-core-builds 17:08 -!- z9z0b3t1c [z9z0b3t1c@gateway/vpn/protonvpn/z9z0b3t1c] has quit [Ping timeout: 256 seconds] 17:46 -!- koolazer [~koo@user/koolazer] has quit [Read error: Connection reset by peer] 21:15 -!- z9z0b3t1c [z9z0b3t1c@gateway/vpn/protonvpn/z9z0b3t1c] has joined #bitcoin-core-builds 21:18 -!- z9z0b3t1_ [z9z0b3t1c@gateway/vpn/protonvpn/z9z0b3t1c] has quit [Ping timeout: 244 seconds] 21:22 -!- meshcollider [meshcollid@meshcollider.jujube.ircnow.org] has quit [Ping timeout: 248 seconds] 21:54 -!- meshcollider [meshcollid@jujube.rpblc.net] has joined #bitcoin-core-builds --- Log closed Sun Jun 05 00:00:43 2022