[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <52C0DAB2.7090001@infradead.org>
Date: Sun, 29 Dec 2013 18:30:10 -0800
From: Randy Dunlap <rdunlap@...radead.org>
To: "H. Peter Anvin" <hpa@...or.com>, linux-kbuild@...r.kernel.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: KCONFIG_ALLCONFIG + allmodconfig = brokenness
On 12/29/13 18:22, Randy Dunlap wrote:
> On 12/29/13 17:32, H. Peter Anvin wrote:
>> When KCONFIG_ALLCONFIG is used with "make allmodconfig", the result ends
>> up being largely the same as "make allyesconfig", because the resulting
>> kernel ends up with CONFIG_MODULES=n:
>>
>> How to reproduce:
>>
>> : tazenda 125 ; make O=../o.test allmodconfig
>> GEN /home/hpa/kernel/o.test/Makefile
>> scripts/kconfig/conf --allmodconfig Kconfig
>> #
>> # configuration written to .config
>> #
>> : tazenda 126 ; grep CONFIG_MODULES ../o.test/.config
>> CONFIG_MODULES_USE_ELF_RELA=y
>> CONFIG_MODULES=y
>> : tazenda 127 ; env KCONFIG_ALLCONFIG=/dev/null make O=../o.test
>> allmodconfig
>> GEN /home/hpa/kernel/o.test/Makefile
>> scripts/kconfig/conf --allmodconfig Kconfig
>> #
>> # configuration written to .config
>> #
>> : tazenda 128 ; grep CONFIG_MODULES ../o.test/.config
>> CONFIG_MODULES_USE_ELF_RELA=y
>> # CONFIG_MODULES is not set
>> --
>
> Yes, I discovered this a few weeks ago.
> I just ended up adding
> CONFIG_MODULES=y
> to my KCONFIG_ALLCONFIG file.
>
> There was a comment in the git commit for it about this (that I discovered
> during my "research" into it), but I can't find it just now.
See 11097a0367e48954ecf616f9b0df48d86835dd0d.
> I wasn't fond of the change either.
>
>
--
~Randy
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists