IRC channel logs

2021-07-01.log

back to list of logs

<fossy>does anyone have a link for the riscv bootstrapping work? (was it someone porting mes to riscv?)
<theruran>fossy: ekaitz is working on it: https://ekaitz.elenq.tech/lightening.html https://ekaitz.elenq.tech/hex0.html https://ekaitz.elenq.tech/machine-code-generation.html
***terpri is now known as robin
***roptat is now known as Guest9177
***terpri is now known as robin
***Guest9177 is now known as roptat
<xentrac>happy Leibniz day!
<oriansj>theruran: that reminds me, I probably need to find a copy of the Linux RISC-V syscall table to add to my notes
<oriansj>fossy: but as far as I can see, it looks like most of the RISC-V bootstrapping work is in MesCC
<oriansj>Which is entirely understandable. Getting *GOOD* M1 definitions is a problem (especially if more than one person has to use them)
<oriansj>Not to mention the desire to squeeze word behaviors into a byte language on architectures not designed for byte alignment.
<clemens3>hi, I know, you guys/girls have your (admirable) projects, but maybe you like the slogan.. here: http://techinvest.li/tinux/
<clemens3>a LFS based distro that doesn't depend on itself or is delivered via iso..
<clemens3>of course, mega blob still needed, but source compiled at the customers place..:)
<Hagfish>you had me at Devuan :)
<Hagfish>clemens3: "is signed buy" -> "is signed by"
<clemens3>haeh:)
<clemens3>its a mega blob, but it's a start:)
<stikonas>clemens3: we can basically rebuild something close to LFS without blobs
<stikonas>(well, for now x86 only)
<stikonas>but in principle you can cross-compile from there