So I joined the OpenADK/uClibc mailing lists to discuss problems that I faced and found. Turns out that RISC-V support is still very limited and even reproducible in QEMU. Well ... that sucks o.o So I have to switch to musl - which brings a whole new set of problems. It HATES being statically linked... x.x So I have to give up some of my ambitions of a fully static and thus portable toolchain and my container image is bound to be a bit bigger as well. Beh. Oh well, it is only an intermediary container that serves to become a foundation anyway - it will be discarded rather fast once Alpine's configuration of a toolchain is ready to go. Also, since I have had that much success with this, I am going to be making posts to the RISC-V forums that I am at to either find volunteers to look into uClibc's TLS impl and raise awareness of OpenADK; because it is REALLY good. Easy to handle and straight forward. I like it much more than Buildroot - which is also good, but it's refusal to build a toolchain into the resulting rootfs is a big bummer, since you will likely want one in the long run. So... that one is out of the question.

Through the OpenADK I also became aware of BareBox - basically Busybox for bootloaders. u-boot is the much more compatible one, but Barebox has a much nicer interface to work with. So who knows, maybe I can get a port out of this? After all, the JH7110 bootROM will, unconditionally, boot into the first partition found on the storage medium selected by the dip switches. o.o It'd make for a great substitute for u-boot; it's scripting language is classic POSIX - /bin/sh. Much more legible than the clusterfuck that u-boot has. xD Can even construct a menu, built-in! So let's see where all of this goes.

Meanwhile in school: Explain virtualization and build a server for an imaginary client.

Hue. Way ahead of them all. x)

Bullish on #nostr, bullish on #riscv - let's go! =)