Document using KCFLAGS rather than EXTRA_CFLAGS to pass compiler flags for
kernel builds.
KCFLAGS has been supported since upstream kernel commit 69ee0b352242
("kbuild: do not pick up CFLAGS from the environment") which was
included in v4.0 in 2007.
Support for EXTRA_CFLAGS was removed from the upstream kernel
by commit e966ad0edd00 ("kbuild: remove EXTRA_*FLAGS support")
in April 2025 which was included in v6.15-rc1.
Found by inspection.
Signed-off-by: Simon Horman <ho...@ovn.org>
---
Documentation/intro/install/general.rst | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/Documentation/intro/install/general.rst
b/Documentation/intro/install/general.rst
index 0f3cb4e4961d..f96dc26089ad 100644
--- a/Documentation/intro/install/general.rst
+++ b/Documentation/intro/install/general.rst
@@ -288,10 +288,10 @@ target machine.
.. note::
CFLAGS are not applied when building the Linux kernel module. Custom CFLAGS
- for the kernel module are supplied using the ``EXTRA_CFLAGS`` variable when
+ for the kernel module are supplied using the ``KCFLAGS`` variable when
running make. For example::
- $ make EXTRA_CFLAGS="-Wno-error=date-time"
+ $ make KCFLAGS="-Wno-error=date-time"
If you are a developer and want to enable Address Sanitizer for debugging
purposes, at about a 2x runtime cost, you can add
_______________________________________________
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev
