I have had exclude all patches after patch-11-12 to make the build system not error on the makepkg --nobuild --skipinteg ( because I did not remove the crc checks ) and am about to try the full compile.
My current kernel is your previous 6.6 build and I have only added a SCSI_transport_FC flag and a qla2xxx driver module for a fibre channel card i sometimes use via pci to connect to a clusterFS.
eh? ccache is not required, but if the build script (PKGBUILD) found it, it will try to use it, so when you rebuild it again after make some changes, it will finish a lot faster.
This is weird, can you try sudo pacman -Syu before makepkg? I built it on my VF2 many times before made a release, and they were all pass. How about justmakepkg -o?
I did not update anything before trying. I need to make image backups before I try to -U the zst files. on my good build … or use a clean cwt-23 image and test from that to the new one.
I use bash and had an issue with CCACHE=$(which ccache 2>/dev/null) not working properly for some reason. The command worked outside of the script, but would not work while running it. This was resolved by installing the package, however to make it work for me WITHOUT installing, as per the 'IF THEN" paragraph, I had to make the following adjustments. I did use POSIX compliant commands to make sure it would be compatible with everything. I did not DIFF the two files… sorry. here below is the section with minor change.
prepare() section …Preformatted text
if command -v ccache 2>&1 >/dev/null; then
CCACHE=$(which ccache 2>/dev/null)
echo $CCACHE # too make sure
gcc="${CCACHE} ${CROSS_COMPILE:-}gcc"
else
echo " ........ccache not installed ! ........................"
gcc="${CROSS_COMPILE:-}gcc"
fi
I tried booting but the kernel crashes with: modprobe[76]: unhandled signal 4 code 0x1 at 0x0000003fb27080dc in ld-linux-riscv64-lp64d.so.1[160dc,3fb26f2000+23000
hello. So I have found two refences to this package …
it is the risc-v implemetation of ld.so … which is a toolchain loader of some type…
and another reference to cross compiling errors.
To start with, barring any hardware errors, RAM errors, bad bits, et cet. … I would have to know if the kernel was cross compiled, and a bit more about the environment it was made on. GCC version may be an issues also. Is it a fresh install from the *img file to an SD/NVME card or an upgrade with CWT’s updater script that builds and installs the updated kernel/headers and the like?
Hello. Fresh install to SD card from the latest img but I am on a Milk-V Mars.
However, I think I changed the u-boot in SPI flash to the mainline one to be able to boot Ubuntu.
Hello gentlemen. I do not have a MARS board. I have been trying to use all types of QEMU images and the associated tools to make images for different systems. I will look into the nuances of the MARS board.
It could just be a compiler flag that needs to be set different/added/removed also…
