23500+ entries in 0.058s
mod6: then place auto.sh in the same directory as 'bitcoin', then execute.
mod6: oh, I see what you did. heheh. Yeah, you need to have a directory of patched v0.5.3.1 source in 'bitcoin' first.
mod6: Yeah, I linked the auto.sh script (v0.0.5) + signature to the website.
mod6: I still don't follow.
mod6: Anyway, if x32 ( I remember this had problems last week ) I'd be awesome if you could execute: `readelf --dynamic bitcoin/src/bitcoind`, but you have to have bitcoind built first.
mod6: What arch are you on x32|x64?
mod6: danielpbarron: hi, so it looks like you built OpenSSL, BDB and Boost I'm guessing by the look of that log file? Now it looks like you need to compile bitcoin v0.5.3.1
mod6: ben_vulpes: ok good deal! i'm about to post the lastest version of the perl build script too -- which should pull v0.0.2 of the static-makefile patch.
mod6: jurov: are you here?
mod6: ;;later tell jurov The mailing list is still snarffing messages. The dns fix didn't seem to help.
mod6: mircea_popescu: ok thanks!
mod6: <+mircea_popescu> incidentally, i wonder if one could make a filesystem specifically for blockchain storage. << i definately wanna discuss this.
mod6: asciilifeform: this is the device you ordered?
mod6: jurov: still doesn't seem to be working.
mod6: <+jurov> mod6 sorry, dns problem, fixed << ahh, awesome. not a problem. Thanks!
mod6: jurov: not even a test email made it through.
mod6: ;;later tell jurov btc-dev mailing list is snarffing messages again
mod6: jurov: i don't think the mailing list is working. it has snarffed 2 different messages from me so far today. i know the sigs are good on each & attachments.
mod6: had 2 attachments, a .patch file and a .sig file
mod6: jurov: can you see if a message got snarffed from the btc-dev list, i sent one in with the subject "Static Makefile Patch v0.0.2"
mod6: <+mircea_popescu> mod6: im glad we're all trying this now. << kinda the advantage of doing stuff here. << true enough :]
mod6: im getting laaaaaged
mod6: i think 33 was "-l w"
mod6: danielpbarron: it would have been like line 34
mod6: then going forward, we'll add in more conditions into these things to account for various platforms/configurations
mod6: or at least once we have a "freeze"
mod6: decimation: i think, in interest of time.. perhaps (with your help/testing) we'll post a patch for the makefile & the auto.sh post release.
mod6: you too. many thanks.
mod6: still have a moutain of work ahead, but we're on a good track.
mod6: this was highly productive tonight; I thank you all who helped!
mod6: i'll do some more sync testing once I get the changes we found tonight resubmitted to the mailing list.
mod6: that bitcoind does run and start pulling blocks btw too
mod6: so i'll re-submit that makefile patch and what will be v0.0.5 of the mod'd pogo script (with 'no-dso')
mod6: well, that's good to know i guess in case of RH
mod6: alright gents, i added 'no-dso' to the openssl configure and removed "- dl" from the makefile, and it compiled just fine:
mod6: asciilifeform: it is certainly /strange/ that this problem occurs right after the last checkpoint in our version.
☟︎ mod6: ok, sweet, i'll give that a try now.
mod6: decimation: so no-dso gets passed to the openssl build?
mod6: ahh, my bad. sorry I didn't clairify
mod6: no, not yet. i've been focused on just getting a release out.
mod6: well, it was 0.9.8o that was giving us the issues with the tx in the 168`001 block
mod6: pre-heart bleed? like 0.9.8o or whatever?
mod6: which works, because those are just warnings. it does output a bitcoind in the bitcoin/src dir
mod6: ok if i re-add back in "-l dl" into the makefile, then I get this:
mod6: at some future point, we'll get the crypto libs built in directtly.
mod6: <+asciilifeform> see fellas, when i said, 'hey hey ho ho openssl has got to go' << I'm with you .
mod6: danielpbarron: oh you're running this on ARM? this won't build on arm probably.
mod6: danielpbarron: i think you have some other issues going on probably.
mod6: i'll know in a minute.
mod6: cant recall for sure though
mod6: i wanna say that i ran into that as well.
mod6: i'll have to figure out what needs to be different in the 32 bit version.
mod6: ok thanks danielpbarron.
mod6: hrm. ok, i'm gonna try building without -l dl and -l z
mod6: yeah, it's like 60mb or something.
mod6: i haven't compiled on a 32bit system yet so this is a great test.
mod6: thanks, that's good. i'll have you do a `cd bitcoin/src ; readelf --dynamic bitcoind` when its complete.
mod6: yeah, that works too. cool
mod6: ah! ok good to know.
mod6: i don't even own or use a M$ machine, so it has to be the paste sites.
☟︎ mod6: so ... i guess perhaps we try with dpaste and see.
mod6: yeah, pastebin sticks on CRLF's... like a derp
mod6: one sec, i'll get you a new one. pastebin fucked us.
mod6: im glad we're all trying this now.
mod6: danielpbarron: try editing the script and getting rid of the -xu thing after /bin/sh
mod6: there's a realpath bin you can install iirc
mod6: yeah, that's required from the original pogo script.
mod6 looks at danielpbarron's paste
mod6: yeah, that's its default behavior. if you don't want it to delete the stuff, just change $FULL_CLEAN to "FALSE"
mod6: oh crap, lol, i didn't change the $BUILD_DIR back to "CHANGEME" derp
mod6: s/--lock--never/--lock-never/
mod6: also removed $HOME for $BUILD_DIR
mod6: decimation: nice find!
mod6: hmm. noted. thanks decimation