Matches for rotor, 360 total results Sorted by newest | relevance
Mon Jan 11 18:57:57 UTC 2016 <ascii_butugychag> http://log.bitcoin-assets.com/?date=11-01-2016#1366935 << and rotor is..?
Mon Jan 11 16:23:25 UTC 2016 <ascii_butugychag> (recall when we diffed rotor builds ??)
Mon Jan 11 15:42:38 UTC 2016 <mircea_popescu> how does v currently know where to connect to build the rotor ?
Mon Jan 11 15:40:21 UTC 2016 <assbot> Logged on 11-01-2016 15:37:56; mircea_popescu: jurov im thinking more like a rotor script to build a local hosts out of, maybe, deedbotted things ?
Mon Jan 11 15:37:56 UTC 2016 <mircea_popescu> jurov im thinking more like a rotor script to build a local hosts out of, maybe, deedbotted things ?
Mon Jan 11 01:42:57 UTC 2016 <asciilifeform> i wrote 'rotor', which lets you build for nintendo if you like.
Mon Jan 11 01:32:36 UTC 2016 <asciilifeform> actually rotor doesn't give a damn what you build on, so long as it is specified
Sat Jan 09 14:08:40 UTC 2016 <thestringpuller> i'm compiling on the same machine I'm running it on. did the whole stator+rotor build here
Fri Jan 08 23:54:14 UTC 2016 <trinque> http://deedbot.org/trb-mk.tar.gz http://deedbot.org/trb-mk.tar.gz.asc << mod6, asciilifeform, ben_vulpes, et al., this thing has crapped a working trb enough times to get feedback. It's a set of makefiles for the former build script and rotor. There are interesting knobs in the various makefiles, including (I think) an easy way to put other builders alongside rotor (as asciilifeform mentioned). Lemme
Fri Jan 08 23:47:51 UTC 2016 <asciilifeform> go compile rotor.
Mon Jan 04 21:22:10 UTC 2016 <thestringpuller> rotor also blew up in my face on debian wheezy
Mon Jan 04 03:57:44 UTC 2016 <asciilifeform> (locally, a la rotor, is another matter, and works great for its purpose)
Sat Jan 02 14:01:13 UTC 2016 <assbot> Logged on 02-01-2016 04:57:20; thestringpuller: ugh all these expired keys is making it impossible to build rotor with the old script
Sat Jan 02 05:43:22 UTC 2016 <mod6> anyway, yeah, this is the build script that I created for testing the build of 'rotor', TEST2, and the static binary.
Sat Jan 02 05:33:40 UTC 2016 <phf> i understand all that, and i was explaining that there's no conceptual integrity to it, as it stands. we have a .wot folder which is supposed to be a manually curated folder of <nick>.asc files. there were a few threads where mp and ascii argued that the folder should not be generated automatically (no sks or pre packaged tar files). so if one wants to build a rotor they need a .wot folder with pubkeys of all the foundation
Sat Jan 02 05:22:11 UTC 2016 <mod6> buiroot is not v-ifiable. so in the rotor+TEST2 build script it was decided (in here) that we should check the hashes and the signatures.
Sat Jan 02 04:57:20 UTC 2016 <thestringpuller> ugh all these expired keys is making it impossible to build rotor with the old script
Thu Dec 31 19:59:36 UTC 2015 <mod6> alright cool. mind if I ask which rotor+TEST2 script you're using?
Thu Dec 31 19:51:58 UTC 2015 <mod6> pete_dushenski: are you trying to build rotor+TEST2 on i686? (sorry, i'm kinda coming in the middle of this convo.)
Thu Dec 31 19:41:17 UTC 2015 <assbot> Logged on 22-12-2015 04:58:44; 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-9999