[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <fb60e245-86f2-53c6-79d8-bd395ef011dd@cn.fujitsu.com>
Date: Mon, 12 Feb 2018 12:22:14 +0800
From: Cao jin <caoj.fnst@...fujitsu.com>
To: Masahiro Yamada <yamada.masahiro@...ionext.com>
CC: Michal Marek <michal.lkml@...kovi.net>,
Linux Kbuild mailing list <linux-kbuild@...r.kernel.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>
Subject: why scripts/link-vmlinux.sh has a final build of init/
Hi Masahiro-san,
As I remember, init/ is already built during recursive make, and I did
a clean build(make mrproper, make localmodconfig) with all plugins
included on x86_64 with following patch, the kernel can boot without any
obvious problem. So, I don't figure out why we need this final build?
diff --git a/scripts/link-vmlinux.sh b/scripts/link-vmlinux.sh
index e6818b8e7141..086b2efd4d53 100755
--- a/scripts/link-vmlinux.sh
+++ b/scripts/link-vmlinux.sh
@@ -247,9 +247,6 @@ else
expr 0$(cat .old_version) + 1 >.version;
fi;
-# final build of init/
-${MAKE} -f "${srctree}/scripts/Makefile.build" obj=init
GCC_PLUGINS_CFLAGS="${GCC_PLUGINS_CFLAGS}"
-
archive_builtin
#link vmlinux.o
--
Sincerely,
Cao jin
Powered by blists - more mailing lists