GhostBSD ARM64 porting from x86 code base (RISC-V in the future??)

GhostBSD-Arm64  Future Road Map Ideas to share with present Users.   FreeBSD is where GhostBSD gets upstream sources.  FreeBSD is the parent, but GhostBSD copies and keeps its own repository of source code in packages.  Howto on GhostBSD-Arm64 uses to obtain ghostbsd source code.  Start with a FreeBSD snapshot running Workstation to obtain source code like this: mkdir -p /usr/ghost14 ;  cd /usr/ghost14 git clone  github.com/ghostbsd/ghostbsd-src cd ghostbsd-src;  make buildworld ; make buildkernel KERNCONF=GENERIC-VCHIQ XFCE4.18 is operational on GhostBSD Arm64 Operating System based on FreeBSD Arm64 Tier 1  Freebsd.org/where find a RPI 3/4 snapshot like 13.2 or 14.0 https://download.freebsd.org/releases/arm64/aarch64/ISO-IMAGES/14.0/  https://download.freebsd.org/releases/arm64/aarch64/ISO-IMAGES/14.0/FreeBSD-14.0-RELEASE-arm64-aarch64-RPI.img.xz or  13.2  https://download.freebsd.org/releases/arm64/aarch64/ISO-IMAGES/13.2/...

time make -j4 buildworld KERNELCONF=GENERIC-VCHIQ -DNO_CLEAN    # script /var/tmp/mw.out Script started, output file is /var/tmp/mw.out   https://people.freebsd.org/~rodrigc/doc/handbook/makeworld.html Can /usr/obj be removed when finished? This directory contains all the object files that were produced during the compilation phase. Normally, one of the first steps in the make buildworld process is to remove this directory and start afresh. Keeping /usr/obj around when finished makes little sense, and its removal frees up a approximately 2GB of disk space. Can interrupted builds be resumed? This depends on how far into the process the problem occurs. In general, make buildworld builds new copies of essential tools and the system libraries. These tools and libraries are then installed, used to rebuild themselves, and are installed again. The rest of the system is then rebuilt...