Re: Build regression: unknown option "visible"

Previous thread: [RFC PATCH] trace event block: conversion to tp_assign/tp_memcpy by Mathieu Desnoyers on Monday, December 20, 2010 - 10:20 am. (3 messages)

Next thread: [PATCH] dmaengine: dma40: Add support to split up large elements by Per Forlin on Monday, December 20, 2010 - 10:31 am. (6 messages)
From: Carlos R. Mafra
Date: Monday, December 20, 2010 - 10:22 am

After pulling latest git from Linus (v2.6.37-rc6-132-g55ec86f)
I can't compile it anymore:

[mafra@Pilar:linux-2.6]$ make -j2 O=/mnt/ext4/kernel-output/
  GEN     /mnt/ext4/kernel-output/Makefile
scripts/kconfig/conf --silentoldconfig Kconfig
drivers/i2c/algos/Kconfig:6: unknown option "visible"
drivers/media/common/tuners/Kconfig:48: unknown option "visible"
drivers/media/video/Kconfig:115: unknown option "visible"
drivers/media/dvb/frontends/Kconfig:16: unknown option "visible"
make[3]: *** [silentoldconfig] Fehler 1
make[2]: *** [silentoldconfig] Fehler 2

This was introduced by 37e3273ee52f ("media/video: convert Kconfig 
to use the menu's `visible' keyword"), but I did a quick search 
and apparently I am the only one with a broken build. 

In any case, that's a regression for me and therefore I'm reporting it.

I can test patches etc and provide more info if needed.
--

From: Arnaud Lacombe
Date: Monday, December 20, 2010 - 10:37 am

Hi,

Did you build from a clean tree or a dirty one ?

I know these is issue with Kbuild where the parser will not get
updated to the new version if the target already exist but is older
than the current "shipped" one.

 - Arnaud
--

From: Carlos R. Mafra
Date: Monday, December 20, 2010 - 4:30 pm

It was the same one which I always compile after pulling. 
So there is compiled stuff in the build dir /mnt/ext4/kernel-output

Hm, not sure what this means. Should I do a 'make clean' to get it
back working?
--

From: Arnaud Lacombe
Date: Monday, December 20, 2010 - 4:41 pm

Hi,

yes.

 - Arnaud
--

From: Carlos R. Mafra
Date: Monday, December 20, 2010 - 5:31 pm

Ah, it works now. Sorry about the noise.
--

From: Michal Marek
Date: Monday, December 20, 2010 - 4:46 pm

Yes, if you build kconfig in the source tree and then do another build 
in a separate directory (make O=/some/where), the build system will not 
detect this and happily use generated kconfig files from the previous 
build attempt. I really should fix this given the pace of kconfig 
development lately :-).

Michal
--

Previous thread: [RFC PATCH] trace event block: conversion to tp_assign/tp_memcpy by Mathieu Desnoyers on Monday, December 20, 2010 - 10:20 am. (3 messages)

Next thread: [PATCH] dmaengine: dma40: Add support to split up large elements by Per Forlin on Monday, December 20, 2010 - 10:31 am. (6 messages)