23900+ entries in 0.057s
mod6: but you need to really watch out for 168,001
mod6: the checkpoint block is 168,000
mod6: it'd be awesome because then derps would give up and go and play with hula-hoops
mod6: just relating that im indeed against distribution of binaries
mod6: thanks for testing!
mod6: maybe throw a `uname -a` in there as well
mod6: if you do get that, please give us a pastebin of the 'getinfo' & 'openssl version -a'
mod6: youll know that you've hit the bad tx when you see an error in getinfo like this: "errors" : "WARNING: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade."
☟︎ mod6: ok 0.9.8o is the version we had problems with too though
mod6: better to watch `tail -f /path/to/.bitcoin/debug.log` to see whats really actually happening.
mod6: so just be aware of that -- sometimes it can take a /while/ to respond.
mod6: sometimes you do a 'getinfo' and its "busy" doing "SetBestChain" or something similar.
mod6: run this: `openssl version -a`
mod6: you hit it on your linux box?
mod6: yeah, the latter. i wouldn't worry about it.
mod6: but, will set up a different vm for this later
mod6: shouldn't be too long before i get to where i want to be. i can't even do full sync on this vm anyway. i didnt make the vm disk big enough.
mod6: ok im off and running again
mod6: <+punkman> and you can move the binary to other machine without having to pull all the boost-dev packages << fwiw, i've never done this ever. should always rebuild binarys on the local environment.
mod6: so when the dynamic compile is done here, will start back up.
mod6: An adventurer is you!
mod6: this one uses LibreSSL 2.0
mod6: that was on linux w/openssl v0.9.8o
mod6: ah, no. but recently had issues with VerifiySignature on a tx in block 168,001
mod6: i gotta recompile (linking dynamically) and see if I can get past 168,001
mod6: so are you running v0.5.3.1 or .7.2 ?
mod6: after that thing blew up i was like, time for bed.
mod6: statically linking the libs into the bitcoind output binary made it cross its eyes and wet its pants lastnight
mod6: well, thats all for me.
mod6: [1] + Segmentation fault ./bitcoind -datadir=/home/mod6/.bitcoin -daemon (core dumped)
mod6: its like ~10mb larger
mod6: alright, and yeah, the output binary is way bigger:
mod6: ok here we go, one more time
mod6: i thought the IFDEF should do that
mod6: oh LMODE2 didn't get set.
mod6: this in one place: -Wl,-Bstatic : this in another: -Wl,-Bdynamic
mod6: i still don't think i did the right thing there..
mod6: "LMODE", not "LDMODE"
mod6: im not sure if that worked
mod6: well, i think im just tired.
mod6: i'll rebuild with STATIC and see
mod6: thestringpuller: thanks for testing that script tonight
mod6: gotta add a patch for that stuff
mod6: i thought the warings at the end of the openbsd compilation were rather lulzy
mod6: i think a lot of em are, yeah.
mod6: An adventurer is you!
mod6: its hairy in there.
mod6: red ring + magical sword & shield required.
mod6: mutual exlusion semaphore
mod6: one sec, lemme find this /. post & artcile i was reading.
mod6: so, the funny part is, as the story goes, most of what is in boost was put into the 2011 standard.
mod6: punkman: yeah, there's a bunch of work to be done surrouding openssl/libressl
mod6: 7th checkpoint passed
mod6: 6th checkpoint passed
mod6: s/autoremote/autoremove/
mod6: one thing that sucks about this version of bdb 4.6 is that it doesn't support my database flag to autoremote the database transaction logs : dbenv.log_set_config(DB_LOG_AUTO_REMOVE, 1);
mod6: passed 3rd checkpoint..
mod6: obsd v0.5.3.1 got past first 2 checkpoints: "version" : 50301, "blocks" : 42307,
mod6: asciilifeform: that look better?
mod6: that's fine. i kinda was thinking trying to statically link the libs was giving me an issue. forgot to add it back in.
mod6: ah. i'll add it back in. no prob. just wanted someone to look over my shoulder on that part.
mod6: (this is on debian 6)
mod6: i'll formalize this stuff in the next few days and get it on to the list.