522 entries in 0.781s
punkman: we maybe could have bug-to-bug compatibility between bitcoinds built with
rotor, but otherwise when did bitcoind have bug-to-bug compatibility across versions of itself, openssl, bdb, etc
assbot: Logged on 29-08-2015 20:47:31; mod6: ;;later tell davout You did test out
rotor w/TEST2 or stator this month right? Or did I mis-remember that?
mod6: but built with
rotor, cool. what OS?
danielpbarron: Bitcoin version 0.5.4-beta << I'm currently running this, made with the
rotor instructions
mod6: yup, that's required on every system that i've encountered when built with the `
rotor'.
mod6: ;;later tell danielpbarron You did test out
rotor w/TEST2 or stator this month right? Or did I mis-remember that?
mod6: ;;later tell jurov You did test out
rotor w/TEST2 or stator this month right? Or did I mis-remember that?
mod6: ;;later tell punkman You did test out
rotor w/TEST2 or stator this month right? Or did I mis-remember that?
mod6: ;;later tell davout You did test out
rotor w/TEST2 or stator this month right? Or did I mis-remember that?
☟︎ hanbot: in latest ml adventure,
rotor-test2 for i686 makes a static bitcoind that gives sigill w/ LC_ALL=C (and won't run w/o it):
http://dpaste.com/0J6HXAH assbot: Logged on 23-08-2015 17:32:45; mod6: my
rotor+TEST2 has fully sync'd on gentoo. (3rd full sync with -verifyall)
mod6: my
rotor+TEST2 has fully sync'd on gentoo. (3rd full sync with -verifyall)
☟︎ mod6: hanbot is testing out my i686 changes for buildroot/
rotor.sh - even got a script for it. so that's p-cool.
danielpbarron:
rotor feels like a "safe space" to borrow some redditard terminology
danielpbarron: btw I got stator to build with the
rotor toolkit and it is currently syncing and up to 153k blocks
BingoBoingo: joecool: With the anticipated spam attacks ideally you will want to bolt the Ophanage amputation and thermonuke modifications to whatever you choose. Also make sure you fix the BDB locks problem in your chose codebase. Anything post 0.3.21 and pre 0.8 should be fine. If you don't have particular things you fuss over 0.5.4'stator/
rotor' is probably as close to idea as you will come
mod6: another crazy thing is this BDB configure script. i got
rotor to build on i686 with TEST2. but the crazy thing is that it seems to compile just fine when BDB has --host=x86_64-linux OR --host=i386-linux but NOT without a --host=<SOMETHING>
hanbot: "orchestra" supercedes "
rotor" which supercedes "stator", and the v versioning system is usable (as-is) for "orchestra" only, correct?
mircea_popescu: <Adlai> so where do i begin with this bitcoin thing? << get stator/
rotor going, is a start.
thestringpuller: make[2]: Leaving directory `/home/thestringpuller/real_bitcoin/
rotor/buildroot-2015.05/output/build/host-gcc-initial-4.9.2/build/gcc'
assbot: Logged on 11-08-2015 19:12:55; hanbot: shinohai: hanbot compiled pogo ? O.o << nein. have built stator "manually" as of last night, tho still need to verify runs as expected, after which will put together notes. have not pogo-ed,
rotor trial to come. (ubuntu 10.04 32bit + mod6's gracious help)
mod6: So, if anyone wants to try out these automated cucumber tests on v0.5.4-TEST2 w/
rotor ; I have some recipes that work on: ubuntu 10.04, deb6/7/8 and gentoo. Just send me a PM and I'll work with you on it.
cazalla: asciilifeform, in your
rotor guide, can you help me understand what step 6 asks me to do?
mircea_popescu:
http://log.bitcoin-assets.com/?date=13-08-2015#1237221 << upside is massive but hard to quantify. upside is that we HAVE FOUND THE HOLES IN GCC! upside is that we know what to say about linux, and why we're saying it. upside is that we have
rotor, and that we know why nobody without a
rotor has a chance. upside of a sane approach is never "where it gets you", but always "where it didn't take you".
☝︎ assbot: Logged on 13-08-2015 14:44:54; pete_dushenski: shinohai: wonder of wonder, miracle of miracles, i took
rotor by the hand, turned him around and - miracle of miracles - led him to the promised land !
funkenstein_: I must say the
rotor is a software release like no other I have seen, yes very deterministic
pete_dushenski: shinohai: wonder of wonder, miracle of miracles, i took
rotor by the hand, turned him around and - miracle of miracles - led him to the promised land !
☟︎ pete_dushenski: ben_vulpes: did you have any 'absolute path' issues when setting up coracle ? i still haven't overcome this issue with my
rotor attempts
shinohai: the new
rotor script mod6 and I tried this weekend past is so easy a redditard could do it
hanbot: shinohai: hanbot compiled pogo ? O.o << nein. have built stator "manually" as of last night, tho still need to verify runs as expected, after which will put together notes. have not pogo-ed,
rotor trial to come. (ubuntu 10.04 32bit + mod6's gracious help)
☟︎ mod6: ascii_field: for people who'd like to build
rotor w/stator or
rotor w/TEST2 on i386/i686, is there anything special that they would need to do to this file? rotor_buildroot_dot_config
mod6: hey, if i build
rotor-TEST2 on say gentoo, and someone else builds the same whole thing on debian, we get the same number of output bytes in the bin, but the checksums are different, seem to be some offset differences.
TomServo: I'm probably too slow to be much use, but what are the current requests for testing? still TEST2? or
rotor?
TomServo: Effort better spent building
rotor?
ben_vulpes: asciilifeform: i did eventually succeed with the
rotor/stator combo
mod6: <+ben_vulpes> after much derping, i have a
rotor-built stator bitcoind << heeey! neat. :]
ben_vulpes: after much derping, i have a
rotor-built stator bitcoind
mod6: shinohai: you built successfully with
rotor-TEST2.sh on deb 8 right?
ben_vulpes: asciilifeform: is the untarred buildroot intended to live in toolchain or in the root of the
rotor directory?
mod6: funkenstein_: ok this is a new one for me. what are the detalis: debian 8, x86-64... ok. is this with the
rotor/stator hand build from ascii's guide with tea? or my thing I just posted a bit a go
rotor-TEST2.sh?
mod6: All: If you are going to build the
rotor-TEST2.sh on debian be advised that you may need the following installed: build-essential curl unzip python bc rsync
mod6: asciilifeform: only main change I had to make other than pulling down the TEST2 bundle itself was to add this: sed -i 's/bitcoin\/bitcoin\/src/bitcoin\/src/'
rotor.sh
mod6: ;;later tell pete_dushenski I have a script for you to try on Debian 7 to build TEST2 with
rotor. You might need to install a few minor pre-reqs. I can hold your hand if required for that part. Let me know when you have some time.
mod6: So Shinohai and I just got done testing my TEST2 bundle with
rotor script. We've built successfully on: Gentoo/glibc, Ubuntu 10.04, Debian 6 and Debian 8 :: All x86_64
pete_dushenski: punkman: what would be 'something that works' for line 49 of
rotor.sh ?
punkman: and you can run rotor_bitcoin_only.sh now
pete_dushenski: i'm about as n00bing as they come around here and i still feel like i'm shockingly, wonderfully close to making
rotor work
punkman: open
rotor.sh, look at the filepaths
pete_dushenski just noticed asciilifeform's 'if you are having locale issues' note on '
rotor' buildsheet
pete_dushenski: asciilifeform: "copy my rotor_buildroot_dot_config to the now-untarred buildroot dir as '.config'" << speaking of which, i seem to be snagged up here. can't find 'rotor_buildroot_dot_config'
mod6: was a gentoo/glibc environement -- compiled buildroot with the musl settings. didn't change anything to the "
rotor" steps execept for adding the change to BDB configure options in trinque's message.
mod6: was nice to see
rotor build cleanly today btw.
mod6: once we have that, and a new patch from trinque, i can complete my script and have a
rotor that builds these test bundles with x86-64
mod6: ok. that's my next basic goal. build a patched bundle up through verify-all with
rotor.
mod6: was thinking that next I'll work on a patched bundle up through -verify all with
rotor. and then work ourselves up to a place where we feel comfortable.
mod6: asciilifeform: so, what my goal is, short term, is to produce a bundle that (similar to TEST2) is patched up through -verifyall that we can drop into the
rotor, and use that for testing next.
mod6: pete_dushenski: don't bother with the testing for TEST2 (or anyone else), just work for now on building
rotor.
mod6: Right, should be trying to bulid the
Rotor, really.
pete_dushenski: asciilifeform: i know you wrote
rotor for a reason, of this there is little doubt, but believe it or not, your instructions aren't dumbed down enough for me