Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Romain Naour <romain.naour@gmail.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/2] linux: introduce LINUX_KCFLAGS to add additional options to the C compiler
Date: Sat, 26 Sep 2020 21:13:29 +0200	[thread overview]
Message-ID: <20200926191330.96074-1-romain.naour@gmail.com> (raw)

Since 9a50447b5d4b2ab0162e3235395ab9a4c8a647d5 KCFLAGS is set
to disable a compiler warning but doesn't allow to provide
more flags.

This refactoring introduce LINUX_KCFLAGS to provide more
options to the C compiler.

Signed-off-by: Romain Naour <romain.naour@gmail.com>
---
 linux/linux.mk | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

diff --git a/linux/linux.mk b/linux/linux.mk
index e07e014d1e..b9b223e3f3 100644
--- a/linux/linux.mk
+++ b/linux/linux.mk
@@ -71,7 +71,8 @@ LINUX_PATCH = $(filter ftp://% http://% https://%,$(LINUX_PATCHES))
 # host-pkgconf will look for host libraries and not target ones.
 LINUX_MAKE_ENV = \
 	$(HOST_MAKE_ENV) \
-	BR_BINARIES_DIR=$(BINARIES_DIR)
+	BR_BINARIES_DIR=$(BINARIES_DIR) \
+	KCFLAGS="$(LINUX_KCFLAGS)"
 
 LINUX_INSTALL_IMAGES = YES
 LINUX_DEPENDENCIES = host-kmod \
@@ -154,7 +155,7 @@ endif
 # sanitize the arguments passed from user space in registers.
 # https://gcc.gnu.org/bugzilla/show_bug.cgi?id=82435
 ifeq ($(BR2_TOOLCHAIN_GCC_AT_LEAST_8),y)
-LINUX_MAKE_ENV += KCFLAGS=-Wno-attribute-alias
+LINUX_KCFLAGS += -Wno-attribute-alias
 endif
 
 ifeq ($(BR2_LINUX_KERNEL_DTB_OVERLAY_SUPPORT),y)
-- 
2.25.4

             reply	other threads:[~2020-09-26 19:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-26 19:13 Romain Naour [this message]
2020-09-26 19:13 ` [Buildroot] [PATCH 2/2] linux: Disable -ftree-loop-distribute-patterns when building for microblaze with gcc >= 10 Romain Naour
2020-09-30 20:59   ` Thomas Petazzoni
2020-09-30 21:04     ` Romain Naour
2020-10-01  8:06       ` Thomas Petazzoni
2020-10-06 18:46         ` Arnout Vandecappelle
2020-10-06 18:50           ` Thomas Petazzoni

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20200926191330.96074-1-romain.naour@gmail.com \
    --to=romain.naour@gmail.com \
    --cc=buildroot@busybox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox