IRC channel logs

2020-11-17.log

back to list of logs

<samueldr>siraben: I'm curious if you even started on mescc-tools+mes+tinycc, if you want to compare notes
<samueldr>I have what I believe is a fully working tinycc build, I haven't gone further down or up the ladder of abstraction
<samueldr> https://github.com/samueldr/nixpkgs-bootstrappable-playground
<V>ooh
<samueldr>really at this state, the only patch needed (and it really wasn't required) was this https://github.com/samueldr/nixpkgs-bootstrappable-playground/blob/development/0001-mescc-Don-t-depend-on-coreutils.patch
<samueldr>I just wanted to get nix path-info happy
<V>The state is that the Usage (Maybe don't.)
<samueldr>I always put quips like that in personal projects
<samueldr>there is absolutely no SLA on that repo :)
<samueldr>I updated the README, the patch I linked to drop basename/dirname makes it so all dependencies are "the ambient impure posix /bin/sh", mescc-tools and mes
<samueldr>otherwise we would have coreutils/bash and deps in there
<samueldr>I *guess* static busybox could do too
<OriansJ>well if you have guile, gash and gash-utils are a good replacement for bash and core-utils
<OriansJ>ideally gash and gash-utils will in the future run on mes-m2 and kaem provides all the shell one needs to bootstrap up until that point.
<samueldr>I don't know guile :) when I first was doing fool's errand of working with x86_64 the guile build would fail in inscrutable ways (to my neophyte eyes) while the shell-based bootstrap was more inspectable
<samueldr>ah, neat
<samueldr>though, note that I don't have anything against guile/scheme, I just don't know any of it
<OriansJ>samueldr: fair
<samueldr>other than reading enough of the guix commencement/bootstrap to get a feeling of some constructs and how they map to Nix/Nixpkgs constructs
<OriansJ>samueldr: well gash is supposed to be a bash work-alike
<samueldr>yeah, I figured
<samueldr>for the time being what I have here works with both directions of the ladder of abstraction to be built
<samueldr>this is a really minimal set of rungs
<OriansJ>well big and complicated; usually is hard to make work. Extremely so when you are trying to start from nothing.
<samueldr>yep, I'll try to remember to follow the news and when 0.23 is out and ready, see if updating to it is good
<samueldr>though tbf I didn't try 0.22, but there is not tinycc branch for 0.22
<OriansJ>updated https://bootstrapping.miraheze.org/wiki/Stage0#cc_.2A_.2B_family (for the first time in a long time) feel free to point out anything important I might have missed or anything I did not cover clearly.
<xentrac>that's wonderful!
<Hagfish>yeah, that's a really great introduction for people, and it's nicely laid out reference document
<siraben>samueldr: do you program in other functional languages?
<siraben>Scheme can be understood by desugaring it to raw lambda calculus, the important extra addition is hygienic macros
<siraben>samueldr: thanks, will check it out
<siraben>I haven't gone either up or down as well
<siraben>samueldr: http://ix.io/2Ern
<siraben>I also had to update the hash of your pinned nixpkgs and mes.nix
<siraben>samueldr: https://github.com/samueldr/nixpkgs-bootstrappable-playground/pull/1
<rain1><blackwidowmovie0> They're all Miraheze users @rain1
<rain1><b<blackwidowmovie0> They're all Miraheze users @rain1
<rain1><blackwidowmovie0> It automatically creates the users on every wiki.lackwidowmovie0> It automatically creates the users on every wiki.
<rain1>sorry middle button is broken
<rain1>this was the response from #miraheze
***coldtom0 is now known as coldtom
***stikonas_ is now known as stikonas
<samueldr>siraben: no, I don't have actual experience with functional programming in the theoretical sense
<samueldr>siraben: uh, DUH, I forgot to pin the actual hash in the tarball URL
***cbaines_ is now known as cbaines