Re: why scripts/link-vmlinux.sh has a final build of init/

Sorry for late. On 02/14/2018 07:31 PM, Masahiro Yamada wrote: > 2018-02-13 16:08 GMT+09:00 Cao jin : > >> BTW, I still have 2 questions. >> >> 1. In final build, why need >> >>GCC_PLUGINS_CFLAGS="${GCC_PLUGINS_CFLAGS}" >> >> Doesn't GCC_PLUGINS_CFLAGS already exist in the environment? >> >>

Re: why scripts/link-vmlinux.sh has a final build of init/

2018-02-13 16:08 GMT+09:00 Cao jin : > BTW, I still have 2 questions. > > 1. In final build, why need > >GCC_PLUGINS_CFLAGS="${GCC_PLUGINS_CFLAGS}" > > Doesn't GCC_PLUGINS_CFLAGS already exist in the environment? > > I also tested the Randomizing Structure Layout plugin with this patch, > the

Re: why scripts/link-vmlinux.sh has a final build of init/

On 02/12/2018 10:48 PM, Masahiro Yamada wrote: > 2018-02-12 13:22 GMT+09:00 Cao jin : >> 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

Re: why scripts/link-vmlinux.sh has a final build of init/

2018-02-12 13:22 GMT+09:00 Cao jin : > 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,