[00:00:01] @prole @mxaddict [09:57:54] nice [09:58:09] has anyone compiled on 16.04 lately? i can't get it to work on my first attempt [09:58:33] depends are built [09:59:56] ./autogen.sh ./configure --prefix=/home/navworker/navcoin-core/depends/x86_64-pc-linux-gnu make [10:00:13] Making all in src make[1]: Entering directory '/home/navworker/navcoin-core/src' make[2]: Entering directory '/home/navworker/navcoin-core/src' CXXLD navcoind /usr/bin/ld: libnavcoin_consensus.a(libnavcoin_consensus_a-blake.o): relocation R_X86_64_32 against `.rodata' can not be used when making a shared object; recompile with -fPIC libnavcoin_consensus.a: error adding symbols: Bad value collect2: error: ld returned 1 exit status [10:00:13] Makefile:3871: recipe for target 'navcoind' failed make[2]: *** [navcoind] Error 1 make[2]: Leaving directory '/home/navworker/navcoin-core/src' Makefile:9827: recipe for target 'all-recursive' failed make[1]: *** [all-recursive] Error 1 make[1]: Leaving directory '/home/navworker/navcoin-core/src' Makefile:704: recipe for target 'all-recursive' failed make: *** [all-recursive] Error 1 [10:00:24] is this the disable hardening flag i need yeah? [10:02:09] seems like it [10:02:33] ./configure --prefix=/home/navworker/navcoin-core/depends/x86_64-pc-linux-gnu --disable-hardening make seems to be continuing past the error [10:26:55] yup [16:35:38] @mxaddict @prole @salmonskinroll 2 new pull request to review, they fix the issues i've found when syncing from scratch https://github.com/navcoin/navcoin-core/pull/634 https://github.com/navcoin/navcoin-core/pull/632 I've also added a second dns seeder, and reenabled the first which was offline https://github.com/navcoin/navcoin-core/pull/633 [16:40:53] @aguycalled I don't have time to review these right now. I'll review tomorrow first thing. [16:40:57] Nice work by the way. [16:42:29] @aguycalIed about the gitian build, would it be possible to detect if there are changes to the depends? and only clear the depends dir if changes were made to it? [16:42:54] If not, then I might have to patch the depends functions to check for it. [16:43:29] id say once that branch gets merged to master the issue will be gone [16:43:48] when other branches are based on it [16:43:50] so maybe not worth it the extra effort [16:43:56] The reason why the depends functions are not able to handle this situation is because qt has multiple tar files and the default logic that checks this is only coded to check the main tar [16:44:12] So if the main tar file exists, but the other tars are missing, it fails to build. [16:44:38] Hmmm, yeah, I guess so, once the changes are merged into master the issue will be gone [16:44:44] Until we do the dao branch [16:44:57] As that also has changes to depends that will cause it to fail. [16:45:18] Yeah, might not be worth the effort as we don't usually make many changes to the depends anyway. [17:05:01] btw i've seen the pink button issue in catalina [17:06:01] https://cdn.discordapp.com/attachments/416000318149754881/646018283232821269/unknown.png [19:40:31] I've updated and reviewed a few of the PRs I'll get to the rest in the morning. [19:51:27] @aguycalled for the three new PRs, what would make syncing from scratch fail? if i launch a new sync with reindex=1, would i fail to sync? on what system? [19:52:08] i detailed in the issue in what systems i've seen it, but for -reindex i've seen it everytime [19:52:08] or just PR 632 [19:52:13] ok [19:52:36] when you launch with -reindex you need the wallet already synced [19:52:40] it can be from a bootstrap [19:53:15] gotcha [19:53:48] reindexing happens before syncing, so if u do it with a new sync it will do nothing [19:54:02] i see [21:11:48] im testing it but it takes forever to sync. im waiting for current release to reach 2762327, i mean it's already kinda stuck since it can't find headers after that. [21:11:57] https://cdn.discordapp.com/attachments/416000318149754881/646080172654592018/unknown.png [21:24:40] can you send me the debug.log file? [21:25:08] yeah, but i didn't have debug=1 i think [21:25:47] 2019-11-18 19:10:21 ERROR: AcceptBlock: cold-staking-not-enabled (code 16) [21:25:50] is at line 12408 [21:28:31] https://cdn.discordapp.com/attachments/416000318149754881/646084340308246530/debug_-_Copy.log [21:29:31] PM'd you [22:13:38] what binary are you running? @salmon3s [22:14:04] im running current release to reproduce the problem. [22:14:15] it's from the navcoin.org website i think [22:14:19] im on windows 10 [22:14:55] you are seeing the issue fixed in #632 [22:14:56] https://github.com/navcoin/navcoin-core/issues/631 [22:15:03] https://cdn.discordapp.com/attachments/416000318149754881/646096054294544384/unknown.png [22:15:35] yup, im just wondering if i need to finish the sync now to confirm it actually stucks at that block height or i should just use the newly built binary to confirm it's fixed [22:15:52] it won't sync further that block [22:16:02] without the fix [22:16:13] okay, i'll just close it then [22:16:28] will run it with the new binary by the bot now [22:16:42] perfect 👍