7.1 build failure

[RadxaYuntian]

Incorrect include path: K900/linux@5be9827

[RadxaYuntian]

Might be difference in build environment. K900 likely built the kernel with nix, which might strip additional ccflags defined in linlon Makefile.

[EvilOlaf]

Works for me: armbian/build#10167

[USAVault]

Incorrect include path: K900/linux@5be9827

Isn't this related to linlondp adding includes with $(srctree) in the Makefile?
This usage is deprecated because during out-of-tree/split module builds, kbuild sets $(srctree) to an absolute path to the kernel source tree, while $(src) already contains the full absolute path to the module directory. Prepending $(srctree) results in a double absolute path (e.g. /path/to/kernel//path/to/module), which breaks includes. Simply using -I$(src)/include -I$(src) works correctly in all cases

--- a/drivers/gpu/drm/cix/linlon-dp/Makefile
+++ b/drivers/gpu/drm/cix/linlon-dp/Makefile
@@ -1,8 +1,8 @@
 # SPDX-License-Identifier: GPL-2.0
 
 ccflags-y := \
-    -I $(srctree)/$(src)/include \
-    -I $(srctree)/$(src)
+    -I $(src)/include \
+    -I $(src)
 
 linlon-dp-y := \
     linlondp_drv.o \

[coffnix]

I built the kernel directly inside the source tree, without an out of tree build (O=), and it compiled successfully. It might be worth trying a standard in tree build first to see if the issue is specific to the build environment rather than the driver itself.

[coffnix]

try my script:

#!/bin/bash

DATA=$(date +'%Y-%m-%d')
cp -rp /boot /boot-bkp-${DATA}

cd /usr/src ; rm -rf /usr/src/cix-linux-main ;  git clone https://github.com/cixtech/cix-linux-main.git

cd /usr/src/cix-linux-main/patches-7.1/

cd /usr/src/linux
for p in ../cix-linux-main/patches-7.1/*.patch; do patch -p1 < "$p"; done
cp /usr/src/cix-linux-main/config/config-7.1.defconfig .config

scripts/config --disable DRM_NOUVEAU
scripts/config --disable DRM_AMDGPU
scripts/config --disable OCTEONTX2_PF
scripts/config --disable OCTEONTX2_VF
scripts/config --disable OCTEONTX2_AF
make olddefconfig

make -j"$(nproc)" Image
if [ "$?" -ne 0 ];then echo 'ERROR' ;exit 1 ;fi

make -j"$(nproc)" modules
if [ "$?" -ne 0 ];then echo 'ERROR' ;exit 1 ;fi

make -j"$(nproc)" dtbs
if [ "$?" -ne 0 ];then echo 'ERROR' ;exit 1 ;fi

cd /usr/src/linux
export NEW="$(make kernelrelease)"

cp /usr/src/linux/arch/arm64/boot/dts/cix/sky1-xcp.dtb /boot/efi/sky1-orangepi-6-plus-${NEW}.dtb
cp arch/arm64/boot/Image /boot/vmlinuz-${NEW}
cp arch/arm64/boot/Image /boot/efi/vmlinuz-${NEW}
cp System.map /boot/System.map-${NEW}
cp .config /boot/config-${NEW}
make modules_install
depmod -a "${NEW}"
ls /lib/modules/"${NEW}" >/dev/null || exit 1
dracut /boot/initramfs-${NEW}.img ${NEW}
cp /boot/initramfs-${NEW}.img /boot/efi/initramfs-${NEW}.img
cd

[USAVault]

I built the kernel directly inside the source tree, without an out of tree build (O=), and it compiled successfully. It might be worth trying a standard in tree build first to see if the issue is specific to the build environment rather than the driver itself.

Your in-tree build works because $(srctree)="." and $(src) is relative, so $(srctree)/$(src) resolves to ./drivers/gpu/.... Some build systems (like Portage) compile this driver using a split build, where a separate output directory is used. In this case $(srctree) holds the relative path from the output directory back to the source tree root (e.g. ../linux-7.1), while $(src) resolves to an absolute realpath of the source directory. This turns $(srctree)/$(src) into a broken double path like ../linux-7.1//var/tmp/portage/.../linux-7.1/drivers/.../include. Since kernel 6.9 upstream forces using just $(src) instead

[coffnix]

I built the kernel directly inside the source tree, without an out of tree build (O=), and it compiled successfully. It might be worth trying a standard in tree build first to see if the issue is specific to the build environment rather than the driver itself.

Your in-tree build works because $(srctree)="." and $(src) is relative, so $(srctree)/$(src) resolves to ./drivers/gpu/.... Some build systems (like Portage) compile this driver using a split build, where a separate output directory is used. In this case $(srctree) holds the relative path from the output directory back to the source tree root (e.g. ../linux-7.1), while $(src) resolves to an absolute realpath of the source directory. This turns $(srctree)/$(src) into a broken double path like ../linux-7.1//var/tmp/portage/.../linux-7.1/drivers/.../include. Since kernel 6.9 upstream forces using just $(src) instead

Yeap.... You can enable the symlink USE flag on any ebuild to build it with Portage, which makes it much easier to create scripts or use tools like genkernel, as well as other ebuilds such as vanilla-sources and similar packages.

[USAVault]

Yeap.... You can enable the symlink USE flag on any ebuild to build it with Portage, which makes it much easier to create scripts or use tools like genkernel, as well as other ebuilds such as vanilla-sources and similar packages.

Haven't touched them since I started using Gentoo tbh; really like dist-kernel with installkernel and if needed - ebuild prepare, nano, git diff