Re: error when using KCONFIG_ALLCONFIG?

[Randy Dunlap <rdunlap@xenotime.net>]

Randy Dunlap wrote:
> Sam Ravnborg wrote:
>> On Wed, Apr 29, 2009 at 03:38:36PM -0700, Randy Dunlap wrote:
>>> Hi,
>>>
>>> I often use
>>> make KCONFIG_ALLCONFIG=filename allnoconfig
>>>
>>> and it works fine.  However, when I use O= with that:
>>>
>>> make O=xx64 KCONFIG_ALLCONFIG=filename allnoconfig
>>>
>>> I get an xx64/.config file that is the same as
>>>
>>> make O=xx64 allnoconfig
>>>
>>> I.e., the KCONFIG_ALLCONFIG=filename part was ignored.
>>>
>>> Is this new?  expected?  known?
>> I dunno if it is new but it is not expected.
>> Can you try if it help to move 'filename' to output directory.
> 
> make O=xx64 KCONFIG_ALLCONFIG=xx64/filename allnoconfig
> 
> gives the same result as 'make allnoconfig'.

It appears that using O= with KCONFIG_ALLCONFIG causes the
KCONFIG_ALLCONFIG option/feature to be ignored completely.

All of these commands act as though KCONFIG_ALLCONFIG=filename
was not used at all:

make O=zz64 KCONFIG_ALLCONFIG=filename allyesconfig
make O=zz64 KCONFIG_ALLCONFIG=filename allmodconfig
make O=zz64 KCONFIG_ALLCONFIG=filename allnoconfig

These all produce the same output .config files that are
produced by entering:

make O=zz64 allyesconfig
make O=zz64 allmodconfig
make O=zz64 allnoconfig


~Randy