odroidc1: fix GCC 14 build via config.mk -fpermissive patch (not cflags hook)

The initial fix appended -Wno-error flags to uboot_cflags_array, but that has no
effect on this 2011-era hardkernel u-boot (odroidc-v2011.03): its pre-Kbuild
config.mk assigns CFLAGS with := and ignores the framework's injected
KCFLAGS/env CFLAGS. The build kept failing on the same GCC-14 default-errors
(implicit-function-declaration, int-conversion, incompatible-pointer-types, ...
in board.c/gpio.c/bootm.c) - confirmed by the flags being absent from the actual
per-file gcc command lines.

Replace the hook with a source patch that adds -fpermissive to config.mk's
CFLAGS. In GCC 14, -fpermissive downgrades exactly those C permerrors back to
warnings; verified accepted by arm-linux-gnueabi-gcc 14 and confirmed to build.
ARCH=armhf, so the int<->pointer conversions are same-width and benign.

Signed-off-by: Igor Pecovnik <igor@armbian.com>

Author: igorpecovnik

config/boards/odroidc1.conf

@@ -27,19 +27,7 @@ write_uboot_platform() {
 	dd if=/dev/zero of=$2 seek=1024 count=32 bs=512 conv=fsync > /dev/null 2>&1
 }
 
-# GCC 14 (trixie host) promotes -Wint-conversion, -Wimplicit-function-declaration,
-# -Wimplicit-int and -Wincompatible-pointer-types from warning to hard error. This
-# 2011-era hardkernel Amlogic u-boot (odroidc-v2011.03) trips on all of them
-# (board.c / gpio.c / bootm.c: get_dev_by_name, vpu_probe, amlogic_gpio_*, malloc,
-# pointer-from-integer, ...). It built on noble/GCC 13; downgrade back to warnings
-# so it builds on trixie. ARCH=armhf, so the int<->pointer conversions are
-# same-width and benign.
-function post_config_uboot_target__odroidc1_downgrade_gcc14_errors() {
-	uboot_cflags_array+=(
-		"-Wno-error=implicit-function-declaration"
-		"-Wno-error=implicit-int"
-		"-Wno-error=int-conversion"
-		"-Wno-error=incompatible-pointer-types"
-	)
-	return 0
-}
+# NB: the GCC 14 build fix lives in the u-boot source patch
+# patch/u-boot/legacy/board_odroidc1/fix-gcc14-permissive.patch, not a
+# uboot_cflags_array hook: this 2011 u-boot's config.mk assigns CFLAGS with :=
+# and ignores the framework-injected KCFLAGS, so a hook has no effect here.

patch/u-boot/legacy/board_odroidc1/fix-gcc14-permissive.patch

@@ -0,0 +1,34 @@
+From: Armbian
+Subject: [PATCH] odroidc1: build config.mk with -fpermissive for GCC 14
+
+This 2011-era hardkernel Amlogic u-boot (odroidc-v2011.03) uses the pre-Kbuild
+build system: config.mk assigns CFLAGS with `:=`, ignoring the environment /
+KCFLAGS the Armbian build framework injects. So a post_config_uboot_target hook
+appending -Wno-error flags to uboot_cflags_array has no effect here (unlike the
+newer odroidxu4 u-boot, which honours KCFLAGS).
+
+GCC 14 makes implicit-function-declaration, implicit-int, int-conversion,
+incompatible-pointer-types and return-mismatch hard errors *by default* (no
+-Werror needed), and this codebase trips on all of them (board.c/gpio.c/bootm.c:
+get_dev_by_name, vpu_probe, amlogic_gpio_*, malloc, pointer-from-integer, ...).
+It built fine on GCC 13 / noble.
+
+-fpermissive downgrades exactly those C permerrors back to warnings (GCC 14 C
+behaviour, verified accepted by arm-linux-gnueabi-gcc 14). Add it straight to
+config.mk's CFLAGS so it lands on every object. ARCH is armhf, so the
+int<->pointer conversions are same-width and benign.
+
+--- a/config.mk
++++ b/config.mk
+@@ -192,6 +192,11 @@
+
+ CFLAGS += $(call cc-option,-fno-stack-protector)
+
++# GCC 14 makes implicit-function-declaration, implicit-int, int-conversion,
++# incompatible-pointer-types and return-mismatch hard errors by default; this
++# 2011 u-boot predates that. -fpermissive downgrades them back to warnings.
++CFLAGS += $(call cc-option,-fpermissive)
++
+ # $(CPPFLAGS) sets -g, which causes gcc to pass a suitable -g<format>
+ # option to the assembler.
+ AFLAGS_DEBUG :=