Hennadii Stepanov

Tracked in https://github.com/hebasto/bitcoin-core-nightly/issues/6.

> Edit: And where is your `libsqlite3.so.0` that it can't find? As a result of executing the `pkgin install sqlite3` [command](https://github.com/bitcoin/bitcoin/blob/master/doc/build-netbsd.md#descriptor-wallet-support), the library is installed in the `/usr/pkg`: ``` $...

> So the `ld` finds the lib to link against, but the runtime loader then can't find it? That seems absurd. > > > > Or is it because the...

Seeking early feedback from Android connoisseurs. Friendly ping @icota :)

> I'd say a CI task config should exist. Otherwise, there is no way to test the build easily for non-android people. No opinion on adding it to the live...

@maflcko > No objection, but assert/Assert seems to be used widely in the codebase, so shouldn't this be done for all test binaries, or none? Otherwise the same assert could...

Not related to this PR, but the [error in the `wallet_fees` target](https://github.com/hebasto/bitcoin-core-nightly/actions/runs/14801894543/job/41562322239#step:8:484): ``` wallet_fees: succeeded against 23 files in 0s. Run wallet_fees with args ['D:\\a\\bitcoin-core-nightly\\bitcoin-core-nightly\\build\\bin\\Debug\\fuzz.exe', WindowsPath('D:/a/_temp/qa-assets/fuzz_corpora/wallet_fees')] \u26a0\ufe0f Failure generated from...

> Not sure about compiler specific changes, that rely on the presence of an undocumented environment variable (which we don't explicitly set as far as I can tell?), to make...

> > It is documented, and it is pre-defined by CI itself: > > It's not in our docs, or in our CI code, which means our CI would "work",...

> > This does not apply to the "raw" GitHub Actions workflows, where this code takes effect. > > Can't someone just compile and run the same binaries locally? Certainly,...