12900+ entries in 0.027s
mod6: so, im not 100% off the top of my head, but getting rid of the two rotor build script and integrating that portion into our makefiles ~might~ resolve at least part of the source redundancy issue.
mod6: oh yeah, we're not reall messing with any of that stuff. stator hasn't been a part of the 'orchastra' for some time now.
mod6: the two .sh scripts you have in there can be integrated into the makefiles directly i think. however, we'll still need the openssl-004-musl-termios.patch and rotor_buildroot_dot_config
mod6: oh, if you're saying that the rotor is no longer needed, i can agree with that. to an extent anyway.
☟︎ mod6: When you come back, maybe we can discuss what you're trying to exactly say.
mod6: I can't make heads or tails out out of what you're saying there asciilifeform.
mod6: Altogether, since we have V, I like the idea of keeping things like makefiles and buildscripts out of the main source tree. One can get V, press the makefile project. Run a `make`, which will in-turn, press everything via V and then build with buildroot.
mod6: I think that keeping the Makefiles as a separate V tree would keep things a lot more clean.
mod6: Anyway, I bring this up because if we're determined to stick with this plan; the Makefiles included with the bitcoin source, then there is another ball of wax that needs to be discussed.
mod6: this is because the makefile process does it's own V press.
mod6: The problem is here, that when you run `make`, it'll build everthing under: build/rotor/TEST2/bitcoin/src despite the fact that the source is really under src/
mod6: And we haven't discussed it since.
mod6: We discussed this, it was Mr. P.'s hunch that these should belong together (I hope I'm remembering this correctly), and I saw the wisdom in that.
mod6: It was my first hunch, during a pre-emptive go around with this to not place the makefiles in with current source base -- as pressed out via V.
☟︎ mod6: And in doing so, it kinda brings us back to a previous discussion.
mod6: We are pretty much at the point of starting V-ify these makefiles.
mod6: <+mircea_popescu> tell you what, if we're ever shipwrecked on a deserted island with hillary, we'll fuck hillary. << think she coughs now? wait until she chokes on all that dick!
mod6: <+asciilifeform> we burned it out of trb with hot irons, first thing, for a reason. << werd. thx.
mod6: yeah, alright, i'll take a look.
mod6: so forget that maybe.. just wondering if anyone has tried this before?
mod6: yeah, im not super clear on the whole thing.
mod6: alf, you ever attempt anything like this?
mod6: there are some projects out there seems like, in this vein.
mod6: so yesterdays discussion got me thinking about a lisp machine (lisp-cpu) with verilog on a fpga
mod6: is there a way to search the logs from one of these bot?
mod6: ah, mircea_popescu, maybe i'm wrong then; in that sense of "models"
mod6: <+mircea_popescu> anyway. point being the situation's windy rather than calm. << agreed.
mod6: ya. but alas, not a different computational model; just new hardware. non-usg shit.
mod6: i very much doubt this is their long term strategy.
mod6: they just need to stab "wintel"
mod6: well, they probably don't need a new model of computation.
mod6: i agree mircea_popescu
mod6: This sort of leads us back to the original question: to Ada, or not to Ada.
mod6: help africa, give them fb!
mod6: So again, eventually.
mod6: not that I'm saying "i'm going to write a tmsr compiler this year."; however, seeing the need for this years ago, having one written by us that we can trust, is a worthwhile project. i've taken steps in this direction by doing some very much required reading on the subject.
☟︎ mod6: it's just what we currently are shackled with. chains will be broken.
mod6: <+mircea_popescu> but you don't know it. <+mircea_popescu> no one does. << indeed, Sir.
mod6: but better the devil you know...
mod6: <+trinque> and you trust gcc? << lol. f no.
mod6: tmsr will probably, eventually, have to write its own translater/compiler.
mod6: fact remains, i couldn't trust it, any farther than I could throw it.
mod6: that seems more like a condemnation to me. they make a lot of things that "work". what of it?
mod6: maybe review should be left as an exercise for us all
mod6: maybe i should have said "technical critque". anyway, he probably doesn't have the time. i'd hate to distract him from the one big project he's working.
mod6: well, this, of course. comes from shitgnomes, et. al.
mod6: alf would you be willing to write up a critque/review of llvm/clang in your blog -- something that rounds up the previously stated?
mod6: i think alf has said a number of things about it in the logs.
mod6: results within a day or so, which is very very helpful.
mod6: one thing that's pretty nice, is that he seems to be readily available when I've got something to test
mod6: <+mircea_popescu> mod6 guy that started as a tester a year ago is now qualified to the point of check him out huh! << yeah! pretty helpful over the last year to have a dedicated individual such as shinohai to help specifically test. and yeah! seems to be a handy bot mechanic.
mod6: yeah might take some time to get it into storage, but same thing if you got 65 tons of quarters from a slot machine.
mod6: <+mircea_popescu> mod6 here's something to blow your mind : noob kid in eulora dug up an ord sr claim of mine ; got 65k sr. he's dragging it to town, 1k at a time. he's calculated it'll take him ~4 hours. << that's an awesome jackpot though!
mod6: lol, apparently so.
mod6: lol. +5%. go jump in a lake.
mod6: Thanks, Sir. I like it!
mod6: ah, i saw something about that. it said: DRUG DEALERS LOVE THIS!
mod6: uh. i doubt it. can't speak for other tho.
mod6: thanks for all the help, much appreciated. :]
mod6: shinohai: ah, ok great. just wanted to make sure.
mod6: <+hanbot> hey mod6 99994 test worked flawlessly for me tonight. also, my testbox seems healthy again, available for further whatevers. << hey! good deal, thanks for giving it a shot :]
mod6: eitherway, works to bridge the gap until that part is complete.
mod6: see, now, we have two different scripts; one to build while pulling items from the inet, and one for offline builds; the makefiles will combine these two capabilities.
mod6: needs some polishing, and an appropriate vpatch and such, but yeah, we're close.
mod6: makefiles. i just tested my changes with the deeds in place. works.
mod6: it's about to be moot very soon i think :]
mod6: oh, and with those turn of the century disks; after grinding them down with the sanding block -- they're like solid aluminum. so i cut them into tiny pieces with these:
mod6: i'm a bit conflicted; but it might still be some work until the makefiles are fully baked.
mod6: so it might be moot, soon.
mod6: and I'm gonna put it out there shortly. but just got a long distance in a short a mount of time working on these makefiles today.
mod6: ok, so I have this offline build script ready to go.