That would be very interesting, yes. The A-06 is very capable of compiling anything, but linking qt6 required an obscene amount of RAM and, after much trial and error, I landed on using qemu-binfmt on my desktop system. Some fiddling was required to get a functional chroot: since I registered qemu as the handler for 64-bit ARM binaries, I had to make sure that qemu-aarch64 was available inside the chroot and all the libraries it linked against.
I think something like that would work fine for a RISC-V CPU, but very interested in how you’ve set yours up. I mostly used the prebuilt packages from slarm64 ([sic], the ARM-64 Slackware project has sort of taken custody of the RISC-V Slackware port), and for anything else that I needed, it was fast enough to compile on-device. (I am not likely to try to run Firefox on it. I really like the D1, I don’t wanna fill its memory with JavaScript.)
For builds now, I actually use a TPi2 RK1; I should probably write that up in the thread ( CRUX for DevTerm A06, dev notes ). I imagine that you could do something analogous by getting one of those Lychee Clusters: LicheePi Cluster 4A - Sipeed Wiki . Very cool gear, but possibly overkill just to speed up your builds.