My files seem to work fine but it turns out that makepkg didn’t even create the final packages. It doesn’t give any error message for not being able to generate the packages.
I gave up on creating arch from gentoo for now
Since an image of parabola was released I will use that one if it works.
I was able to mount it and retrieve the rootfs. I have no interest in a vm, I rather use the real thing.
Mounting it is not a big deal as long as you are familiar with the type of image
Just in case you would have issues, here are the commands needed as root to get the rootfs into an xz compressed file
modprobe nbd max_part=8
qemu-nbd --connect=/dev/nbd0 parabola-riscv64.qcow2
mount /dev/nbd0p1 rootfs
tar cvfJ …/images/parabola-20210621.tar.xz *
I hope to be able to use this and chroot on it.
Once I get it working on the beaglev with the correct kernel I will see if I can replace systemd with openrc.
One thing that I have noticed is that the lib directories are not handled the same way as on gentoo.
I do have archlinux on my ryzen computer but find gentoo to be faster so that is my main work system. I do use archlinux at work, I didn’t want to spend the time needed for gentoo…
For embedded systems I often prefer archlinux, that is what I use on my beaglebone black boards.
On gentoo /lib and /usr/lib are different directories as well as /lib64 and /usr/lib64
/lib64 as well as /usr/lib64 used to not have any files but a directory called lp64d or lp64 depending on whether you want hard to pass arguments in FP registers or not
Recently the gentoo maintainer(s) have changed this so you get lp64d → . or lp64 → . and the library are on the lib64 directories
On this it looks just like on my Ryzen computer,
lib → usr/lib
lib64 → usr/lib
usr/lib64 → lib
So my question to the parabola maintainer(s), which protocol is used for your system, lp64d or lp64?
I guess I could figure out eventually