Matches for rotor, 360 total results Sorted by newest | relevance
Thu Dec 24 17:13:05 UTC 2015 <asciilifeform> (the ~4MB elf we get from a rotor run)
Thu Dec 24 17:02:37 UTC 2015 <trinque> so outermost makefile would do what this script is doing, then call a rotor makefile.
Thu Dec 24 15:00:24 UTC 2015 <asciilifeform> and also 'rotor' is a generalization of it
Wed Dec 23 18:03:26 UTC 2015 <ascii_field> about half of the 4MB rotor bin is openssl crud
Wed Dec 23 17:49:06 UTC 2015 <assbot> Logged on 23-12-2015 17:29:04; mircea_popescu: aaand in other news, the new rotor has been mightily blackholed since last night (the usual array described here multiple times), it's got ~20k blocks through in a day or so.
Wed Dec 23 17:29:04 UTC 2015 <mircea_popescu> aaand in other news, the new rotor has been mightily blackholed since last night (the usual array described here multiple times), it's got ~20k blocks through in a day or so.
Tue Dec 22 22:36:22 UTC 2015 <mod6> <+jurov> oh it's going to be all unpacked there? << yeah, perhaps not. currently i extract & build all that stuff under 'rotor'. i guess shit should just be: <+jurov> "The shit: BDB, Boost, OpenSSL & the MANIFEST for turds" <- this stuff the turdballs and the manifest.
Tue Dec 22 22:30:31 UTC 2015 <mod6> i think since that post, we talked about changing 'build' to 'rotor'. thoughts?
Tue Dec 22 21:14:59 UTC 2015 <mod6> I guess we can place a small README in bitcoin/ that can direct peeps to rotor dir.
Tue Dec 22 21:14:42 UTC 2015 <trinque> why rotor? is there going to be some other build system?
Tue Dec 22 21:14:26 UTC 2015 <mod6> i'm sold on that. s/build/rotor/
Tue Dec 22 21:14:10 UTC 2015 <ascii_field> i'd name 'rotor'
Tue Dec 22 20:38:36 UTC 2015 <mod6> the rotor is out of the scope of that part.
Tue Dec 22 20:37:28 UTC 2015 <mod6> <+mircea_popescu> my personal ideal would be that ALL directories involved in this without exception are spawned as subdirs of whatever current dir the script ran in. << this makes sense. right now you end up with /.../rotor/ and ~/.wot, and ~/.seals iirc.
Tue Dec 22 20:35:12 UTC 2015 <mod6> and the subsequent commands would just do something like `./v.pl p TEST2 vpatchnameforhead wd /.../rotor/.wot` or something.
Tue Dec 22 20:34:28 UTC 2015 <mod6> in the context of the script, it'd have to be altered in the script to say place the .wot in .../rotor so you'd have /.../rotor/.wot/
Tue Dec 22 20:32:35 UTC 2015 <mod6> currently, what is required is that you execute the rotor+V+TEST2 script that I wrote, and then it'll create a 'rotor' dir in that present working directory. then you'll end up with like: rotor/TEST2/bitcoin/src/
Tue Dec 22 20:30:24 UTC 2015 <mircea_popescu> mod6 could the default be that all dirs are made under whatever dir runs the rotor script ?
Tue Dec 22 04:58:44 UTC 2015 <mircea_popescu> anyway, for pete_d and anyone else who might have encountered difficulty with trb or fears they might : it's actually rather painless. 1. you create an account on a server ; 2. you cd /home/account_name ; 3. you create a .wot directory (mkdir .wot) ; 4. you put the pubkeys of people you trust in there as name1.asc, name2.asc etc ; 5. you download the rotor script (curl deedbot.org/build-bitcoind-99997K.sh > build-bitco
Tue Dec 22 00:57:22 UTC 2015 <mod6> I am following my exact instructions above ^^^ nearly done building a rotor+V+TEST2.