Date: Fri, 11 Jan 2019 09:20:05 -0800 From: Kees Cook <keescook@...omium.org> To: Masahiro Yamada <yamada.masahiro@...ionext.com> Cc: linux-kbuild <linux-kbuild@...r.kernel.org>, Kernel Hardening <kernel-hardening@...ts.openwall.com>, Emese Revfy <re.emese@...il.com>, LKML <linux-kernel@...r.kernel.org>, Michal Marek <michal.lkml@...kovi.net> Subject: Re: [PATCH 2/2] kbuild: simplify GCC plugin build rules On Fri, Jan 11, 2019 at 1:19 AM Masahiro Yamada <yamada.masahiro@...ionext.com> wrote: > > GCC-plugin is the only user of the shared library build rules in > scripts/Makefile.host. Hence, those rules do not need to be treewide > available. > > The build rules in scripts/Makefile.host are written in a too generic > way. I guess the main reason is because commit 24403874316a ("Shared > library support") revived the code ripped off by commit 62e2210798ed > ("kbuild: drop shared library support from Makefile.host"). > > Currently, every plugin is built from a single C file. So, all we need > is a pattern rule to create %.so from %.c. What'll it look like if we get a multi-file plugin in the future? There are existing out-of-tree plugins that this change may make porting more difficult... -- Kees Cook
Powered by blists - more mailing lists
Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.