Current Image for Building Packages is a Nightmare

[michael-pptf]

First of all, I'll have to admit that I am not a very experienced RISC-V developer. I have ported a fair share of x86 libraries to ARM, with hiccups here and there of course, but nothing to the extents when it comes to this RISC-V board.

I was going to build the qdevice package for NanoKVM to give a quorum vote for Proxmox cluster. However, when using the provided toolchains over at LicheeRV Nano repo and setting the $SYSROOT to the Linux image there, it is absolutely bare with not even the most standard libraries.

It goes like this:

In order to build qdevice, I need to build corosync and nss. nss being a Mozilla library for numerous Internet related functionalities, including browers, is missing. Sure, let's build that. Then, I need to build nspr and zlib which nss depends on, all from source with musl.

Then corosync needs libqb and kronosnet, which require sctp, nss(which I just built), gcrpyt, zlib(again I built it myself), lz4, lzo2, lzma, bzip2, zstd and couple other more, which are all STANDARD for any Linux distribution.

I'm won't be trying for any porting attempts with a 10-ft pole anymore. Just use a normal RISC-V Linux distribution with standard libraries and package managers - TF cards are not that expensive, we can afford to have the image bigger in size.

My wording might be strong, but that's my frustration with how difficult it is to port anything to this kit.

[PatrickHuetter]

I don't know wether this helps but i've seen some forks/custom images which might help (running on nanoKVM):
https://github.com/scpcom/sophgo-sg200x-debian/tree/ubuntu
https://github.com/scpcom/LicheeRV-Nano-Build
https://github.com/scpcom/nanokvm-skeleton