asciilifeform: mod6 is the one who 100% automated asciilifeform's rotor builder; you may want to use his model, ~iff~ waiting for cuntoo is not permissible
asciilifeform: diana_coman: depending on how far cuntoo is from flight-readiness ( trinque , any idea ? ) this may be worth doing in your case
asciilifeform: i solved this same problem for trb -- i.e. building 100% musltronic proggy with '9000' deps , on a conventional box☟︎
asciilifeform: diana_coman: hence why i said 'rotor buildroot env'
asciilifeform: diana_coman: if you were making simply a musltronic version of euloratron, it could be done rotor-style (buildroot env) . but sounds like you want cuntoo straight away.
asciilifeform: http://btcbase.org/log/2018-06-21#1827977 << 're-emerge' seems to imply systemwide ? you're more or less guaranteed a borked box, muslism has to be done either rotor-style (i.e. 100% user-local build of 1 proggy at a time) or systemwide ( trinque's cuntoo ), on account of the impossibility of cleanly linking glibc libs to musl proggy or vice versa☝︎☟︎
asciilifeform: these are actually quite ancient, iirc early '80s performance given in house at hewlettpackard
asciilifeform: ( fwiw i have copy of the films , from decade+ ago , on cd )
asciilifeform: esthlos: i had nfi these were ever hosted on lolcattube to begin with
asciilifeform: pretty sure that gprbuild does not suffer from said idiocy, but this will have to be tested.
asciilifeform: 'build that iterates over the keys of a Perl hash will have problems, since these elements are also returned in a variable order' << perlism has gotta go.
asciilifeform: 'Unix doesn't specify an order in which readdir() and listdir() should return the contents of a directory, so components can get built in an unpredictable order' << this is gonna need a cure.
asciilifeform: 'Lamb referred to a build that had been made non-reproducible by a 15-digit random number that was generated during each build and baked into the resulting binary. It turned out that it was used as an OpenID secret, which meant that everyone running a given build of the software was using the same secret key.' << genius...
asciilifeform: also didjaknow! , 'Building everything from sources that one has hand-inspected is a solution to this, but it doesn't scale. Many of us aren't qualified to spot security weaknesses...' etc
asciilifeform: whatever of these survives elf stripping, at the very least.
asciilifeform: btw as soon as ave1 fully pins down his gnat, 1st order of biznis is the burning out with hot irons of all timestampism and misc crapola emitted into binaries
asciilifeform: 'In the tricky middle ground of 95-96%, his position would depend on why builds were non-reproducible, as there are a few valid reasons for this to happen. In response to another question, he said that two good reasons for a non-reproducible build were packages that build inside their own virtual machine, such as Emacs, and security packages with signing keys such as secure boot. ' << lolwaaat
asciilifeform: earlier diana_coman requested conventional gentoo. what'll it be ?☟︎
asciilifeform: right, ave1 produced a working self-builder gnat. nobody's bolted it into a gentoo in such a way that ~everything~ gets built with it, of yet. ( this as i understand is in the cuntoo conveyor )
asciilifeform: full musl implies cuntoo, hence asciilifeform's initial confusion
asciilifeform: ( let's imagine, say, the eulora folx suddenly want to connect 6 FG's. currently cannot do )
asciilifeform: even so, better to start the train going, so disks etc can be 'yes!! we have disks!' if suddenly a primary box goes up in smoke, rather than 'oh hmm where do we get some disks'.
asciilifeform: i'ma ask that anyffing sent to asciilifeform for transport, be either marked (if sent from human hands) or serial # gpggrammed to asciilifeform , so he can mark it.☟︎
asciilifeform: BingoBoingo: put your sp study to use in the battlefield.
asciilifeform: BingoBoingo: it is very much worth looking into speaking with iron shoppe d00d and working out something re disks. may prove to be cheaper.
asciilifeform: disk shortage is serious problem imho, these will have to be an absolute priority item for next airdrop. the tricky bit is that the only reliable way to transport'em, without triggering the ruinous tax, is inside machines.
asciilifeform: hey ben_vulpes do we have a Troo Full Inventory posted somewhere ?
asciilifeform: iirc there is also a cold spare ssd belonging to mod6 , can work something out with him.
asciilifeform: diana_coman, mircea_popescu if you need this box asap, it is possible to pull the hot spare from primary and make a single-disked staging box out of the spare.
asciilifeform: ben_vulpes: correct, and ben_vulpes , trinque , lobbes ( iirc ) send in disks , which then went into it
asciilifeform: diana_coman: plox to correct the above disk spec if necessary
asciilifeform: BingoBoingo: plox to visit ye olde iron shoppe then, and obtain quote for 5 1tb ssd, if available, or output re what is available, if these are not
asciilifeform: BingoBoingo: plox to make inventory of drives
asciilifeform: and then can start the process of auditing, cleansing.
asciilifeform: when ave1 comes back with patch for cross-x64 , it will be time to genesis the thing
asciilifeform: but for this it will have to work in all possible combos of 'who-whom'
asciilifeform: what i'd like to end up with, is to make ave1's gnat the default gcc in my gentoos ( and , in time, in cuntoo )
asciilifeform: ( the 1 item which did not work, is the building of x64 gnat ~on~ arm64 gnat, iirc he went to fix this and not yet come back )
asciilifeform: i tested his latest builder on x64 and arm64, both perform like champs.
asciilifeform: which then run on , theoretically, any linux of compatible cpu.
asciilifeform: a musl-gnat is first built, using a conventional gnat; this is then installed in user homedir, placed in path, and becomes the active gnat; with which then can build musltronic proggies.
asciilifeform: diana_coman: you don't need cuntoo to build musl executables, ave1's gnat does this on an ~arbitrary linux. ( via similar method as the 2015 'rotor' item )
asciilifeform: chances are that it'll work without coad changes.
asciilifeform: ( well, technically 2nd, gcc was 1st )
