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

Poudriere Simple Tips on $PATH, ccache, &Calling Poudriere command line  Poudriere Simple Tips Create a Jail  poudriere jail -c -j ghostbsd-14-aarch64 -m src=/usr/ghost14/ghostbsd-src   Bulk build packages from a previously create jail and a package list file  poudriere jail -l  poudriere bulk -j  ghostbsd-14-aarch64 -p ghostbsd_ports -f /usr/local/etc/poudriere.d/pkglist    Bulk build all packages (yes 33,000+) poudriere bulk -j ghostbsd-14-aarch64  -p ghostbsd_ports -a   To create   ghostbsd ports for poudriere poudriere ports -c -p ghostbsd_ports -m git -U "https://github.com/ghostbsd/ghostbsd-ports" -B main To update ghostbsd ports source code to latest main version poudriere ports -u -p ghostbsd_ports -m git -U "https://github.com/ghostbsd/ghostbsd-ports" -B main  

 vchiq_core.c  FreeBSD 14.0-CURRENT has compile errors   Standard update to /usr/src  code to the latest git -C /usr/src pull --ff-only   time make -j4 buildkernel TARGET_ARCH=aarch64 KERNCONF=GENERIC-VCHIQ  Below is the output: So I have 3 choices,  edit the makefile and turn of the Warn Error message flags -Wall -Werror edit the source file and correct format statements Find the author of this modified file and ask about his setup to compile and then do the same setup  use KERNCONF=GENERIC?  This option did work to compile the FreeBSD kernel. So that I could start Poudriere to build GhostBSD arm64 packages. What is the proper way to compile this file?: https://cgit.freebsd.org/src/tree/sys/contrib/vchiq/interface/vchiq_arm/vchiq_core.c cc -target aarch64-unknown-freebsd14.0 --sysroot=/usr/obj/usr/src/arm64.aarch64/tmp -B/usr/obj/usr/src/arm64.aarch64/tmp/usr/bin -c -O2 -pipe  -fno-strict-aliasing  -g -nostdinc  -I. -I/usr/src...

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...

 GhostBSD-ARM64 port Telegram Group: Search telegram for "GhostBSD ARM port"  updated January 23, 2021 What we are working toward   Kernel Debugging Tips note raspberry_pi debugging raspberry pi linux kernel with jtag and GDB Eastrivervillage.com KGDB-KDB-over-serial-with-RaspberryPi LLDB URL links to read Fred Finster, [02.01.21 17:36] Found some recent December 2020 reading material lLLDB-debugger-improvements-for-freebsd/   https://www.moritz.systems/blog/freebsd-remote-plugin-final-milestone-achieved/ FreeBSD 13.0 Current Look at https://PersonalBSD.org     for binary images for  Khadas, RockPi64, RockPi 4, RockPi 4c, Pinebook Pro, NanoPC-T4, ROC RK3399, Plus PC, Lambda Land  Post about getting FreeBSD 13.0 running on the Raspberry Pi 4 https://lambdaland.org/posts/2020-12-23_freebsd_rpi4/   https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=247012 Look for Raspi4 with 8Gigs u-boot version. https://github.com/raspberrypi/firmware/t...