From: Arnd Bergmann <arnd@arndb.de> To: unlisted-recipients:; (no To-header on input) Cc: Nicolas Pitre <nico@linaro.org>, Andi Kleen <ak@linux.intel.com>, linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org, Arnd Bergmann <arnd@arndb.de> Subject: [PATCH 1/7] [HACK] lto: make config.gz symbol visible Date: Fri, 2 Feb 2018 17:15:39 +0100 [thread overview] Message-ID: <20180202161550.2106846-2-arnd@arndb.de> (raw) In-Reply-To: <20180202161550.2106846-1-arnd@arndb.de> building with LTO enabled, I often get warnings about kernel/configs.c being empty when CONFIG_IKCONFIG is disabled: x86_64-linux/bin/nm: kernel/configs.o: no symbols Making the symbol visible is probably not the right solution, but it does get rid of the warning. Signed-off-by: Arnd Bergmann <arnd@arndb.de> --- kernel/Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kernel/Makefile b/kernel/Makefile index 7666ee88e237..40b48e3e87a2 100644 --- a/kernel/Makefile +++ b/kernel/Makefile @@ -120,7 +120,7 @@ targets += config_data.gz $(obj)/config_data.gz: $(KCONFIG_CONFIG) FORCE $(call if_changed,gzip) - filechk_ikconfiggz = (echo "static const char kernel_config_data[] __used = MAGIC_START"; cat $< | scripts/basic/bin2c; echo "MAGIC_END;") + filechk_ikconfiggz = (echo "const char kernel_config_data[] __used __visible = MAGIC_START"; cat $< | scripts/basic/bin2c; echo "MAGIC_END;") targets += config_data.h $(obj)/config_data.h: $(obj)/config_data.gz FORCE $(call filechk,ikconfiggz) -- 2.9.0
WARNING: multiple messages have this Message-ID (diff)
From: Arnd Bergmann <arnd@arndb.de> Cc: Nicolas Pitre <nico@linaro.org>, Andi Kleen <ak@linux.intel.com>, linux-kernel@vger.kernel.org, linux-kbuild@vger.kernel.org, Arnd Bergmann <arnd@arndb.de> Subject: [PATCH 1/7] [HACK] lto: make config.gz symbol visible Date: Fri, 2 Feb 2018 17:15:39 +0100 [thread overview] Message-ID: <20180202161550.2106846-2-arnd@arndb.de> (raw) In-Reply-To: <20180202161550.2106846-1-arnd@arndb.de> building with LTO enabled, I often get warnings about kernel/configs.c being empty when CONFIG_IKCONFIG is disabled: x86_64-linux/bin/nm: kernel/configs.o: no symbols Making the symbol visible is probably not the right solution, but it does get rid of the warning. Signed-off-by: Arnd Bergmann <arnd@arndb.de> --- kernel/Makefile | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/kernel/Makefile b/kernel/Makefile index 7666ee88e237..40b48e3e87a2 100644 --- a/kernel/Makefile +++ b/kernel/Makefile @@ -120,7 +120,7 @@ targets += config_data.gz $(obj)/config_data.gz: $(KCONFIG_CONFIG) FORCE $(call if_changed,gzip) - filechk_ikconfiggz = (echo "static const char kernel_config_data[] __used = MAGIC_START"; cat $< | scripts/basic/bin2c; echo "MAGIC_END;") + filechk_ikconfiggz = (echo "const char kernel_config_data[] __used __visible = MAGIC_START"; cat $< | scripts/basic/bin2c; echo "MAGIC_END;") targets += config_data.h $(obj)/config_data.h: $(obj)/config_data.gz FORCE $(call filechk,ikconfiggz) -- 2.9.0
next prev parent reply other threads:[~2018-02-02 16:17 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2018-02-02 16:15 [PATCH 0/7] LTO: hacks to build LTO-enabled randconfig kernels Arnd Bergmann 2018-02-02 16:15 ` Arnd Bergmann 2018-02-02 16:15 ` Arnd Bergmann [this message] 2018-02-02 16:15 ` [PATCH 1/7] [HACK] lto: make config.gz symbol visible Arnd Bergmann 2018-02-02 16:20 ` [PATCH 2/7] [HACK] x86: lto: always link in library files Arnd Bergmann 2018-02-02 16:21 ` [PATCH 3/7] [HACK] x86: crypto: fix link error with LTO Arnd Bergmann 2018-02-02 19:49 ` Nicolas Pitre 2018-02-02 22:18 ` Arnd Bergmann 2018-02-02 16:21 ` [PATCH 4/7] [HACK] lto: shut up some warnings Arnd Bergmann 2018-02-02 16:21 ` [PATCH 5/7] [HACK] avoid gcc-8 ICE on LTO Arnd Bergmann 2018-02-02 17:04 ` Joe Perches 2018-02-02 16:21 ` [PATCH 6/7] Kbuild: lto: clean build artifacts Arnd Bergmann 2018-02-02 16:21 ` [PATCH 7/7] Kbuild: lto: pass -m32/-m64 to to LDFINAL Arnd Bergmann 2018-02-02 18:41 ` Nicolas Pitre 2018-02-02 20:18 ` Arnd Bergmann 2018-02-02 20:38 ` Nicolas Pitre 2018-02-02 20:55 ` Arnd Bergmann 2018-02-02 21:17 ` Nicolas Pitre
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=20180202161550.2106846-2-arnd@arndb.de \ --to=arnd@arndb.de \ --cc=ak@linux.intel.com \ --cc=linux-kbuild@vger.kernel.org \ --cc=linux-kernel@vger.kernel.org \ --cc=nico@linaro.org \ /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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.