From: Michal Marek <mmarek@suse.cz>
To: Arnaud Lacombe <lacombar@gmail.com>
Cc: "Carlos R. Mafra" <crmafra2@gmail.com>,
LKML <linux-kernel@vger.kernel.org>,
Mauro Carvalho Chehab <mchehab@redhat.com>
Subject: Re: Build regression: unknown option "visible"
Date: Tue, 21 Dec 2010 00:46:12 +0100 [thread overview]
Message-ID: <4D0FEAC4.8020009@suse.cz> (raw)
In-Reply-To: <AANLkTi=3WHB6iKaM5-=z33b9Nux7WyQ2K0apuRNwMhD=@mail.gmail.com>
On 20.12.2010 18:37, Arnaud Lacombe wrote:
> Hi,
>
> On Mon, Dec 20, 2010 at 12:22 PM, Carlos R. Mafra<crmafra2@gmail.com> wrote:
>> 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.
>>
> 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.
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
prev parent reply other threads:[~2010-12-20 23:46 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-20 17:22 Build regression: unknown option "visible" Carlos R. Mafra
2010-12-20 17:37 ` Arnaud Lacombe
2010-12-20 23:30 ` Carlos R. Mafra
2010-12-20 23:41 ` Arnaud Lacombe
2010-12-21 0:31 ` Carlos R. Mafra
2010-12-20 23:46 ` Michal Marek [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D0FEAC4.8020009@suse.cz \
--to=mmarek@suse.cz \
--cc=crmafra2@gmail.com \
--cc=lacombar@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox