18000+ entries in 0.038s
mod6: no worries atm. but yeah, awesome work. thanks for doing that
mod6: so eventually we could even have this with like V too right? or just let trinque's makefiles do the heavy lifting with V there i guess too.
mod6: heeey this is really neat 'RUN echo "Building Daemon" \ ... && wget <URL_TO_FOUNDATION>/v0.5.3...tar.gz \ ...'
mod6: jurov: ya, saw that. the system is confused about which compiler to use i think.
mod6: guruvan: really? cool!
mod6: i wanna send a bunch of more txs to the foundations addy and debug while im doing that.
mod6: couldn't even make an a.out
mod6: the main issue is here, that i mainly just use this instance for build tests & full-sync tests. but the debugging i wanna do now, requires a fully syncd chain.
mod6: i think it's ok. i'll probably just shut down this instance, detach the volume, fire up my old deb instance and debug on that.
mod6: guruvan: yeah, i guess that buildroot must hvae used 4.8.4 to build the 4.9.x with musl that buildroot uses.
mod6: # gcc-config -l [1] x86_64-pc-linux-gnu-4.8.4 *
mod6: or.. related to that. i /know/ the compiler itself works, because i just recompiled bitcoind lastnight on here. but i dunno, seems like buildroot somehow hijacked the systems gcc and how is rendered defunct?
mod6: CC='/mnt/btc-dev/rotor/toolchain/usr/bin/x86_64-therealbitcoin-linux-musl-gcc'
mod6: guruvan: hey thanks, yeah i think after looking at the config.log output it's because of this:
mod6: configure: error: cannot run C compiled programs.
mod6: checking whether the C compiler works... configure: error: in `/var/tmp/portage/sys-devel/gdb-7.10.1/work/gdb-7.10.1':
☟︎ mod6: to get the level of detail required for that, it'd probably need to be 50' high. all the better. :D
☟︎ mod6: ;;later tell pete_dushenski pretty neat ice scuptures. i'd like to see an ice sculpture of a guy with a sharpie in pooper.
☟︎ mod6: hey cool, its building gdb now :}
mod6: get your rags ready
mod6: running a `emerge --sync` now.
mod6: maybe this is the problem: * Last emerge --sync was 188d 1h 7m 43s ago.
mod6: >>> Failed to emerge sys-devel/gdb-7.7.1
mod6: ... bunch of can not find ur thing ...
mod6: emerge sys-devel/gdb
mod6: in other news, this is annoying:
mod6: oh, fair point Mr. Vulpes.
mod6: *contributions! even.
mod6: Thank you for your services and contribution, Sir.
mod6: <+mircea_popescu> jurov did the foundation ever spend anything, i forget. <+ben_vulpes> foundation spend << not to date << technically we have made one expenditure, paying jurov his yearly fee.
mod6: when i drive, i sound like i have tourettes im sure.
mod6: looks like BIP 66 diffs reflect a bunch of der sig checking
mod6: i basically dropped that code into the Sign() { } function in key.h and am just looking at that atm...
mod6: to bring the interface back up `ifconfig <iface> up`
mod6: so, start up bitcoin, to disconnect your internet connection just do a `ifconfig <iface> down`, then see
mod6: <+thestringpuller> yea it exited when the connect failed << would someone like to test this & log their results so we can put this one to bed? basically should be able to start up bitcoind, run a `ps ax`, `netstat -an` and an `ifconfig`, then a `./bitcoind stop`, then the `ps ax`, `netstat -an` and `ifconfig` again to see whats happening - perhaps even a tail of the last 100 lines of the debug log...
mod6: I think I've got those R & S values picked out correctly, right? Anyone have any thoughts on this?
mod6: I've made a patch to remove high-S, added in patch, recompiled, restarted bitcoind and then sent a tx. here's what I'm looking at from a dumpblock of that tx:
mod6: who's up to speed on DER?
☟︎ mod6: <+pete_dushenski> bbias. have to move car underground. it's going to be -33c overnight... << -27.4 F, yep, that'll chill ya out. makes for pretty hard & fast ice tho. so there's the upside there.
mod6: <+BingoBoingo> Because what other ports should it have open? << you should only open incoming port 8333 when you want people to connect to your node to sync ~from you~
mod6: iirc, to fully sync a node /before/ -verifyall or orphanage burner were even a thing, took me ~8-10 days on a medium sized AWS server. now its a bit longer with those two in play.
mod6: ;;later tell PeterL Sorry, just missed you there. Thanks for your patience and efforts to build! We'll get through it.
mod6: and additionally, this cuts out SKS.
mod6: that way when someone wants to get going with V, they can find the keys without having to dig through 6 blogs.
mod6: but... maybe it'd be useful to put the links to our exported, ascii armored keys in the assets wiki?
mod6: ben_vulpes: so yah, having the keys on blogs/homepages isn't a bad idea.
mod6: getting it resolved... he's on a i686 env.
mod6: trying to get there... just a zillion things to work on :(
mod6: my apologies. what exists on the website is meant to help someone build v0.5.3.1 -- the rest of this stuff is basically as-of-yet-unreleased.
mod6: ./v.pl p verbose TEST2 asciilifeform-programmable-versionstring.vpatch
mod6: and change it to this:
mod6: ./v.pl p verbose TEST2 asciilifeform_add_verifyall_option.vpatch
mod6: if you want it to do so, you'll need to edit this line:
mod6: and... like i said, create a new dir, drop this script in there and run it -- but be aware that if left unchanged from the original, it'll not build alf's latest two patches in when pressing the source out.
mod6: but this is the one
mod6: thanks, couldn't find it on deedbot though
mod6: is there a way to search the deeds in deedbot?
mod6 is still digging in the logs.
mod6: you need buildroot+everything to build the static binary.
mod6: <+PeterL> ok, I used v to get the source, then what do i do with the source to build it? << the latest build script will do all of this for you ~except~ creating your ~/.wot directory with the appropriatly named keys placed in the directory.
mod6: it just pulls down the vpatches, and inflates the source tree from zero.
mod6: so, V doesn't actually do any building at all.
mod6: oh yeah. that's very old. lemme dig up the latest one.
mod6: i'd try creating a new dir somewhere, putting the build script in the new dir, and then running it again.
mod6: ok, so trying to run that script more than once might cause some pain.
mod6: no, i don't think it's linked. it's not 'official' at this point -- just a thing I put together to build the full orchastra and pull & press src with V.
mod6: did you try to run this script more than one time?
mod6: PeterL: hi, are you using the v99997 build script?
mod6: <+mod6> PeterL: Hey, glad you got it resolved! << should have put this in a later tell, sorry.
mod6: PeterL: Hey, glad you got it resolved!
mod6: <+pete_dushenski> cheers to mod6 for his assistance in applying stan's last two patches ! << glad you got it working, Sir. =]
mod6: pete_dushenski: yup, how goes it?
mod6: ;;later tell PeterL I guess also, if that doesn't resolve the issue, there could be something weird going on with your gpg import. might have to investigate more with you.
mod6: ;; later tell PeterL hey, the version of 'v.pl' that you have looks correct to me. the issue is that you have the pubkeys named incorrectly, try with 'mod6.asc', 'ben_vulpes.asc', 'asciilifeform.asc' and 'mircea_popescu.asc'
mod6: now i will look at PeterL's issue.